Product Design Case Study · Design SystemsContainer xChange · container logistics · 2022 – 2025
Running a design system as an internal product
Container xChange was growing faster than its UI kit: 79 different buttons, and fixing a single component could eat a week. I started Compass, built the team and ran the system as a product. It is still running today, outliving the team that built it.
- Role in the project
- Design Systems Team Leadand lead designer: strategy, architecture, team, rollout, measurement
- Team
- Guild, then systems teamFirst on my own, then with a direct report; later 2 design, 1 QA, 2 engineering
- Responsibility
- Compass as an internal productRoadmap, OKRs per trimester, research and the sentiment report
- Status
- and 2 more states
Live+2
As of September 2026
Live
In the live product since T2 2023, after 11 months from zero to one
In use
Still in use and still evolving
Open
Documentation use stayed the weak spot at 2.2
Live+2
As of September 2026
Live
In the live product since T2 2023, after 11 months from zero to one
In use
Still in use and still evolving
Open
Documentation use stayed the weak spot at 2.2
A design system is not a kit you ship once. It is a product with users and upkeep, and it has to keep running without its team.
Compass Design System
At a glance
55 → 71%
overall sentiment in the Compass Sentiment Report
55 → 71%overall sentiment in the Compass Sentiment ReportInternal survey, Q3 2022 → T2 202311 → 82%
positive responses about Compass
11 → 82%positive responses about CompassCompass Sentiment Report, Q3 2022 → T2 202379 → 1
buttons in the live product, then one Compass button
79 → 1buttons in the live product, then one Compass buttonCounted in the code; the Compass button live in T2 2023
Problem
A product, not a UI kit
79 different buttons in the live product. I set Compass up with users, a roadmap and OKRs.
Intervention
Building blocks first, docs later
250 tokens, one button instead of 79, live in T2 2023. The price: documentation use stayed at 2.2.
Outcome
Outliving the team
4 of 7 key results in T2 2023. Compass is still running, outliving the team that built it.
- Role in the project
- Design Systems Team Leadand lead designer: strategy, architecture, team, rollout, measurement
- Team
- Guild, then systems teamFirst on my own, then with a direct report; later 2 design, 1 QA, 2 engineering
- Responsibility
- Compass as an internal productRoadmap, OKRs per trimester, research and the sentiment report
Not another UI kit, but a product with users
The old UI kit could no longer be reworked. Every team solved problems on its own, flows and interfaces contradicted each other, and one-off solutions ate time that product work needed. The live product had 79 different buttons in use. We counted them in the code: a developer on the team had built a script that tracked down duplicates and custom code.
The old kit was broken at the root: nested spacers inside every component, with Bootstrap still lurking underneath. Every change turned into a repair job.
Instead of building yet another UI kit, I set Compass up as a product: its own strategy and roadmap, OKRs every trimester and three user groups, designers, engineers and product managers. I pitched it and represented it in the Product & Tech Leadership Circle. My design lead sponsored it, with backing from product and engineering leadership.
At first there was no official team for it. Compass began as an initiative and grew step by step:
- Me
Guild
First foundations alongside day-to-day work, laid by me
- MeProduct designer
Product designer
Brought in with my design lead, reporting to me
- MeProduct designer
Systems team
Me as Design Systems Team Lead and lead designer
- DesignDesignQAEngineeringEngineering
With engineering
Later 2 design, 1 QA, 2 engineering
One system, four roles, four different jobs
Before we touched a single component, I found out who needed Compass and for what. The Q3 2022 baseline survey had its own questions for every role: how does the old system feel, how satisfying is it, where does time get lost, what does documentation cost, who contributes. 35 people answered, 18 from engineering and QA, 12 from product and leadership, 5 from design. We added interviews with a pain-point analysis, a review of tools and processes, and benchmarks such as Shopify Polaris and IBM Carbon.
The baseline survey asked each role its own questions. Four jobs to be done came out of it, one per role:
Product designerJob story
- When
- I design a new feature,
- I want
- proven building blocks,
- so
- my time goes into the problem, not into rebuilding UI.
UI engineerJob story
- When
- I build an interface,
- I want
- Figma and Storybook to show the same thing,
- so
- I don't rebuild what already exists.
Product managerJob story
- When
- I plan a feature,
- I want
- to know what the system already covers,
- so
- I can decide faster and not wait for one-off solutions.
Brand and marketingJob story
- When
- I build a campaign,
- I want
- the same colours and rules as the product,
- so
- xChange looks the same everywhere.
Absolutely chaotic, outdated and impractical.
I spent a week fixing a single component.
To find the structure, we ran a card sort on the existing components: 46 building blocks, five people from design and engineering. It produced the taxonomy Compass still runs on today: foundations, actions, inputs, data display, containers, overlays, navigation, feedback, notifications, patterns, loaders, atomic elements and branding.
Building blocks first, the big vision later
The first plan was a research plan. We wanted to understand the problems, gather qualitative insights and derive a target picture we could plan backwards from. The models were scalable systems like Shopify Polaris and IBM Carbon: a foundation you can build several houses on.
Original
Vision first
Research and learning, leading to a target picture for a system like Polaris or Carbon.
New
Building blocks first
Tools that let teams ship faster right away. The research results were kept.
Why the switch: the company and its products were in an experimental MVP phase.
That set the goal for Q4 2022: the new UI kit for design by the end of the year, and for engineering from Q1 2023. At the same time we worked out with engineering how the route from design into code should look and what they needed for it.
For alignment we sorted everyone involved into three rings: who builds, who has a say and who stays informed. That made it clear whom to involve when.
- 01Core teamUX/UI design from product, front-end engineering from the marketplace, graphic design from marketing, QA as an open role
- 02InvolvedBrand lead, product managers, the front-end guild with a senior engineer
- 03InformedHead of engineering, head of product and further leadership
A name says what a colour is for
Compass had to carry five products: Leasing, Trading, Trucking, Slots and Wallet. So it was laid out as a hierarchy: tokens at the bottom, components, patterns and templates on top of them, the products at the very top. Whatever should look consistent at the top needs one shared source at the bottom. Without it, 79 different buttons had appeared.
Tokens
Colours, type, elevation, spacing, shadows
Components
Toggles, buttons, input fields, badges, checkboxes
Patterns
Tables, cards, page headers, modals, lists
Templates
Navigation, login, funnel, profile, dashboard
Products
Leasing, Trading, Trucking, Slots, Wallet
- Categories
13, from a card sort in July 2022: 46 building blocks, five people from design and engineering
- Modules
Complex blocks such as page header, navigation and shell elements, with their own area on the board
- Homes
Figma kit for design, Storybook for code, Zeroheight for the docs
- Benchmarks
Shopify Polaris and IBM Carbon
The old kit knew colour values but not their jobs. So I named every colour by role, family and state: “interactive-primary-hovered” is the hover of a primary element, whatever tone sits behind it. Semantic names are longer and take discipline. In return, a tone changes in one place and reaches all five products, instead of being chased through every file.
The grammar of the tokens
We kept the foundation deliberately small, because usability and maintainability were the first objective: 250 tokens, ten colour roles with up to six states per family, eleven type sizes on a 4px grid, twelve spacing steps, six radii and two shadows. During the rollout we cleaned the tokens up and scaled them so new products could adopt them instead of inventing their own. That is what the hierarchy was for.
The alert draws on the same families as the button: danger, warning, success, informative. Change a tone and both change. See the alert in the lab.
Every edge comes from a token
The button shows how the system works at small scale: eight styles, four heights from 24 to 48 pixels, an icon on the left, the right or on its own, and a loading state. Spacing, radius, type and colour each come from a token, including hover, pressed and focus.
Button with token inspector
For this page I rebuilt Compass: measured from the rendered original and written from scratch in React. I rebuilt 65 components this way and checked each against the original, measurement by measurement; whatever I had to approximate is listed on its page.
Measuring exposed a gap: in the original, a disabled toggle looks almost like an enabled one; only the icon colour and the cursor change. The rebuild shows it on purpose, the way it was. See the gap in the lab.
Accessibility
Accessibility was a binding design principle in Compass: keyboard use, contrast, colour use and type sizes. The starting point was the old kit, whose colours lacked contrast. During the rollout we sharpened the contrast of the neutral tokens for placeholder and subtle text, made the type tokens responsive and checked all 57 components against the responsive criteria. There was no full WCAG review or audit.
The rebuild now measures against WCAG and shows where the original still had gaps: the disabled toggle is barely distinguishable from the enabled one, some contrasts fall below AA, and not every element shows a visible focus. In the rebuild these spots are documented on the component page and fixed where possible.
Contribute, don't fork
A library alone doesn't carry a system. The Figma kit, Storybook and the documentation had to stay in sync, and teams needed a clear way to contribute instead of building next to Compass.
Figma kit
Components and tokens as the source for design.
Storybook
The same components in code, reworked during the rollout.
Zeroheight
One home for rules, examples and usage.
Product teams
Use, report and contribute through contribution guidelines.
The hardest route was the one from design into code. In autumn 2022 we worked out with engineering what they needed and planned a test library. In T2 2023 we reorganised and overhauled Storybook. That did not close the gap completely: in the survey, teams asked for Storybook, docs and Figma to line up better, and missed code documentation.
Above the components sat the patterns. We ran complex building blocks such as page headers, navigation and shell elements as modules, with their own area on the board: 42 of the 181 tickets in T2 2023. A pattern library for recurring flows came on top.
One flow instead of many parts
Rules turn building blocks into a system. The survey asked designers how they use the kit, on a ladder from one-off solutions to global components only. In T2 2023 all seven designers stood on the same rung.
- Extend by the rules
- 0%100%+100 pp
- One-offs
- 60%0%−60 pp
1 · One-offsOne-offsEvery design a one-off, so-called snowflakes.2 · MixMixOne-offs and global components, adapted personally.3 · Adapt and give backAdapt and give backAdapt global components and give the change back to the system.4 · Extend by the rulesExtend by the rulesUse global components, extend them by set rules or request new variants.5 · Global components onlyGlobal components onlyWithout any adaptation.
One answer per designer.
Two principles sat behind it. Before anyone builds a new component, they check whether an existing one can be extended. And Compass provides building blocks that fit 80 per cent of the time, without anyone having to reinvent them.
Open to everyone, with set routes
Compass was open to contributions from every team. To keep that from turning into chaos, every contribution needed a set route into the system, and every role knew what it was responsible for. Every release got a version, and anything being replaced was marked deprecated before it was removed. We planned to retire the old UI kit and its legacy code over two trimesters. That was harder than expected, because nobody knew exactly where old code was still hiding.
Request or contribution
In the #design-systems channel or by the contribution guidelines
Parking lot and backlog
Everything lands on the Compass board, prioritised by the OKRs
Weekly sprint
Design and engineering in the same week
Quality gate
My frontend developer checks every contribution before release
Release and changelog
As a version, with the changelog in Confluence, Zeroheight and the channel
Systems team
Plans, builds, releases and measures the system, prioritised through OKRs every trimester.
Design
Uses the building blocks, extends them by the rules and requests new variants.
Engineering
Keeps the components in code identical to the kit and watches over consistency.
Product
Asks for existing components first and plans MVPs from what exists.
Marketing and brand
Brings the brand guidelines into the docs, since T2 2023.
Split from the target picture at the start; marketing and brand joined in T2 2023.
A system doesn't adopt itself. We presented Compass at all-hands and tech town halls, started an AMA for designers, set up a channel for questions and a Confluence page with a changelog, and opened the system to contributions from every team.
Learning
If you think you are over-communicating, you are probably doing it right. A design system lives on its messages landing again and again.
Measuring what tickets can't show
In T2 2023 the new UI kit went live, and the team rebuilt the whole platform on Compass, right up to the frame around every page.
- Components75 tickets
- Modules42 tickets
- Docs25 tickets
- Strategy21 tickets
- Foundation12 tickets
- Other6 tickets
15
components and modules documented to our MVP definition
100%
of components meet the responsive criteria
From token to product screen
Measurability was a key result in its own right: at least two qualitative and quantitative metrics for the impact on product and business. For the quantitative side we compared notes with teams at booking.com, Figma and Pinterest; all of them were wrestling with the same question. My proposal was a shared label for design-system work. Until then, the sentiment report carried the load, with its own scoring across all answers.
- Satisfied · 4 and 5
- 21%56%+35 pp
- Dissatisfied · 1 and 2
- 33%14%−19 pp
Share of answers per rating, across all questions.
Averages in T2 2023, scale 1 to 5
3.9+0.9
Compass overall · before 3.0
3.9Compass overall · before 3.0Average of all answers about Compass overall, on a scale from 1 (very dissatisfied) to 5 (very satisfied). From 3.0 in Q3 2022 to 3.9 in T2 2023.4.0+1.4
Figma kit (design) · before 2.6
4.0Figma kit (design) · before 2.6How designers rate the Figma kit. From 2.6 to 4.0: the kit went from obstacle to tool.4.0+2.2
UI kit used as intended (design) · before 1.8
4.0UI kit used as intended (design) · before 1.8How consistently designers use the UI kit by its rules. At +2.2 the biggest jump among these values.4.0+0.9
Code library (engineering) · before 3.1
4.0Code library (engineering) · before 3.1How engineers rate the code library. From 3.1 to 4.0; positive answers from 28 to 69 per cent.3.5+0.4
Code library usage · before 3.1
3.5Code library usage · before 3.1How much the code library is used day to day. The smallest rise: from 3.1 to 3.5.2.2newly measured
Docs: usage
2.2Docs: usageAsked for the first time in T2 2023, so there is no earlier value. At 2.2 the lowest value, the price of the decision: building blocks first, docs later.
That weak spot was the price of my October 2022 call to ship the bricks first and the docs later: documentation usage scored 2.2, well below everything else.
Trimester scorecard: 4 of 7 key results
When xChange had to restructure, the systems team was disbanded. I took over Financial Services. Compass is still in use and still evolving; the designer who stayed on has made it tool-agnostic for AI-assisted coding. My design lead at the time later wrote that I had built the initiative from the ground up.
Compass Sentiment Report, Q3 2022 → T2 2023
55 → 71%
overall sentiment in the Compass Sentiment Report
55 → 71%overall sentiment in the Compass Sentiment ReportPoints against the maximum across all questions, scale 1 to 5: 55.1% from 35 responses, 70.5% from 33. The questionnaire grew from 7 to 17 questions.11 → 82%
positive responses about Compass
11 → 82%positive responses about CompassShare of answers rating Compass 4 or 5, from 35 and 33 responses.28 → 69%
Engineering: positive responses on the code library
28 → 69%Engineering: positive responses on the code libraryEngineering only, on the code library: average 3.1 → 4.0, from 18 and 13 responses.
We planned in trimesters with OKRs. The first objective in Q4 2022 was deliberately narrow: the UI kit ready for designers by year end, for engineering from Q1 2023. In T2 2023 there were three objectives. In Jira, each key result got its own version and each theme its own epic, from foundation through components and modules to strategy and operations. At the end of every trimester you could see which work fed which objective, and how much ran without one.
15 components and modules documented to our MVP definition
Reached in T2 2023.
O1 · Usability and maintainability
Brand and marketing guidelines fully in Zeroheightopen
Started: brand and marketing took on ownership, but it was not complete within the trimester.
O1 · Usability and maintainability
Change communication strategycut
Cut on purpose: there were not enough people for a communication strategy of its own.
O1 · Usability and maintainability
At least 2 qualitative and quantitative impact metrics
Reached in T2 2023.
O2 · Make product impact measurable
Remaining share of the old kit in code, for deprecationcut
Cut on purpose: where the old kit still sat in the code could not be found reliably.
O2 · Make product impact measurable
Responsive criteria defined
Reached in T2 2023.
O3 · High-quality design output
All 57 components meet the criteria
Reached in T2 2023.
O3 · High-quality design output
I dropped two key results on purpose: where the old kit still lived in the code couldn't be pinned down reliably, and we lacked the people for a dedicated communication strategy. OKRs aren't a scorecard for me; they're a way to prioritise, and you're allowed to change them mid-flight.
Outlook: From foundation to partner in projects
Up to T2 2023 we built the foundation. After that, Compass was to move into a project-based way of working: share goals and the roadmap openly, and sit at the table from the start of bigger projects.
The design system as a stakeholder in future projects
3.6
average agreement, scale 1 to 5
67%
positive answers
A visible roadmap
A roadmap for the next trimester, so teams can plan.
Patterns and flows
Guidelines, patterns and global flows, not just components.
Code and docs
Code documentation and a Storybook that matches Figma and the docs.
Mobile and multilingual
The mobile and localisation initiative, restarted in T2 2023.
The vision from the start was not off the table. It now came after the building blocks teams had needed right away, and would have been the next step.
What I learned and would do differently today
Caveats
The initiative was mine; many people built Compass: first a guild, then the systems team with design, QA and engineering. The figures come from an internal survey with 35 and 33 responses; values per discipline rest on small groups. As of October 2026.
Learnings
Usable first, complete later
The building blocks came before the docs. Teams got faster, and documentation use at 2.2 was the price.
Big rollouts need project leadership
A rollout across the whole platform is a project of its own. It ended the trimester as a learning in our report.
Speed needs a shared label
Without consistent ticket labelling, velocity cannot be measured honestly. Until then, the sentiment report carried it.
Act proactively
Don't wait for teams to ask for the system. Go to them and show what it can do.
What I would do differently today
Involve engineers earlier
More engineering in the concept phase would have made technical integration easier from the start.
Start with pilot teams
Rolling out to a few teams first would have brought earlier feedback and more room to adjust.
Plan measurement from day one
I'd introduce a shared label for design-system work before the first component, not propose it after the fact.
Check every state early
Test every state for contrast and recognisability from day one, not in review. The disabled toggle showed why.
A design system is a product in its own right. It needs clear ownership and ongoing care. Either you build it to last, or it becomes overhead.
fin (for now)