Design Systems as Living Organisms
Tokens, components, and governance that evolve with the product — not against it.
A design system that never changes is a museum. A useful system is closer to a garden: pruned, fed, and occasionally re-planted.
Tokens first
Color, type, and space tokens are the DNA. Components are phenotypes. When DNA is messy, every component mutates differently.
Map of a simple token-to-component system
Governance without bureaucracy
- Owners for each domain (forms, navigation, data display)
- Change logs that product teams actually read
- Escape hatches with an expiry date, not permanent forks
Growth loops
The healthiest systems take real UI debt from product work and fold it back into shared primitives. That loop is the organism breathing.
If your system only ever ships new kits and never retires old ones, it is not growing — it is accumulating.