Home / Work / Loom Design System
Loom Design System
Four products, four visual languages, one very tired engineering team. Loom wove them into a single token architecture with 120 components and a governance model that stuck.
01 — Overview
Four products, one thread
Each Loom product had its own button. Seventeen buttons, to be precise. Design debt had become a hiring problem: every new designer needed a month to learn which grey was theirs.
We audited all four UIs, kept the best ideas from each, and cut the rest without mercy.
02 — Approach
What the engagement covered
- A full UI audit: 2,100 screens reduced to 340 unique patterns.
- Token architecture with alias tiers, built for theming and white-label clients.
- 120 Figma components with matching coded counterparts, tested in CI.
- Contribution model: any team can propose, one council disposes — monthly.
- Migration playbooks per product, sequenced so nothing broke at quarter-end.
03 — Outcome
The system that shipped itself
All four products migrated within two quarters. New-feature design time dropped by half, and the first white-label client theme shipped in three days instead of three weeks.
Loom's design council still meets monthly, still using the contribution template we left behind.
04 — Related work
Keep exploring
Northwind Scheduler — where the first version of these components proved themselves.
Pulse Finance — a mobile kit built with the same token thinking.
Your turn
Drowning in seventeen buttons?
Systems work is our home turf. We will audit, unify and document yours.
Start your project