A design system without an owner is a museum. Everyone visits, nobody moves things.
The systems that ship have one designer and one engineer on the hook. Everyone else contributes; those two decide.
You do not need a Figma library day one. You need a token pipeline and three components in production.
Ownership beats tooling
Name one designer and one engineer who are accountable for the system. Everyone else contributes; those two accept or reject. Committees produce beautiful component libraries that no shipping team can afford to adopt.
Start with tokens, not components
- Colour, spacing, radius, typography and elevation as semantic tokens — never raw hex values in product code.
- One pipeline that publishes those tokens to both design and code, so the two cannot disagree.
- Dark and light handled at the token layer, so themes are free rather than a rewrite.
The first three components
Ship buttons, inputs and cards into a real screen before building anything else. They cover most of the interface surface, they expose every token decision, and they prove the pipeline end to end.
Only after those three are live in production should you extend into tables, navigation and data visualisation.
Rules that keep it alive
- A component enters the system after its second real use, not before.
- Accessibility is part of the definition of done: focus states, contrast, keyboard paths.
- Every change ships with a migration note, so adoption is never a guessing game.
- Deprecations get a date, not a hope.
