Context Banking was built for branches. Small business owners live on their phones.
Opening a business account in the US used to mean a branch visit, a stack of documents and a wait. Novo wanted the whole thing to happen on a phone, with the day-to-day of running the account designed around how owners actually work: fast, on the move, and allergic to bank jargon.
How I found out Research before commitment.
Each flow was tested with business owners before it shipped. Onboarding and KYC got the most rounds, because that is where a new bank loses people. What the tests kept showing was the same thing: fewer decisions per step, plain language for every bank term, and progress you can see.
What I did Fewer steps, clearer decisions, one system underneath.
Simplified the workflows that usually make banking painful: onboarding and KYC, transfers, card controls, integrations and statements. Each one got fewer steps and clearer decisions, and each was tested with real business owners before it shipped.
Then I architected the design system across iOS, Android, web, the marketing site and admin, with the component library and documentation that let design and engineering scale without drift. It started as a way to keep myself consistent and grew into the thing that let a bigger team move fast.
The system started as a way to keep one designer consistent. It became the thing that let the whole team move fast.
With the team Remote across three continents, reviewed screen by screen.
A fully remote team across the US, Europe and Asia, with product and engineering in New York. As the team grew I moved into leading design, mentoring on hierarchy, spacing and interaction patterns, and I still reviewed every screen before it shipped. I also contributed to product planning and company-wide OKRs.
What changed A category-defining fintech on a system that held across five surfaces.
Novo grew from an idea into a category-defining fintech. The onboarding funnels and landing pages I designed became a steady source of lead generation and activation.
After launch What happened next.
add yoursWhat the months after launch looked like: adoption, what the team kept, what was cut, and the follow-up work it led to. Two or three sentences are enough.
What I’d do differently One thing I got wrong, and what I learned from it.
add yoursReviewers trust a case study more when it admits a misstep. Name one call that did not land, what it cost, and what you do differently now because of it.