“We need a design system” is how half of failed internal projects begin. A system for its own sake eats months and dies without maintenance. Let us look at when it actually pays off.
Honest math
A design system is expensive: 3–6 months of a team's work for v1, plus permanent support — roughly 20% of one designer's and one engineer's time. Payback comes when reuse savings exceed those costs.
When the system pays off
- Three or more product teams work with one brand
- The product lives on several platforms: web, iOS, Android
- Interfaces ship more often than once a month: promos, landings, features
- The team spends over 20% of its time re-drawing the same things
In the platform for 14 sub-brands the system paid off within two campaigns: landing assembly went from three weeks to a day.
When it is too early
One product, one team, rare releases — a UI kit is enough: a Figma component library with tidy tokens. A full system with documentation, Storybook and a contribution process would be overhead.
Tokens are the foundation, components the roof
Start with tokens: color, typography, spacing, radii. They are cheap to maintain and deliver 60% of the consistency effect. Build components as patterns repeat: the third use of a pattern is the signal to extract it.
A system without process is dead
The main cause of design system death is not technology but the absence of an owner. A system needs a maintainer, a change process and regular releases. Otherwise teams go back to copying mockups within six months.
Unsure whether your product needs a system? A process audit answers in numbers within two weeks.