Selected works
01 / 05

Bridge Design System

Reorganised one hard-to-navigate Figma file into Base, Patterns and tokens.

Company
Caplin Systems
Role
Design systems lead
Tools
Figma, Adobe XD, Jira, Slack

The context

Caplin builds FX trading UIs for banks. These are dense, serious products, used by people who spend all day in them and notice every inconsistency.

I was brought in to help the design team migrate from Adobe XD to Figma. A migration like that is a rare chance to ask what the design system should be, instead of copying over what was already there.

The problem

The design system lived in a single, hard-to-navigate Figma file. Everything was in one place, which in practice meant nothing was easy to find.

The colour palette was hard to apply consistently. Two designers could look at the same screen and pick different colours for the same job, and nothing in the file told them which was right.

People struggled to find components, styles and icons. When finding things is hard, people rebuild them, and the system drifts further from what ships.

  • One huge file, with no clear boundary between foundations, components and work in progress.
  • A palette with no shared logic, so colour choices were guesswork.
  • No quick way to trace a piece of design work back to where it started.

How I approached it

I started by listening to how designers, developers, PMs and POs actually looked for things, and where they gave up. The structure had to fit those habits, not my taste.

I'd already solved a similar problem at Strike, so I took that approach as a starting point and adapted it to Caplin's products and the Figma migration. Reusing something that had worked once saved time, and it meant I knew where it would break.

What I did

I split the one big file into three clear parts, so every kind of thing had one obvious home.

  • Base: the atoms. Styles, tokens and icons that everything else is built from.
  • Patterns: components organised per entity or organism, so you look for a pattern by what it is, not by who made it.
  • Jira tickets: records of design work, so decisions stay traceable and don't get lost in the system itself.
The Figma file split into Base, Patterns and Jira ticketsPreview of the new file structure

Colour, in a shared language

The colours were the part people felt most. I reorganised them into three groups, Background, Foreground and Border, and split each into Neutral, Semantic and Brand.

This deliberately mirrors CSS. Developers already think in backgrounds, foregrounds and borders, so designers, developers, PMs and POs now share one vocabulary. Nobody has to translate between “the Figma name” and “the code name”.

It also made decisions smaller. You no longer ask “which blue?”. You ask “is this a background, and is it neutral, semantic or brand?”, and the answer is usually obvious.

Colour palette grouped into Background, Foreground and Border

Making files self-explanatory

I added a cover to every file, with the link to where the work originated, a title, a description and the assignee's Slack avatar.

It's a small thing. But anyone opening a file can immediately see what it is, why it exists and who to ask. In a company where design work passes between a lot of people, that context matters more than it looks.

Figma file cover with origin link, title, description and assignee

The outcome

The “what colour should I use?” questions stopped, and the “where is it in Figma?” questions dropped sharply.

I don't have a number to put on it, and I'd rather not invent one. What I saw was designers getting on with their work and conversations with developers getting shorter and clearer.

Looking back

A design system is mostly a communication tool. The structure and the naming did more than any single component I drew.

If I did it again, I'd bring developers into the naming even earlier. Mirroring CSS worked, and I'd want to prove it in the code as well as in Figma.

Next work

Rehab Physio Dashboard