This wasn’t a consumer product with casual users. Everyone interacting with this platform was a trained finance professional working under real regulatory pressure. Understanding their roles, goals, and frustrations shaped almost every design decision we made.
We adapted a flow-by-flow iterative loop — tackling one calculation flow at a time, learning the domain as we went, across 10 months.
“Requirements didn’t arrive all at once. The domain was unfamiliar. So instead of waiting, we moved with what we had — one flow at a time, repeated until the product was complete.”
Never blocked by missing requirements.
Some major flows followed the same structure.
BAs, devs & client always aligned.
Designed within what could actually be built.
Stakeholder interviews, domain research, competitive analysis, workflow mapping.
Translate complex compliance logic into clear user stories and structured flows.
Wireframes, custom components, prototypes — all aligned to the design system.
Dev hand-off, post-build QA against Figma, and iterative refinement.
We worked as a tightly integrated team with bi-weekly sprints and weekly domain sessions with our Domain Partner, who provided deep IFRS 9 expertise and requirement guidance.
“Almost every major calculation followed the exact same underlying structure. Recognising this early became the backbone of our interaction model.”
A grounded, restrained system with one decisive green accent and clear semantic states — built on Untitled UI and extended with 40+ custom components for compliance-specific patterns.
Compliance UI demands restraint. A grounded neutral base with one decisive green accent, plus semantic pastels for status and section tone.
Inter across the system. Tight tracking for display, comfortable rhythm for body, mono for amounts and IDs.
40+ custom components on top of Untitled UI — dense tables, multi-step wizards, status pills, and verification banners.
The platform transformed how banks approach credit loss provisioning, delivering tangible improvements across efficiency, accuracy, and compliance.
Designing for banking compliance with zero prior domain knowledge was the most challenging — and rewarding — experience of my career.
We began with zero fintech knowledge. By using wireframing as a learning tool and collaborating closely with BAs and our Domain Partner, we built domain understanding through the design process itself — not before it.
Our weekly meetings with the Domain Partner were the backbone of this project. Every design decision was validated against real regulatory requirements, preventing costly redesigns later.
Switching to Untitled UI mid-project felt risky, but it was the best decision we made. Custom components couldn't scale with 40+ features. A mature design system gave us speed and consistency.
Hundreds of configuration options become manageable when layered properly. Smart defaults, step-by-step wizards, and drill-down patterns made the system approachable without hiding power.
Half our flows had old designs from the 'no navigation' phase. Systematically upgrading them to the new standard was tedious but essential — consistency builds user trust in enterprise tools.
Bank employees use this tool daily under regulatory pressure. Small touches — clear error reports, progress indicators for 4-hour computations, smart period selectors — made a real difference.
Thank you for exploring our work! Your feedback is highly valued. If you found this case study insightful, feel free to share it with your network.