Most teams that say they have a design system actually have a component library with a nicer name. That’s not nothing, but it’s missing the half that makes a design system worth the investment.
What’s actually in one
- Design tokens: the smallest decisions (colour, type scale, spacing, radius, shadow) defined once and referenced everywhere, so “change the brand accent colour” is a one-line edit, not a find-and-replace across every screen.
- Components: buttons, inputs, cards, navigation, built once, documented with every state (default, hover, disabled, error, loading), as well as the happy-path screenshot.
- Patterns: how components combine to solve a recurring problem (a form’s validation pattern, an empty-state pattern, a confirmation-before-destructive-action pattern). This is the layer most component-library-only “systems” skip entirely.
- Content and voice guidelines: how the product talks (tone, terminology, what an error message is allowed to say). Without this, every team member writes UI copy in their own voice.
- Accessibility rules built in, not bolted on: contrast ratios, focus states and keyboard behaviour that are correct by default in the component, so using the system correctly makes a screen accessible almost by accident.
- Every surface, including paper: tokens and components should hold up on the surfaces teams forget, like email, PDF export and print. Our own print rules (page numbers, exact brand colours, headings that stay with their text) are part of the system, and we’ve written up how that works.
- A governance model: who can propose a new component, how a change gets reviewed, what happens when a team needs something the system doesn’t have yet. A design system with no way to evolve calcifies within a year.
Skip the last four and what you have is a component library: useful, real, worth having. But it won’t stop two teams solving the same problem two different ways, because a library has no opinion about when or why to use what’s in it. That opinion is the actual point of a design system.
Why it’s needed
Every product decision made without a system gets made from scratch, by whoever’s doing the work that day. That’s fine at small scale, and it’s genuinely fast. Past a certain point it becomes the opposite of fast: the same button rebuilt slightly differently three times, a new hire with no way to know which of four existing patterns to reuse, an accessibility fix that has to be applied one screen at a time because there was never a single component to fix once. A design system trades a bit of upfront discipline for a lot of avoided rework, later, at a point where rework is far more expensive than it would have been early.
When it’s needed
Not at a fixed headcount, but at the point you can point to specific, repeated rework a shared system would have prevented. We’ve written a longer, practical breakdown of that by team size if you want the detailed version; the short version is that building one too early just means rebuilding it once the product stops changing shape, and building one too late means paying interest on months of inconsistency first.
What one looks like in practice
Our own is public. Somnia DS is the design system this website is built from, documented in full: tokens in light and dark, live components, patterns, accessibility rules and the governance that keeps it in shape. It also carries four brands on the same components, and its theme builder generates a fifth from any two colours you give it, contrast-checked, which is the clearest demonstration we know of why tokens matter.
The mistake worth avoiding
Treating a design system as a one-off deliverable (a Figma file handed over, a component library shipped, done) rather than a living product with its own users (your own team) and its own maintenance cost. The systems that actually earn their keep are the ones someone owns, revisits, and is allowed to say no in. Not every new pattern deserves to join the system, and a system that accepts everything stops being one.
Weighing up whether to build a design system, or whether what you actually need is something smaller? Get in touch for a straight answer.
See a design system working
Somnia DS is the design system this website runs on, published in full: tokens, components, patterns, accessibility and governance. We build systems like it for clients, prototype on it, and host and look after the documentation for you.
Same components, different brand: