Skip to contentMasha Sidorova

Empower

A dashboard with one next step, and an AI coach with a person one tap away

Enhanced clarity, personalization, and ease of navigation for a retirement and investment platform with $2T in assets and 20M users, and created further support for varying levels of financial literacy.

Problems

People opened the app out of duty, checked a balance and left. 60% delayed action because they couldn't tell where to begin.

In addition, 69% were in doubt they would ever have enough to retire, and 90% wanted guidance that adapts to their situation. At the same time, the dashboard, serving as the source of truth, gave every action the same weight. In a nutshell, the problems on the user side were:

  1. Financial security fears.
  2. Overwhelming complexity.
  3. Lack of trust.
  4. Limited mobile optimization.
On this pageSolution

Solution and impact

  1. An AI Coach with a real person one tap away, so quick questions get quick answers and big money decisions get a specialist.
  2. Navigation that speaks the customers' language, interactive color-coded charts, and key information first in a clear visual hierarchy.
  3. One design system for a consistent, accessible experience on every platform, with simpler layouts, logically grouped content and high-contrast design.
  4. Mobile screens with standard navigation, streamlined interfaces and shorter multi-step flows.
2,300+
component variants across web and mobile, built on 335 tokens.
4
navigation versions to match how people talk about money.
Summarize with AI

Context

About project and settings

  • A regulated product. Projections carry SEC / FINRA disclaimers, so the AI could not give advice that sounded like a recommendation without a person in reach.
  • 6 audiences, from beginner investors who feel overwhelmed to older savers who want an advisor to decide for them, plus a Spanish-language experience.
  • Phased scope. P0 was a full rebuild of navigation and IA, with partial redesigns of the dashboard, the Coach, accounts, retirement and finance.
  • WCAG 2.2 AA on desktop, tablet and mobile.

Decision 1

Let people try the AI before it takes over support

The original brief called for a full AI coach that would replace the help center and pass people to a human when needed. Our first usability test, 6 people in hour-long sessions, changed that plan. People told us plainly that they wanted to know when they were talking to an AI and when to a person. They were happy to ask an AI about calculations, projections and definitions, but wanted a person involved in any big money decision from the start. They also asked "Why should I trust this data?"

So the Coach arrives in 2 steps:

  1. Coach Lite, the MVP. A carousel of short, actionable cards with a chat feel, a typing indicator and one message at a time, placed next to Chat with an advisor. People get used to where the Coach lives without having to type a money question to an AI.
  2. The next phase: a chat that hands over. The Digital Coach answers basic questions and points to the Empower team on anything bigger; one tap invites a person into the same conversation. Answers carry view sources, a rating and a way to change the level of detail.

This way, AI Coach, human advisor and product support are labeled as 3 separate channels, because people asked for that line explicitly.

This strategy was proven by a follow-up usability test, where the Coach wasn't in the prototype, and participants asked for personalized, chat-like advice on their own. That told us the first step had worked.

How to handle the uncertainty of AI

The Coach answers what it can and suggests the Empower team for anything bigger. One tap invites a person into the same conversation.

Coach card: New co offers a $1,000 bonus for opening an Empower cash account. Open one now to get your bonus. View
Dashboard: the Coach card with a View button
Digital Coach: Hi, Caroline! How can I help you today? Suggested questions and Start new chat
Caroline asks: Will I pay tax if I consolidate my retirement accounts? The Coach is typing
The Coach answers in 3 short lines and offers the Empower team
Invite Empower team is sent, the chat switches to a person
Samantha from the Empower team joins the same conversation

Decision 3

Retirement is 30 years away,
so make the distance visible

Gamification was in the first brief, and we removed it in April to ship a clean MVP. In May, usability test III put goal widgets in front of 12 participants: first in context on the dashboard, then each goal type side by side.

  • Goals gave a clear snapshot, and color made status stand out in a gray UI. People wanted the goals that need attention first.
  • Dollars beat percentages 85% of the time, and almost everyone wanted a goal marker for long-term goals like the emergency fund and the retirement budget.
  • A pace can turn against people. Some asked to celebrate milestones instead: "Markers don't acknowledge when life happens."
  • People wanted help setting and prioritizing their goals.

