Design systems are one of those things that get recommended as a universal best practice, regardless of whether the team asking about one actually needs it yet. Sometimes the honest answer is: not yet, and building one now would slow you down.

Solo founder or pre-product-market-fit

Probably not yet. At this stage the product itself is still changing shape. Colours, components and patterns are still being figured out through use, not standardised. A design system built here usually gets rebuilt within a few months anyway, once real usage shows what actually needed to be consistent. The better investment is a small, loose set of shared styles, not a documented system.

Small team, one or two products, shipping regularly

Getting close. This is usually where the pain starts to show up in a specific way: the same button gets rebuilt slightly differently three times, or a new screen takes longer than it should because nobody’s sure which spacing or component to reuse. That’s the actual signal: not team size on its own, but repeated, avoidable rework. A lightweight system covering the components actually being reused is worth the investment here.

Scaling team, multiple products or a growing design team

Yes. Once more than a couple of people are shipping UI, an undocumented set of conventions stops being enough. Decisions that used to happen by osmosis in one person’s head now need to be written down so a new designer or engineer can find them. This is also the point where the system pays for itself fastest, because the cost of not having one (inconsistency, duplicated components, slower onboarding) is now being paid repeatedly, by more people.

The actual test

The right moment depends less on headcount than on whether you can point to specific, repeated rework that a shared system would have prevented. If you can’t point to a concrete example yet, it’s probably still too early.

Not sure whether your team’s at the point where a design system pays for itself? Get in touch and we’ll give you a straight answer, even if it’s “not yet.”

See a design system working

Somnia DS is the design system this website runs on, published in full: tokens, components, patterns, accessibility and governance. We build systems like it for clients, prototype on it, and host and look after the documentation for you.

Same components, different brand:

← Back to all insights