
Local teams across Deutsche Bank Wealth Management kept designing and building the same components, from different libraries, for different countries.
I audited every component across the design libraries and live websites, ranked what to build first, and set the strategy for the design system in Figma.
A prioritised list of 80 components, starting with the 14 on every website, and a plan for one system serving both retail and wealth.
Deutsche Bank's Wealth Management design system was set up as a delivery accelerator for the whole bank: design and build digital assets once, and reuse them many times. Until then, local project teams had designed and built their own components, repeating effort and adding cost every time.
I was brought in for the first phase: analysis and strategy. What components exist, which matter most, and how should the system be set up in Figma so teams could start using it?
Clients saw different designs from one country and channel to the next.
The same component designed and built again by different teams.
Products and services built separately, sharing little.
Experiences that didn't follow the brand guidelines.
Pages that weren't optimised for mobile, or for search engines.
Below industry standards, and below what clients expected.
Local project teams designed and built their own components, again and again.
Every repeat added cost, and the costs kept growing.
Without ready-to-use components, every new product started from scratch.
Teams in different places, on different tech stacks, with different ideas of what a design system is.
So every product looked a little different.
Little focus on responsive design.
Before designing a single component, find out how many versions of it already exist.
I went through 11 design libraries, built over the years from four different sources, and listed every component in each. Then I checked 5 live websites, for Wealth Management and for Belgium, Spain, Italy and India.
57 of the 117 components existed in more than one library. The most common appeared in 8 of the 11.
Rather than design everything at once, I ranked components by how many live websites used them. The 14 on every site came first: build those once, and every site benefits.
Retail and Wealth Management had grown different looks. I explored whether the same components, a hero card, a global navigation and a content feed, could serve both through themes: a light UI and two dark ones.
Illustrative: the same components in three themes. Not real Deutsche Bank screens.
It buys time: design kits and component libraries can follow on top.
Even while the early work is tokens and design kits.
Teams need the most help at the start. Plan for it.
With examples, until it's how everyone talks.
Build the business's confidence that the system is a force for good.
Tokens for colour, type, spacing and motion, carrying each brand. Then atoms, molecules (components), organisms (patterns) and templates, following the atomic model the whole bank would share.
Component documentation with when to use each one, do's and don'ts, accessibility guidelines and use cases, in the design files themselves, so designers don't have to go looking.
Audited across 11 design libraries and 5 live websites.
Starting with the 14 used on every website.
Tokens, atoms, molecules, patterns and templates.
The same components for retail and wealth.
The prioritised components designed and built, starting with those on every website.
Available from January 2027
I take on contract roles as a design consultant, head of design or fractional design lead, across product, service and design systems. Remote anywhere, or hybrid across the UK.