So I came back to gamification with a narrower question: how do you show a near, reachable step on a 20–30-year horizon?

I explored 5 metaphors, a dinosaur, a city, a tree, an alpaca and a hot-air balloon, all on one data model: estimated income, income goal, savings, employer contributions, Social Security, the gap. The metaphor is a skin; the real numbers stay visible in every version. Explored, not shipped, parked for Phase 2.

Dinosaur widget: an egg hatches into a dinosaur that grows with each income milestone; next step $2,500

Dinosaur.Grows with each income milestone.

City widget: each building is a goal, the estimated income, income goal and gap underneath

City.Each building is a goal.

Tree widget: from a seed in 2025 to a full tree at the 2047 goal

Tree.Grows along a timeline.

Alpaca widget: the alpaca jumps from platform to platform, one year at a time

Alpaca.Jumps across platforms, one step at a time.

Hot-air balloon widget: the balloon rises towards the income goal, 5% of the goal, next step $1,000

Hot-air balloon.Drawn from Empower's own logo.

Design system

One system in 3 libraries, maintained by other people

A shared Foundation and 2 platform libraries, Web Desktop and Mobile App, so a token change lands once and reaches both.

  • 335 variables, 105 primitive colors and 163 semantic, with Desktop, Tablet, Mobile and Wide Desktop modes; 34 text styles, including a number scale for financial figures; 256 icons.
  • 2,300+ variants across 242 component sets. Data visualization is one of the largest areas, because that's where testing found the most pain.
  • The Coach is a component in both libraries, so AI surfaces follow the same rules as everything else.
  • Governance: a changelog, documentation in zeroheight for Empower's design and engineering teams, and a status on every page: Ready, In progress, On hold or Archive.

Data on a phone. Holdings is a wide investment table. On mobile it comes in 2 patterns: a collapsible table, where each holding opens into its details, and a scrollable table, where the holding column stays put and the numbers scroll sideways. Filters, date ranges and accounts open in bottom sheets.

Tools

  • Figma

    Libraries, 335 tokens, 2,300+ variants

  • zeroheight

    Guidelines and governance

Standards

  • WCAG 2.2 AA

    The accessibility target for both libraries

Chart: touch a date to compare your index with each holding
Custom date range in a bottom sheet
Select account in a bottom sheet
Grouping and sorting in a bottom sheet
Scrollable table: the holding column stays, the numbers scroll sideways
Group by in a bottom sheet

Process

Not a straight line: every finding changed the plan, and it still shipped

3 usability rounds, 2 brief rewrites, 4 navigation versions and a summer of post-handoff work. Each finding was written down and changed what came next, so the winding path stays readable as a set of documented iterations.

WhenWhat happenedWhat it changed
Q4 2024Audit, stakeholder interviews, competitor research, card sortingThe product as a chore; the Coach reframed as a feed
Jan 2025Usability test I, 6 participantsCoach off the first screen; support ≠ AI; specific copy
Mar 2025Usability test II: comprehension, findabilityPeople asked for the Coach unprompted → Coach Lite
Apr 2025Brief rewritten twiceGamification removed from the MVP
May 2025Usability test III: goal widgets, 12 participantsDollars over percentages, goal markers kept, milestones over pace → goal metaphors explored
May–Jun 2025Accounts, mobile, handoffReady-for-dev package
Jul–Sep 2025Post-handoff collaboration: design-system work, guidance for the teams, accessibility, refinementsThe system kept up with what engineering built

Lessons

What I'd do earlier

  1. Recruit beyond confident users. Our first test leaned towards people comfortable with digital tools; the audiences Empower worried about most were the least represented.
  2. Agree on an engagement metric before testing engagement ideas. Goal metaphors came back on a qualitative signal; a baseline would have let us compare them on more than taste.
  3. Introduce AI as a presence first. Coach Lite was more than a cut-down chat: it is how people start to trust the Coach.

See other cases