Designing a Global Nav

for 7 Million Users

Designing a Global Nav for 7 Million Users

Designing a Global Nav for 7 Million Users

Overview

Client

Big 3 Asset Manager

role

UX Designer

duration

1.25 years

Tools

Figma & Storybook

Description

Atlas* is an investment company whose principles and offerings focus on retail investors. Recently one of their major strategic goals put an emphasis on modernizing the digital experiences for their clients.

We were contracted by Atlas to accelerate this effort. That’s when I landed in the Atlas “NavLab” and became the UX/UI designer to create a global navigation component. The team’s roster consisted of Atlas UX strategists, an EY researcher, and complete Atlas dev team. The focus of our roadmap was for authenticated (logged-in) clients, but as you’ll see, our stakeholders spanned much further than that.

*To maintain client privacy, some details have been changed or redacted

Design Drivers

Align IA to user mental models

Design in tandem with research

Intentionally familiar

Flexible and feasible solutions for development

Cross discipline collaboration at the core of every decision

Pain Points

Each release was guided by 3 key pain points


Pain Point 1 OF 3

Hidden & Buried Navigation

Where we started

Navigation was commonly mentioned in users’ complaints due to buried or hidden links. User satisfaction had dropped so low that clients were ready to move their assets to competitors. A new navigation component would take more than a year to build, so we found a series of quick wins that would enhance the user experience in the interim.

...my clients are consistently telling me that firms like [redacted] have far greater reliability and are far easier to navigate.

...my clients are consistently telling me that firms like [redacted] have far greater reliability and are far easier to navigate.

...my clients are consistently telling me that firms like [redacted] have far greater reliability and are far easier to navigate.

— Source redacted

Approach

To address hidden and buried navigation and clients' overall decreasing satisfaction, we took 3 steps early in the project that were low risk. These three small wins were ways we learned to walk before official sprints.

Step 1

Repainting "cells" and "organisms" leveraging Atlas' new design system.

Atoms

Tokens

Molecules

Components

Cells

Patterns

Organisms

Blocks

Species

Templates

Atlas Design System

