S/03
Design systems
Tokens, components and the written rules that stop the tenth screen drifting away from the first.
Right-sized, not impressive
A design system built for a company four times your size is a liability. It takes longer to learn than to ignore, and once a team starts ignoring it, it decays faster than having no system at all.
What gets built here is scoped to the product you have and the people who will maintain it. If that is nine components and forty tokens, it is nine components and forty tokens.
Naming that survives a rebrand
Tokens get named for their role — surface-raised, text-quiet, accent-action — not
for their current value. When the brand changes, the values change and the four hundred
references do not.
What you get
A token sheet, a component library with states documented, written rules for contribution, and a walkthrough session with your engineers.