US Bank Extended Onboarding Console
A persistent reentry system that brought 19% of dismissed customers back to complete their account setup, and lifted feature adoption by 10% in the first 90 days.
01 / Challenge
Designing Extended Onboarding: Supporting Continuity and Completion
Overview
Extended onboarding picks up where first login leaves off. It pulls users back to the dashboard and gives them one place to finish what they didn't get to the first time around, on their own schedule, without the pressure of a single sit-down setup.
Problem
If users skipped setup at first login (or only got partway through it), they had no obvious way back. The tasks just disappeared.
Why it matters
Without a way to come back, onboarding fell apart. Accounts stayed half-set-up and key features went untouched.
System context
This is the second half of the onboarding story. Instead of asking users to do everything in one sitting, it lets them finish setup gradually, when it actually fits their day.
System overview
- ▪Dashboard widget, the re-engagement entry point
- ▪Onboarding console, the task completion hub
Key insight
The hard part wasn't getting users through the tasks, it was getting them back to the tasks at all. They needed a reason to return and a clean place to land when they did.
Tension
It had to nudge people without nagging them, and surface multiple tasks without dumping everything on them at once.
Constraints
Whatever I built had to live inside the dashboard we already had, and play nice with the existing onboarding rules.
My role
I led design on both pieces, the dashboard widget and the console, and got product, eng, and content aligned on one connected flow.
Approach
Entry Point (Widget)
- ▪Surfaces incomplete tasks
- ▪Encourages reengagement
- ▪Directs users back into onboarding
Onboarding Console
- ▪Centralizes remaining tasks
- ▪Provides structure and clarity
- ▪Supports guided task completion
Outcome
Shipped a connected onboarding system that gives users a way back in, makes it clear what's left, and lets them finish at their own pace.
Part of a connected system
This experience builds on First Login Onboarding, where users are initially introduced to onboarding tasks.
02 / Impact
Reducing dropoff through persistent reentry and structured task completion.
A Reminder (Dashboard Widget) and a Console (Onboarding Console) gave people a low-pressure way to finish setting up their account on their own time. The results showed it worked.
+10%
Feature Adoption
More customers completed extended setup tasks like Alerts, Paperless, Overdraft, and Autopay within their first 90 days compared to the previous experience.
+15%
Discoverability
Users found and navigated to key digital services noticeably faster. Having the widget on the dashboard made a real difference in how people explored their account.
+19%
Console Return Rate
Customers who dismissed the first login flow returned to complete setup tasks via the dashboard widget, a behavior that didn't exist before the console launched.
My Role & Team
What I led
- ▪Set the design direction. The split between widget and console was my call, as was keeping task completion inline instead of bouncing users to separate flows.
- ▪Ran the working sessions with PM and Engineering on what was shippable in v1. I argued for the things that affected user trust and let go of the ones that were nice but not necessary.
- ▪Owned prototyping and led the moderated testing rounds with our researcher. Rewrote sections of the console after seeing what people actually did, not what they said they would do.
- ▪Stayed close to engineering through build. Pushed back when shortcuts would have weakened the spacing system on mobile or collapsed the task grid into a list.
Team
- Experience Designer (Me)
- 1 Experience Architect
- 1 Researcher
- 1 Content Strategist
- 2 Product Managers
- Dedicated Engineering Pod
Scale
Millions of U.S. Bank credit card customers
03 / Solution
A 3-component system that drove +10% feature adoption and +15% discoverability within 90 days.
The solution was a system of three connected pieces: a Prompt (Interstitial Microflow) on first login, a Reminder (Dashboard Widget) that stays visible for 90 days, and a Hub (Onboarding Console) where customers can pick up right where they left off.
One-time interstitial only
Login, see the modal once, close it, never find it again
Prompt → Reminder → Hub
Log in, see the widget, jump into the console whenever it feels right
Widget Entry Point
Console
04 / Key Decisions
The choices that shaped the outcome.
Separated the experience into a re-engagement entry point and a task completion system
Returning users turned out to be the bigger problem, so I split the design into two pieces. The dashboard widget handled getting people back in. The console handled actually finishing the work. Each piece could focus on one job instead of doing both badly.
Prioritized clarity of system feedback over reducing steps
Even after we cut steps, drop-off didn't really move. The issue wasn't volume, it was visibility. Users couldn't see what was left, so they either assumed they were done or assumed it was endless. I shifted the whole direction from "simplify the list" to "show the list clearly," which changed pretty much every decision after that.
Centralized onboarding tasks into a single, actionable console
The old fragmented setup never showed users the full picture, so I pulled every task into a single view. Now they could see what was left, what each task involved, and what was coming. If I'd had more time, I would've pushed harder on the modal-versus-full-page question.
Designed guidance and progress cues to support task completion
Users didn't just need a list, they needed reassurance. So I leaned into two things: progress they could see at a glance, and short context on why each task actually mattered. That shift took users from grudgingly checking boxes to actually engaging.
Curious how we got here? The research, explorations, and high-fidelity prototypes are all below.