When design systems is worth the effort

The advice here is unglamorous, which is probably why it gets skipped. Design systems is not free, and pretending otherwise leads to bad decisions.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

When it is worth it

A shared component set stops every page reinventing the same button. 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.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. That sounds obvious written down. It is still the thing most often skipped.

How to decide

The system pays for itself around the third or fourth page. Where this goes wrong is almost never a lack of knowledge. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

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

Worth checking on your own setup before it becomes someone else's problem to fix.