One thing per screen
Each step asks for one kind of information, so the flow feels quick even though nothing required was removed.
Case study 01 · wondr by BNI
Onboarding Experience
Designing the first thing 10M+ people tap: opening a bank account on your phone, in one calm flow.
- Product thinking
- End-to-end design
- Consumer banking
The serve the challenge
Onboarding is the very first thing every new wondr user touches. It has to turn identity checks, regulatory requirements and personal details into something people can finish on their own, on a phone, in a few minutes, while giving the bank and regulators full confidence.
- Speed vs. compliance: every required step stays, but none should feel like paperwork.
- Trust: people hand over their ID and a selfie, so every step has to explain why.
- Scale: 10M+ people with very different devices, connections and digital confidence.
✏️ Draft: example copy. Replace with what actually happened.
My game what I did
- Led end-to-end UX design for the Onboarding squad, covering digital registration flows for 10M+ users.
- Drove design decisions together with researchers, POs and scrum masters.
- Ran pre-production design QA and usability testing so the shipped product matched the design intent.
- Kept the experience consistent with tech, research and design-consultant partners.
The rally how it came together
- 01
Understand
Reviewed the registration funnel, the compliance requirements, and where people hesitated or dropped off.
- 02
Map the journey
Laid out the end-to-end flow including the unhappy paths: blurry ID photos, failed liveness checks, interrupted sessions.
- 03
Design & test
Prototyped in Figma and ran usability tests to find the moments people got stuck, then iterated.
- 04
Ship & QA
Reviewed builds before release (design QA) so what shipped matched what was designed.
✏️ Draft: example copy. Replace with what actually happened.
Key shots design decisions
Recover, don't restart
When a photo or check fails, people retry that step with clear guidance instead of starting over.
Say why we ask
Short, human explanations next to sensitive steps (ID, selfie) to build trust at the exact moment it's needed.
✏️ Draft: example copy. Replace with what actually happened.
The score impact
2M+new users within 3 months of launch
10M+users through the digital registration flows
metrice.g. completion rate or time to open an account
✏️ Draft: dashed values are placeholders. Add real numbers or remove them.
Post-match notes what I learned
- In regulated flows, the copy around a step matters as much as the step itself.
- Designing the unhappy paths early saved the most rework later.
- Design QA before release is where good designs stay good.
✏️ Draft: example copy. Replace with what actually happened.
Next match
Case study 02 · BNIdirect Trade Bank Guarantee →