Make something genuinely complex feel calm, guided, and trustworthy.
I designed the flows and interfaces for a GCC-focused FinTax platform from scratch - zero to first release - with that one north star.
“In fintech, clarity isn't a nice-to-have. It's how you earn the right to be trusted with someone's money.”
Complexity stacked on complexity.
- Region-specific tax rules and compliance requirements that couldn't be simplified away.
- Dense, multi-step processes - registration, filing, reconciliation - each with many fields and states.
- A mixed audience, from finance professionals to business owners with little tax expertise.
- High stakes: errors carry financial and legal consequences, so confidence and accuracy are everything.
The design couldn't hide the complexity - it had to organise it so users always knew where they were and what to do next.
Map the whole domain first; let the UI follow.
I began by mapping the entire domain as user flows - every path, decision point and edge case - before touching UI. Getting the structure right was 80% of the work.
Mapping flows first exposed hidden branches and let us sequence complexity, not dump it.
From those flows, the interface principles followed:
- Progressive disclosure - break long processes into digestible steps; show only what's relevant right now.
- Structured data over dense forms - clear grouping, sensible defaults, and inline validation to catch errors early.
- Always-visible status - where you are, what's done, what's pending, and what's due next.
- Plain-language guidance - contextual help that translates tax jargon for non-experts without patronising professionals.
An intimidating process, turned into a guided one.
The platform shipped its first release with flows and interfaces usable by experts and newcomers alike.
