Design Systems That Survive the Second Product
How to build a design system that does not collapse the moment a new product joins the family.
Most design systems die quietly. They are born from a single product, optimized for that product, and reworked — not extended — every time a new one joins. The ones that survive share three traits.
Tokens, not components, are the foundation
If the system is a list of components, the second product breaks it. If the system is a set of design tokens (color, spacing, type, motion) that components consume, the second product extends the tokens, not the components.
Document the why, not just the what
Every component ships with a usage guide, a do/dont list, and the principle it was built to support. Without the principle, the component gets copy-pasted into places it should not go.
A maintainer, not a committee
One team owns the system. Anyone can propose a change, but ownership is small and accountable. Otherwise the system becomes a museum.