Role scope, the team, and the problems I was hired to solve.
The decisions that separated okay work from earned trust.
Flows, prototypes, and the system decisions that shipped.
What moved after launch, in the panel's own metrics.
Feedback from the people who reviewed the work.
The role I want, and why I'm ready for it now.
Eight years designing checkout, risk, and onboarding flows for fintech products used by millions. Three case studies, one throughline: earn trust before you ask for money.
I take briefs before they have a clean spec — fraud, compliance, and edge-case-heavy flows — and turn them into a shippable point of view.
Every direction I ship is backed by a usability read, a funnel number, or a support-ticket pattern — not a hunch.
I sit in the review room. Every claim on these slides can be traced to a number, a quote, or a screen.
Completion and satisfaction lift across the three case studies presented here, measured against each product's own baseline before my redesign shipped.
The next slides walk through the flows, prototypes, and system decisions behind the top-performing case study — the checkout redesign.
Maya was the first designer on our team to turn a fraud-ops complaint into a shipped fix within a sprint. The checkout numbers moved because she asked support the right question, not because she guessed better.
Walk the panel through the Figma file and the decision log behind the checkout case study, screen by screen.
Pair with one of your designers on a live constraint from your roadmap — I want to see how your team actually works.
A team shipping fintech or trust-heavy products, where design sits in the room when risk and growth disagree.
Session recordings and support tickets showed users abandoning at the card-entry step for a reason no funnel metric had captured before.
Checkout is the one screen where a user's trust and a company's revenue sit on the same pixel. Every extra second of doubt costs more here than anywhere else in the funnel.
The team had tried three copy tweaks before I joined. None worked, because the problem was never the words — it was the sequence of trust signals.
Replicated on two later launches with the same pattern. The lift held both times.
Checkout completion rate by week, indexed against the six weeks before my redesign shipped. The lift is not a launch spike — it holds through the full quarter.
Read raw tickets and watch three real sessions before opening Figma.
Turn the pattern into one sentence a PM and an engineer would both sign off on.
A clickable flow that isolates the one variable we're actually testing.
Usability panel plus the funnel metric it's meant to move — never one alone.
Pair with engineering through launch — I don't hand off a spec and disappear.
Three of these, back to back, is what's on the table today.