At some point, most product organisations make the same hire. A designer who is good. Then another, because the first one is stretched. Then a team lead, because no one is aligned. Then a head of design, because the team lead cannot get time with the CPO.

And the product still feels inconsistent.

Decisions still take too long. Every new feature opens a fresh debate about what the button should look like, whether this interaction matches that one, why mobile feels different from web. The diagnosis is always the same: we need more designers.

It is the wrong diagnosis.

The bottleneck is rarely headcount

A design team without a system is a group of individuals making independent decisions at pace. Each one capable. Each one, under pressure, solving the problem in front of them rather than the pattern underneath it.

The result is experience debt. Not broken UIs. Not obvious inconsistencies. The quieter kind that accumulates across a hundred small decisions no one thought to align on. It compounds invisibly until a researcher surfaces it, or a competitor makes it obvious, or a new leader walks in and asks why the product feels like three different companies built it.

Adding more designers accelerates this. Each new hire adds more decision-making surface, more variation, more places where the system should have spoken but didn't.

You are not solving the bottleneck. You are widening it.

What a design system actually is

Not a component library. Not a Figma file with a colour palette and a button in five states.

A design system is an organisational decision made once, deployed everywhere. It is the answer to a question that would otherwise be asked, and answered differently, a hundred times a year.

When I built the Imagine design system at Housing.com, the goal was not consistency for its own sake. It was to free the team to spend its judgement on decisions that had not already been made. Eighty-plus components. A token architecture that meant a colour decision propagated everywhere it needed to. A single typeface doing the work of three without the noise.

The measure of a good design system is not how beautiful it is. It is how rarely you have to think about it.

The compounding argument

Finance understands compounding intuitively. Design leadership rarely talks about it.

A design system is capital. Invest in it once, seriously, and it returns value on every build that follows. The second feature built on the system is faster than the first. The tenth is faster still. Review cycles shorten. Inconsistencies become exceptions.

At Housing.com, the return was not in the components. It was in what the components made possible: multi-iteration within compressed timelines, explorations that started at the strategic question rather than working up to it. When you are not debating what a card looks like, you are debating what the card should do.

That is the conversation that moves products forward.

The leadership responsibility

If you lead a design function without a working system, your team is spending significant capacity on decisions that have already been made. Or should have been.

This is not a craft failure. It is a leadership failure.

Systems do not build themselves. They require someone who treats design infrastructure as the work, not a distraction from it. The organisations that understand this do not ask for more designers. They ask for better systems. And then they find the team they already have can do far more than they thought.

You do not have a design problem.

You have a systems problem.

And it has a solution that is not a headcount request.

Where in your product are independent decisions quietly replacing a system that should exist?