Journal

Shipping design tokens without design debt

Tokens fail when they become a second design system nobody owns. A short note on keeping one source of truth.

Shipping design tokens without design debt
Design tokens fail in a predictable way. A team creates a token layer, migrates half the interface to it, and then spends a year maintaining two systems that disagree. The fix is not more tooling. It is a rule: a token may only exist if it is used, and a raw value may only exist inside a token definition. Everything else is a bug. We keep tokens small and semantic. Surface, text, muted, border, accent, and a handful of spacing steps. We do not create a token for every pixel a designer can imagine, because an over-specific token is just a hard-coded value with extra steps. When a component needs a value the tokens do not cover, that is a design conversation, not a chance to add a one-off. Most of the time the answer is that the component should look like the rest of the product.
Start a project

Tell us what you are building

We reply to every enquiry within two working days, usually with a question or two.

Get Started