Menu

Let’s make something matter.

hello@arevian.studio
All articles

Why a business needs a design system — and when it does not

Arevian Studio

A design system saves money not by being pretty but by making every next screen faster than the last. Below a certain size, though, it is just cost.

A design system is not a brand book and not a library of pretty buttons. It is a set of decisions made once: what spacings exist, what a dangerous action looks like, how a field shows an error, how many heading sizes there are. After that every new screen is assembled from decisions instead of inventing them again.

What it saves

  • Designer time: no re-deciding what is decided
  • Developer time: the component exists and is already tested
  • Review time: arguing about the system, not about taste
  • Rework money: consistency does not have to be imposed later

The last line is the expensive one. A product grown without a system looks like five products after a year: every section with its own spacing, buttons and logic. Unifying that costs more than the system would have.

The size at which it pays

A rough threshold: three people, or twenty screens. While one designer and one developer ship a site in a month, a system will not pay for itself — the decisions already live in one head.

A system is needed where decisions have to be handed over. Until they are, it is documentation for its own sake.

What a minimal system contains

  • Colours by role: not "orange" but accent, danger, background
  • A type scale: a limited set of sizes, not arbitrary numbers
  • A grid and one spacing step
  • States: hover, press, loading, error, empty
  • Components: button, field, card, dialog, table

Notice what is missing: illustration, motion, mood. Those matter too, but they are a layer on top, not the foundation.

How not to turn it into a graveyard

The real danger is a system that was started and then stopped being updated. Six months later developers stop opening it, because half the components no longer match the live product. The rule that works: the system changes in the same change as the product, or the change is not accepted.

The second rule: a system needs an owner. Not a responsible team — a person people go to with "how do we do this". Without one, a system becomes three systems within a year, which is worse than none.

Read next

All articles
Next step

Always in touch.

Tell us about your project, and we'll think about how to make it stronger.

hello@arevian.studio
Office in YerevanOpening Soon…
Email for sales:hello@arevian.studio