How to get design systems right
The advice here is unglamorous, which is probably why it gets skipped. The short answer to design systems is that it is mostly a sequence of small decisions, not one big one.
Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.
Why this earns attention
A shared component set stops every page reinventing the same button. That sounds obvious written down. It is still the thing most often skipped. Budget a little time for it every quarter and it never becomes a project of its own.
The steps
- Establish what you have today before changing anything
- Tokens for colour, spacing, and type keep decisions consistent
- The system pays for itself around the third or fourth page
- Write down the decision so the next person does not re-litigate it
The system pays for itself around the third or fourth page. This is the sort of thing that compounds, quietly, in both directions. It rarely shows up as a line item, which is exactly why it slips.
What to do next
What this looks like day to day
The measurable part of design is whether people can find what they came for and act on it without hesitating. 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
Most of the value here comes from doing the first two things, not all of them.