06
Simplifying Registration
Turning a complex, conditional journey into a more relevant registration experience.
- Systems Thinking
- Registration
- Complex Flows
- Trade-offs
01The problem
Registration had grown into multiple paths involving account types, identity checks, documents, agreements and sponsor-related steps.
Users were navigating system complexity that was not always relevant to their individual journey.
02How I knew
Funnel data showed a 21% drop-off during registration.
Mapping the existing flows then exposed how many dependencies, conditional steps and exceptions users could encounter.
03My role
I mapped the registration logic and edge cases, then designed the core flows, states and reusable patterns across different user types and market requirements.
04Key constraints
Identity verification and business requirements could not simply be removed, and both account types and required steps varied across markets.
05Design process
- Funnel analysis
- flow mapping
- dependency mapping
- shared patterns
- conditional flows
- edge cases
- specifications
The goal was to simplify the experience without oversimplifying the underlying rules.
06Key decisions
I used progressive disclosure so users encountered requirements only when they became relevant to their specific path.
I also created shared interaction patterns instead of designing each registration variation independently.
07Trade-offs
A shorter universal journey would appear simpler but could not support all required verification and market rules.
I accepted more complexity in the underlying system to create less complexity for the user.
08Solution
A reusable registration framework that adapted to account type, identity requirements, documents, agreements and market-specific conditions.
- Simple entry
- Identity & documents
- Contextual registration
- Supporting states
09Result
Registration drop-off decreased from 21% to 14% after the redesign.
The shared framework also made it easier to support different account types and market requirements without creating separate registration experiences.
10What I’d do differently
I’d identify and test the highest-friction conditional paths earlier, rather than validating the registration journey mainly as a whole.
That would help reveal which specific rules created disproportionate friction.