Design
Design system
Also called
- Component library
- Design tokens
A design system is three things together: the visual decisions expressed as tokens (color, type scale, spacing, motion), the components built from those tokens, and the documentation that says when to use which. A library of components without the rules is a component library, not a system.
Its value is economic rather than aesthetic. The first screen costs the same either way. The twentieth costs a fraction, because it is assembled rather than designed. That compounding is the entire argument.
The second value is durability. Consistency that lives in a system survives staff changes; consistency that lives in one designer's head does not.
A team shipping more than a handful of screens a year without a design system is paying the full cost of the first screen every time.
Commonly misunderstood
What people get wrong
The claim
“A design system means everything looks the same.”
What is actually true
It means the *primitives* are the same. Variation lives in composition, where it carries meaning, instead of in whether two buttons are accidentally different shades of blue.
Where this comes up
Services where it matters
Related terms
Next step
Working through a design system decision?
Tell us the situation. We will give you the tradeoffs as we see them, including when the answer is that you do not need what you are being sold.
No pitch deck. A 30-minute conversation about what you are trying to achieve.