Financial services · Confidential
I owned a set of core components, from buttons and form controls to action bars, in a design system rebuilt across 100+ banking applications
Buttons, dropdowns, form controls and action bars for a design system rebuilt across 100+ banking applications and inherited by 500+ partner organisations.
Context
100+ applications, 500+ partners, and no shared language
A global financial services company ran more than 100 internal applications, consumed by over 500 banking partners. Each had been built by a different team at a different time. There was no shared design language, no shared component set, and no consistent accessibility baseline.
The company committed to unifying all of it under one visual system, on a ten-year horizon. I joined as one of seven UX consultants on that programme and owned the components everything else was built on top of.
The rest of this case study covers the decisions, the reversal we had to make partway through, and how the work was validated. It’s behind a code because the client, the interfaces and the internal research are covered by NDA.
Behind the lock
What the code opens, so you know what you are asking for
- The problem
- My role
- What I chose
- What I found
- Constraints
- The design
- What changed
- What I'd do differently
Next
I designed a wallet-first recharge platform for tier-2 India that beat its yearly target in a month