The problem
One platform, two very different sets of people.
Inside the brokerage, admins, managers, compliance, legal and executives needed to get through back-office work faster. Outside, traders needed to deposit, withdraw, join campaigns and copy-trade without the platform feeling complicated.
Underneath that sat a quieter problem. Backend, frontend, managers and QA were working together for the first time, each with their own workflow. Specs and builds drifted apart, and every sprint dragged with back-and-forth.
My role
I own the product design for the CRM, the back office, the client portal and the corporate site across yearly redesign phases, working directly with backend, frontend, QA and business stakeholders.
Constraints
- Regulated domain. Compliance and legal are users, not just reviewers.
- Many money-moving modules (deposit, withdrawal, campaigns, copy trade), each with a different owner.
- A team with no shared source of truth.
- Redesigns ship in phases while the platform stays live for traders.
Decisions
Map every module as three journeys
For each module I mapped the main journey, the assisted journey and the automated journey. Together they form the backbone of the happy path. Wireframes and a prototype came next, then the design system, and only then full UI.
Fix the team, not just the screens
The real gap was not design quality. Business requirements and developers had no shared source of truth. I compared API maps, data-flow diagrams and Swagger docs, using AI to speed up the analysis. None of them captured why each item existed.
Make the inventory list the single source of truth
Working with QA, we found that happy-path testing missed too many items. So every module got an inventory list: each item with its purpose written down. Design, developers and QA test against it and update it every sprint. Developers started owning their work because they understood the intent behind it.
Give the team four numbers to talk about
“How did the sprint go?” became a ten-minute review of four numbers, each owned by one role: spec coverage before build, clarification loops per item, first-pass QA rate, and module cycle time. Plus one business number per module, such as same-day withdrawal processing.
Shorten the path to critical tasks
I rebuilt the navigation architecture so the tasks people do most take two clicks instead of five.
Outcome
- Clicks-to-goal down from 5 to 2 on critical tasks, task success up 27%, satisfaction from 48% to 70% (n=64).
- A reusable component library that cut design debt by 60% and sped up handoff across web and mobile.
- Annual website visitors up 50% to 300K+, with campaign assets behind a 25% sign-up lift.
- The team moved from fixing misunderstandings mid-sprint to agreeing intent before build.
What I’d do next
- Put the four delivery numbers on a live dashboard management can see.
- Link every inventory item to its automated test, so coverage counts itself.
- Run task-based usability tests on deposit and withdrawal, the two flows where friction costs money directly.