← BackCapital One · Jan 2025 – Present

Manager, Experience Design · Capital One

Discover Integration Experience.

Problem statement

A debit customer swipes and spends; a banking customer runs their financial life with you. How do you move spenders across that line — without losing them in the switch?

Role

UI lead — owned the “spender” framing and the end-to-end experience across First Time Experience and L2 setup, managing 2–3 junior designers and a content partner.

Platform

Native mobile · iOS + Android

Timeline

Jan 2025 – Present

Hero — the welcome moment a Discover customer sees on first sign-in to Capital One (native mobile)

First sign-in: the moment a Discover customer becomes a Capital One customer

The problem

Converting people who spend into people who bank

Success metrics · OKRs

89%

customer volume retained

↓ 35%

calls to front-line associates

Discover cashback customers came in with one relationship: a debit card they spend on. Capital One needed them to become full-timecustomers — checking, savings, the accounts people actually run their lives through. That conversion is where the value of the whole integration lives, and it's the hardest behavior to change.

The risk cuts both ways. Every screen is a chance to deepen the relationship — or to confuse someone whose familiar Discover experience just changed underneath them, and watch them quietly drop off. The goal was retention: bring as many people across as possible, and make the switch feel like an upgrade, not a disruption.

The insight

We treated every customer as a “spender”

Instead of segmenting by product or demographics, we framed every incoming customer through one behavioral lens: they're spenders. That's the relationship they already understood, and the one we had to build from. The lens was earned, not assumed — we triangulated behavioral transaction data (how Discover customers actually used their cards) with customer research before we built on it.

It sounds small, but the framing did real work. It gave a cross-functional team one shared mental model of who we were designing for, and it set the job-to-be-done: meet people where they are — spending — and create a clear, low-friction path toward the rest of what a bank can do for them.

“They're not new customers. They're spenders we already have — and the design job is to show them what else is here.”

The experience · 01

The First Time Experience

The first thing a Discover customer sees is the First Time Experience: a welcome animation, followed by a single screen that lays out everything changing for them — at a glance. It orients before it asks for anything: you're in the right place, here's what just happened, here's what's yours.

The animation does the emotional work — it marks the moment as a welcome, not a disruption — and the glance screen does the cognitive work, answering “what changed?” in one place so the question never has to become a phone call. Get this layer wrong and everything downstream inherits the confusion.

FTX — welcome animation

The welcome moment

FTX — what's changed, at a glance

Everything new, in one screen

FTX — hand-off into the home screen

Into the app

The experience · 02

L2 — the setup checklist

The second layer (L2) is where intent turns into action: a checklist of the things that actually make Capital One someone's primary bank — setting up direct deposit, moving autopay and recurring payments, and activating the new card. Each completed step is both a setup task and a small proof that the switch was worth making.

These aren't arbitrary tasks. Direct deposit and recurring payments are the stickiest behaviors a bank can earn, so sequencing the checklist around them meant the steps that took the most effort also carried the most retention payoff.

L2 — checklist overview

Direct deposit · autopay · activate card

L2 — set up direct deposit

The stickiest step

L2 — progress / completion state

Momentum + payoff

The solution

Wayfinding: telling people what changed, and where they are

Across both layers, the core design move was wayfinding — a consistent system of icons and supporting text that orients a switching customer and, above all, signals where action is needed. It answers the running question — “what's going on, and what do I do next?” — right at the point where someone would otherwise hesitate.

This is native mobile work, so the system had to hold up across real iOS and Android patterns — and it was as much a call-deflection strategy as a clarity one: every avoidable “what happened to my account?” is a call to a front-line associate, so a screen that explains itself is a screen that doesn't generate a support call.

Wayfinding — icons + text in context (annotated)

The system, annotated

Before — a screen without wayfinding

Before: easy to feel lost

After — the same screen with wayfinding

After: what changed + what to do, made obvious

The hard part

Designing inside the lines — and selling the why

The biggest constraint wasn't the brief, it was the canvas. This lives inside the full Capital One app, which doesn't allow for many custom components — so the wayfinding system had to be built almost entirely from the existing toolkit, restructured and recomposed to do a new job. The creativity was in working within the system, not around it.

Layered on top: compliance requirements shaped the language, a hard brand-migration cutover meant narrow windows, and there's no second chance — you can't re-onboard someone, so the first impression had to land the first time.

The work that mattered most wasn't pixels — it was making the case to senior leadership that this layer of clarity deserved to be prioritized, and translating “help people understand what changed” into the terms leadership measures: retained volume, and fewer calls to front-line associates.

Outcome

Measured on retention

Success was measured on two things: the customer volume retained through the switch, and how few calls the change drove to front-line associates. The second is the quieter win — clarity at the experience layer means fewer confused customers reaching for the phone. [Placeholder — drop in the OKR targets and any directional results once you share them.]

[Placeholder — what you learned / what you'd do differently.]