Back

Led global settings redesign

Rocket’s product strategy was evolving from a “storefront” with distinct access points for each product to an integrated “platform”, with one centralized hub called “MyRocket”.
I led design on the initiative to centralize and standardize settings experiences to improve cross-sale opportunities and deliver on the integrated platform strategy.
Paul Gehrig, Product Designer
Platform Design, Content, and Engineering
Product Executives
Problem

Missed sales opportunities due to siloed settings data and disjointed client experiences

Variety of access and navigation patterns

Each product had their own design patterns in place to access and adjust product settings. A centralized platform should establish a universal pattern.

No centralized account

Settings were managed by each individual product, leading to duplicate entries from users and data inconsistencies across the company.
Ideation

How might we simplify settings access and management across core products?

Approach
Competitive analysis
Learn how similar companies handle settings management across products.
Information architecture
Determine the hierarchy and flow of information.
Sketch & gain buy-in
Illustrate how this affects each product. Who benefits the most?
Design & beta test
Establish a test case and integrate it with  existing architecture.

Strategy: Unite products under a collective platform to promote cross-product adoption

Consolidation of products under one roof would increase users' product adoption by proactively identifying opportunities to serve users across key financial moments.
Products managed data independently, leading to missed cross-sale opportunities.

Learned from industry-standard settings patterns

We conducted competitive analysis, examining how other design-forward companies with similar product suites organized their settings.
Central account settings managed in a separate experience with dedicated navigation, product-specific settings managed in context.
Secondary navigation menu for product specific settings
Separate account settings experience (link from product settings)
Secondary navigation menu for product specific settings
Separate account settings experience (link from product settings)

Mapped information architecture

We structured a centralized settings data architecture, where changes made at the Account level would reflect across individual product settings. For this to happen, all settings needed to be (technically) managed under one domain.
To appropriately map changes across products, all settings needed to be technically housed within the Rocket Account domain (preferences.myrocket.com).
⚙️ Newly devised information architecture and flow of information.

Solution overview

Problem Title

Problem description
25%
of courts do no remind defendants of upcoming court dates
55%
of courts that send reminders do so via mail or phone call

Results callout

#/%

result description

#/%

result description

#/%

result description

More to come soon 👀

Sorry to leave you on the edge of your seat! I’m actively working on crafting the story of this project and will have fresh updates soon.