It is an odd thing for a studio that builds design systems to say, but most small product teams do not need one yet. They need a few shared decisions and someone who owns them.
A design system is a product with its own users, its own backlog and its own maintenance. It pays for itself when several people make interface decisions without talking to each other. Before that point it is overhead: a library nobody consumes, documentation nobody reads and a governance process with nothing to govern.
The tipping point
If you have one product and two designers, you probably do not need one. The designers already talk. The inconsistencies are visible to the people who could fix them, and fixing them is a conversation rather than a process.
The tipping point is usually the third team shipping screens nobody else reviews. At that point the conversation stops scaling. Decisions get made twice, slightly differently, and nobody sees both.
Signs you have reached it
- The same component exists more than once, and nobody can say which one is right
- Engineers ask designers for values that should already be written down
- A change to the brand colour means a search through the codebase
- New screens are built by copying old ones, mistakes included
- Review is the only thing holding the product together, and review has become the bottleneck
What to do before then
Write down the handful of decisions everyone is already making: colour, type, spacing and the few components every screen uses. Keep them in one place that design and code both read from, and name one person who owns it. This is the part of a design system that pays off on day one, and it is what a system would later be extracted from.
The cost of waiting too long
The trade-off runs both ways. A greenfield system for one product is fast. Extracting a system from four years of accumulated screens is not. Every month past the tipping point adds screens that will have to be reconciled, and the reconciliation is the expensive part.
So the question is not whether you need a design system. It is whether shared decisions can still survive on conversation alone. If you are not sure which side of that line you are on, that is what an audit is for.