The real cost of ignoring design systems
This is one of those topics that looks small until it costs you something. Nobody bills you for neglecting design systems. The cost shows up somewhere else.
The measurable part of design is whether people can find what they came for and act on it without hesitating. Assume whoever inherits this will have half your context and none of your patience.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- A shared component set stops every page reinventing the same button
- Rework, once the problem is finally visible
Tokens for colour, spacing, and type keep decisions consistent. There is a version of this that is over-engineered, and it is worth avoiding. It rarely shows up as a line item, which is exactly why it slips.
Turning this into a decision
The system pays for itself around the third or fourth page. The cost of getting this wrong is rarely visible on the day it happens. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
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
- The system pays for itself around the third or fourth page — 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.