Design systems are products for your own team

Users first, even here

The users of a design system are designers and developers on deadline. If the system slows them down, they will route around it — quietly, and then everywhere.

So we interview them before we draw a single token. Where do they copy-paste? Which components do they rebuild every sprint?

Tokens before components

We define colour, type, spacing and motion as tokens first, named by role, not by value. A token called Text Secondary survives a rebrand; one called Grey 500 does not.

Components come second and only for patterns that repeat. Fewer components, used everywhere, beat a giant library used nowhere.

Releases and governance

A system needs releases, changelogs and an owner, just like a product. We set up the rules for adding, deprecating and versioning so the library grows without rotting.

The best compliment we get is silence: teams just use it.