Shipped
Acacia
A design system that gave a fragmented product suite one coherent voice.
- Role
- Design Lead, Systems Architecture
- Typology
- Design Systems, Product Design
- Timeline
- 2023–2024
- With
- Jordan Lee, Priya Nair
- 40+Teams onboarded
- 6 → 1Libraries unified
- -32%UI bug reports
Acacia
One system, every surface.
The brief
Acacia began as six divergent component libraries — one per product team — with no shared tokens, no shared language, and a steady drift in look and feel. The mandate was to unify them into a single, themeable system without freezing product teams mid-flight.
Approach
We started from tokens, not components: a small, audited set of colour, type, spacing, and radius primitives that every surface could adopt incrementally. Components were rebuilt on top, shipped behind a migration codemod so teams could move at their own pace.
Outcome
Within a year Acacia underpinned every shipping surface, cut UI bug reports by a third, and turned "which button do I use?" into a non-question.
Impact
A year after rollout, Acacia underpinned every shipping surface in the suite.
Teams onboarded
Components shipped
Token coverage