A design system should know when to disappear.

Design systems · 05.02.2025 · 5 min read

There is a version of design systems work that produces consistency at the cost of character. Every screen looks related to every other screen — the same spacing, the same components, the same feel — but nothing feels quite right for the context it is in.

The problem is not the system itself. It is the assumption that a system should do the same thing everywhere. Good design systems are more like grammars than templates. They give designers the rules and the vocabulary to communicate clearly, not a set of fixed sentences to repeat.

When a design system is working, you do not notice it. The interface feels natural for the context — dense and efficient in a data table, generous and considered in an onboarding flow. The system is invisible because it has done its job: it has enabled the right decision in each situation rather than imposing the same decision in all of them.

"A design system that forces sameness has mistaken uniformity for coherence."

The most powerful component in any design system is the permission it grants designers to deviate when the situation demands it. Not permission to ignore the system, but permission to extend it thoughtfully. That requires the system to be principled rather than prescriptive. It needs to say "this is why we do this" rather than only "this is what to do".

Build your system around intent, not implementation. Document the reasoning, not just the rules. A design system that can explain itself is one that can evolve without breaking.