Getting started with design systems
This is one of those topics that looks small until it costs you something. A short on-ramp to design systems for teams who have not touched it before.
The measurable part of design is whether people can find what they came for and act on it without hesitating. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
The reason this keeps coming up
A shared component set stops every page reinventing the same button. Where this goes wrong is almost never a lack of knowledge. It is worth deciding this deliberately rather than inheriting whatever the last person set up.
Your first week
- Find out what is already in place
- Tokens for colour, spacing, and type keep decisions consistent
- Change one thing and measure it
The system pays for itself around the third or fourth page. The teams that handle this well are rarely the ones with the biggest budgets. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.
In practice
Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Three things worth confirming about design systems before you move on:
- Someone can say what the current setup is without going to look
- A shared component set stops every page reinventing the same button — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If you are not sure where your systems currently stand on this, it takes us about an hour to find out.