Design systems, explained without the jargon

Teams tend to reach for this after something has already gone wrong. Here is design systems without the vocabulary that usually surrounds it.

The measurable part of design is whether people can find what they came for and act on it without hesitating. Doing this properly once is usually cheaper than doing it approximately three times.

The short version

A shared component set stops every page reinventing the same button. That sounds obvious written down. It is still the thing most often skipped. Check it against what you would want a competitor's site to get wrong.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The teams that handle this well are rarely the ones with the biggest budgets.

Tokens for colour, spacing, and type keep decisions consistent. None of that requires a large budget, only a decision and someone to own it. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

A reasonable first step

The system pays for itself around the third or fourth page. Where this goes wrong is almost never a lack of knowledge. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

How to tell if yours is fine

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Three things worth confirming about design systems before you move on:

• Someone can say what the current setup is without going to look
• Tokens for colour, spacing, and type keep decisions consistent — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.