Case study · 2023
Atlas — the design system that scaled a logistics platform
Eight product teams, three brands, one tangled codebase. Atlas gave them a shared language — and
a way to keep it healthy as the company grew.
Overview
From fragments to a system
Atlas wasn’t a component library project — it was an alignment project. The hard part was never the buttons; it was helping eight teams agree on what a button should mean.
Approach
Tokens first, components second
We started underneath the UI — naming colour, type, space and motion as tokens — so that visual change could ripple safely across every brand. Components came next, then the patterns that combine them.
- A three-tier token model: primitive → semantic → component.
- One pipeline from design tokens to platform code.
- Contribution paths so teams could extend, not fork.
A design system succeeds when using it is the easiest possible choice — not the mandated one.
Impact across the org
- 8→1 Button implementations, unified
- −70% UI bugs at release
- 3 wks Saved per product launch
- 92% Component adoption
Reflection
The system is the easy part
Atlas taught me that systems are mostly social. The tokens and components matter, but the governance — how decisions get made and unmade — is what keeps a system alive once the launch energy fades.
