A short guide to design systems

Most teams know this matters. Fewer have decided who owns it. Everything we would tell a client about design systems in the time it takes to drink a coffee.

The measurable part of design is whether people can find what they came for and act on it without hesitating. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

What it costs to ignore

A shared component set stops every page reinventing the same button. In practice this is a scheduling problem more than a technical one. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

How we handle it

Tokens for colour, spacing, and type keep decisions consistent. The cost of getting this wrong is rarely visible on the day it happens. Check it against what you would want a competitor's site to get wrong.

The mistakes we see most

The system pays for itself around the third or fourth page. This is the sort of thing that compounds, quietly, in both directions. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

The short version

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

If any of that sounds like a description of your current setup, it is fixable.