Headcount isn't a design strategy

Every scale-up hits the same moment. Design's been keeping up fine, one person, maybe two, making most of the calls. Then growth kicks in. Suddenly design's the bottleneck, and the instinct is obvious: hire more designers.

It rarely works the way anyone hopes.

More people, same problem, just louder

Add two designers to a team with no defined workflow and you don't get more output, you get more opinions. Before, one person made the calls, inconsistent maybe, but at least fast. Now three people are making calls with no shared process for who decides what, and everything slows down while they work it out in real time, usually mid-project.

Headcount was never the actual problem. It was standing in for a workflow that didn't exist yet.

What to sort before you hire

Three questions matter more than the number on the job req:

Who reviews what. Not everyone needs to review everything. Without clear ownership, every decision becomes a meeting.

Who has final say when there's disagreement. Someone needs it. Not to shut down debate, but so debate has an endpoint.

How design connects to product and engineering. This needs deciding before the work starts, not patched in after a launch goes sideways.

Get these three right and the right headcount becomes obvious. A team of two with a clear workflow will often out-produce a team of five without one.

Where AI actually changes this

AI doesn't remove the need for these decisions, if anything it raises the stakes. A designer using AI well can produce exploration and iteration far faster than before. Without a workflow to catch and direct that output, speed just means more unreviewed work piling up faster.

Used well, AI is leverage for a team that already knows how it operates, not a substitute for figuring that out.

The actual fix

Define the workflow first. Then hire into it, not the other way round. It's less exciting than a hiring plan, and it's the difference between a design team that scales and one that just gets bigger.