NavLab (that's us)

Pages

Step 2

Addressing the disjointed taxonomy by incorporating headings to a mega menu, which were informed by IA research findings.

Show UI & Taxonomy

After
Before

Gains and losses

Step 3

Adding personalization for clients with premium services, like Advised Services

Advised Client

Portfolio

Dashboard

Balances

Performances

Watchlist

Gains and losses

Cost basis

Dividends & capital gains

Transact

Buy and sell

Order history

Open an account

Profile and account

Settings

Messages

Statements

Tax forms

The First Release

The results of our approach enabled us to create the renewed mega menu for clients while they viewed their account.

Atlas users can select up to three (3) account types;

and product teams were siloed across these account types

Atlas users can select up to three (3) account types;

and product teams were siloed across these account types

Open an account

Forums

Support

Settings

log off

My Account

What we offer

Products

News

Portfolio

Dashboard

Balances

Performances

Watchlist

Gains and losses

Cost basis

Dividends & capital gains

Dividends
& capital gains

Transact

Buy and sell

Order history & status

Order history
& status

Open an account

Profile and account

Settings

Messages

Statements

Tax forms & information

Open an account

Forums

Support

Settings

log off

My Account

What we offer

Products

News

Advisor

Advisor Overview

Contact Advisor

Reports

Portfolio

Dashboard

Balances

Performances

Watchlist

Gains and losses

Cost basis

Dividends & capital gains

Transact

Buy and sell

Order history & status

Open an account

Profile and account

Settings

Messages

Statements

Tax forms & information

Pain Point 2 OF 3

/

Inconsistent Navigation Patterns

Siloed teams

Atlas users can select up to three (3) account types, self-directed accounts, advised accounts, and lastly employer sponsored retirement. Unfortunately the business split product teams across product types, which inevitably led to siloed teams.

Atlas users can select up to three (3) account types;

and product teams were siloed across these account types

Atlas users can select up to three (3) account types;

and product teams were siloed across these account types

Self-directed

Advised (Robo/Personal)

Employer sponsored retirement

Existing patterns

Since product teams have been siloed, multiple nav patterns existed across the site including the header, footer, and menus.

Atlas

Log out

Atlas

English

Atlas

Atlas

Exit

Retail investors

Open an account

Forums

Support

Settings

log on

What we offer

Why us

News

Atlas.

Retirement

Help

Message Center

Log off

Your investments

Deposits

Accounts

Tax information

Atlas

Personal Advisor

More

Dashboard

Contribute

Withdraw

Investment goals

Contact your advisor

Reports

Upcoming Appointments

Retail investors

Open an account

Forums

Support

Settings

Log out

Atlas

Search

Home

My Accounts

Transact

News and Perspectives

My Accounts

What we offer

Why us

News

Support

Log out

Dashboard

Account

Activity Feed

Contribute Cash

Withdraw Cash

FAQ

Atlas

Robo investing

Collaborative Approach

Research Driven

Organized an IA consistent with user mental models by using card sort and tree test research findings.


Tested different navigation orientations, components and terms, selecting ones that resonated most with our users

Product + Development

Aligned design to agile ceremonies and included development in design feedback sessions.

Documented designs and components to ease hand-off

Everyone

Added a weekly “Studio” ceremony and facilitated weekly workshops with topics like accessibility, research plan feedback, knowledge sharing, and more.

Our Solution

With a limited technology architecture and client segments we required a solution that we could deploy without impacting stakeholders and avoid user change fatigue


Working together, we discovered if we could implement a navigation design system we could meet the needs of both users and stakeholders.


Stakeholder Taxonomy + Nav Design System =
A new nav for any product team, regardless of tech implications.

Taxonomy

{
"topLevelItems": ["1", "2", "3"],

"items": {

"1": {
"parent": null,
"title": "title",
"children": ["11", "12", "13"]
},
"11": {
"parent": "1",
"title": "title",
"children": ["111", "112"]
},
"111": {
"parent": "11",
"title": "title",
"children": ["1111", "1112"]
},
"1111": {
"parent": "111",
"title": "Copyrighted"
},
"1112": {
"parent": "1111",
"title": "Public Domain"

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

Navigation Block Model

Logo and Label

Utility & Global Functions

Site Links

Quick Action

Dropdown Pattern Example

[Heading]

[Link]

[Link]

[Link]

[Link]

[Link]

[Link]

[Featured Heading]

[Heading]

[Body text]

[Link]

Self-directed

Atlas

Employer Plans

2

Plan Summary

Manage contributions

Learning center

Contribute + Withdraw



Advised

Atlas

Retail investors

2

Dashboard

Portfolio

Trade

Products

News & Tools

Contribute + Withdraw



Employer sponsored retirement

Atlas

Robo Advisor

2

Dashboard

Account

Activity

FAQ

Contribute or Withdraw

Figma Demo

Click around and get a glimpse of the redesign.

Second Release

An intentionally familiar design, with additions of persistence and conditionality to reduce client burden while promoting discoverability and personalization.

Atlas

Atlas

Help & Support

Exit

Atlas

Log in

What we offer

Why us

News & Tools

Open an account

Atlas

All Accounts

2

Dashboard

Portfolio

Trade

Products

News & Tools

Tax information

Atlas

Robo Advisor

2

Dashboard

Account

Activity

FAQ

Contribute & Withdraw

Atlas

Personal Advisor

2

Dashboard

Transact

Goals

Reports

Appointments

Contact Advisor

Atlas

Employer Plans

2

Investments

Deposits

Accounts

Tax information

Atlas

Welcome to Atlas

2

Get Started

What we offer

Why us

News & Tools

Finish setting up account

Pain Point 3 OF 3

Isolated Experiences

"Cross-over" users

Remember the three account types?

Self-directed

Advised (Robo/Personal)

Employer sponsored retirement

What would happen to the experience if one investor held multiple account types?

Self-directed +

Advised (Robo/Personal) +

Advised (Robo/Personal)

Employer sponsored retirement

Disparate sites

Approximately 97% of all users are self-directed only clients.


The remainder were a mix of cross-over clients that need to move between sites to access different account details


By default, advised users all land on an advised page. 60% of these clients immediately navigate towards a buried link to move from their advised to self-directed sites.


We heard from multiple users that they relied on bookmarked links in their browser to make navigation easier.

Atlas

All Investments

2

Dashboard

Portfolio

Trade

Products

News & Tools

Tax information

Atlas

Robo Advisor

2

Dashboard

Account

Activity

FAQ

Contribute & Withdraw

Atlas

Employer Plans

2

Investments

Deposits

Accounts

Tax information

Atlas Product Model (simplified)
three separate sites

Self-directed accounts

Advised accounts

Employer sponsored accounts

vs

Crypto and other volatile assets

Accounts aligned

to short term goals

Accounts aligned to

Long term goal

Additional layer of advice

Tax advantage accounts

Highest Risk

Lowest Risk

My accounts

Understanding the paradigms

From user interviews we discovered that users understood there were multiple sites, but did not understand why.


Users typically did not separate their investment strategies by account types, and would have preferred to see all investments on one site.


With technical constraints on the architecture, we were required to design and develop a new pattern for our navigation design system that eased client burden of moving inside the product model.

Testing patterns

With a research driven approach, after interviewing cross-over clients about their mental model, we tested multiple concepts that would be feasible to develop.

All Accounts

Advised Accounts

Employer Plans

Atlas

Dashboard

Portfolio

Trade

Products

News & Tools

Atlas

Account view

Self-directed

Dashboard

Portfolio

Trade

Products

News & Tools

Tax information

Atlas

Your Accounts

Self-managed

Dashboard

Portfolio

Trade

Products

News & Tools

Tax information

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

did not work

The Final Solution,
featuring the "site selector"

A tab pattern next to the logo resonated most with our clients. We discovered that this pattern clearly indicates where a user is in their authenticated experience so they are no longer lost in the product model. Users also understood that the top dark bar, the global controls, changed the bottom white bar, the local links controls. Lastly, we noticed during testing that the tab pattern made it easy to recover or go back between sites, which was important for users who were not familiar with the information architecture.

A tab pattern next to the logo resonated most with our clients. We discovered that this pattern clearly indicates where a user is in their authenticated experience so they are no longer lost in the product model. Users also understood that the top dark bar, the global controls, changed the bottom white bar, the local links controls. Lastly, we noticed during testing that the tab pattern made it easy to recover or go back between sites, which was important for users who were not familiar with the information architecture.

A tab pattern next to the logo resonated most with our clients. We discovered that this pattern clearly indicates where a user is in their authenticated experience so they are no longer lost in the product model. Users also understood that the top dark bar, the global controls, changed the bottom white bar, the local links controls. Lastly, we noticed during testing that the tab pattern made it easy to recover or go back between sites, which was important for users who were not familiar with the information architecture.

Logo

Site Switcher (cross-over users only)

Utility & Global Functions

Site Links

Quick Action

Atlas

All Accounts

Advised Accounts

Employer Plans

2

Dashboard

Portfolio

Trade

Products

News & Tools

Tax information

Atlas

All Accounts

Advised Accounts

Employer Plans

2

Dashboard

Account

Activity

FAQ

Contribute & Withdraw

Atlas

All Accounts

Advised Accounts

Employer Plans

2

Investments

Deposits

Accounts

Tax information

Atlas

Back to Dashboard

2

What we offer

Why us

News & Tools

Open an Account

The end

The end

Once the site selector design was finalized with a "ready for dev" stamp, it was time to rolloff. Luckily our approach you just read through, doubled as a great resource for onboarding a new designer.


All the releases in this case study are now live. Our process worked. We found a solution that worked for every team across Atlas, enabling them to implement the nav design system with their own dev teams. Without their buy-in, there wouldn't have been a consistent and intuitive nav for our users.


I am very proud to have been a part of this "Atlas" team.

Once the site selector design was finalized with a "ready for dev" stamp, it was time to rolloff. Luckily our approach you just read through, doubled as a great resource for onboarding a new designer.


All the releases in this case study are now live. Our process worked. We found a solution that worked for every team across Atlas, enabling them to implement the nav design system with their own dev teams. Without their buy-in, there wouldn't have been a consistent and intuitive nav for our users.


I am very proud to have been a part of this "Atlas" team.

Once the site selector design was finalized with a "ready for dev" stamp, it was time to rolloff. Luckily our approach you just read through, doubled as a great resource for onboarding a new designer.


All the releases in this case study are now live. Our process worked. We found a solution that worked for every team across Atlas, enabling them to implement the nav design system with their own dev teams. Without their buy-in, there wouldn't have been a consistent and intuitive nav for our users.


I am very proud to have been a part of this "Atlas" team.