A team can triple in size and produce less than it used to. The cause is almost never the new hires - it's that the founders are still operating with founder-era decision rights. Here's how to spot it and what to do about it.
The single most common cause of stalled scale in growth-stage companies is invisible on the org chart and undetectable in the metrics dashboard. It looks like a productivity problem, gets diagnosed as a hiring problem, and is almost always a founder problem in disguise.
I have seen this pattern often enough to give it a name: the founder bottleneck. A company triples its headcount over fourteen months. The new hires are senior, well-paid, well-credentialled. The org chart looks impressive in the next board deck. And then, six months later, output is flat or declining and nobody can quite say why.
Everyone has a theory. Hiring quality has slipped. Culture is diluting. The new managers are too process-heavy. Some of this is occasionally true. None of it is usually the actual cause. The actual cause is that the company hired senior people to scale and is still operating with founder-era decision rights, which means most of the new senior hires can't actually decide anything.
The math of a slow collapse
Imagine a 20-person company where every meaningful decision flows through three people: the CEO and two co-founders. Decisions per week, total, is whatever those three calendars can hold. Call it sixty. The company produces output proportional to those sixty decisions getting made.
Now scale the company to 80 people. You have hired four VPs and twelve senior managers. Output should, in principle, scale roughly with headcount. It doesn't, because all meaningful decisions still flow through the same three calendars, which still produce sixty decisions per week. The company is now running 80 people on sixty decisions, which is to say it's running 80 people on the throughput of three calendars.
The VPs you hired are senior, expensive, and bored. They were brought in to lead, then handed roles where they cannot actually decide. The most polite ones go quiet in meetings. The least polite ones leave inside twelve months. Either way, you have spent a lot of money to scale a number on the cap table without scaling the throughput of the business.
Why founders do this
Founders don't bottleneck their companies on purpose. Almost every founder I have worked with on this problem can articulate, in theory, the importance of delegation. They believe in it. They have read the books.
What they cannot do, in practice, is sit through a decision being made worse than they would have made it themselves, by the person they hired specifically to make it. This is the moment everything turns on. The founder steps in once. Then twice. Within six weeks, the new VP has learned that decisions in their domain are made by the founder, regardless of what their offer letter said.
The fastest way to teach a senior hire that they don't actually own their function is to overrule them in their first big decision in front of their team.
The other variant is more passive but equally damaging: the founder doesn't overrule the VP, but everyone in the company has learned that decisions made without the founder's involvement get unwound later. So nobody makes them. Every meaningful conversation routes back to the founder's calendar, regardless of what the formal org chart says.
The symptoms you'll see first
Founder bottlenecks rarely announce themselves directly. They show up as adjacent symptoms that get diagnosed individually and treated, ineffectively, in isolation:
- Top performers go unusually quiet in meetings, especially the ones they were hired to lead.
- Cross-functional initiatives stall at the executive layer rather than the working-team layer.
- The same questions keep coming back to the founder, often from people three layers removed from them.
- eNPS holds up, but exit interviews from senior leavers all say a version of “I didn't have the autonomy I expected.”
- Velocity drops on initiatives the founder isn't directly tracking; velocity holds on the ones they are.
Any one of these has a hundred possible causes. All of them together, in a 60-150-person company, is the founder bottleneck.
What works (and what doesn't)
The interventions that fail share a common shape: they try to fix the problem by talking about it. Off-sites about “empowering leadership”. New values posters about ownership. A reorg that moves boxes around without changing who decides what. None of these touch the underlying mechanism, which is the founder's behaviour in specific moments.
The interventions that work are structural and behavioural in equal measure:
1. An explicit decision-rights map
Catalog every recurring decision in the company - not by department, but by type. Pricing changes. Hiring approvals over a threshold. Brand changes. Architecture choices. Roadmap commitments. Then explicitly assign each one to a role and a level, not a person. The map will surface a dozen decisions the founders are still making by default that everyone agrees should sit elsewhere. Move them, in writing, and circulate the result.
2. A weekly “where did I show up?” audit
For one quarter, have the founders log every meeting they attended and every decision they participated in, then categorise each one as “I should have been there” or “I was in the room because nobody else felt empowered to be.” The second column will be embarrassing in the first month and instructive in the third. Behaviour change requires data the founders can't argue with.
3. The visible non-intervention
When a senior hire makes a decision the founder would have made differently, the founder lets it stand - visibly. They don't reverse it later. They don't litigate it in 1:1s. They might disagree explicitly, in writing, and explain what they would have done. But the decision lands as the VP made it. This is the moment that changes behaviour throughout the company, and there is no substitute for it.
4. Reframe what the founder does
Pitch the change to the founders not as “you are doing too much” but as “the company needs you to do different work.” At 20 people, the founder's job is to make every key call. At 150, the job is to set context, raise the quality of the calls being made elsewhere, and decide the two or three things that genuinely require their judgement. These are different jobs and the second one is harder.
What good looks like, twelve months in
A company that has worked through this transition feels noticeably different. The founders are in fewer meetings. The meetings they attend are higher-altitude - strategy, priorities, the few specific decision categories they own. Decisions get made closer to the work, by the people doing the work, and they get made faster.
Critically, the senior hires who were quietly looking six months ago are now visibly leading. They are running their domains, making calls the founders wouldn't have made, and - in some percentage of cases - making calls the founders think are wrong. The founders are letting it happen anyway, because they have understood, finally, that this is what scaling actually feels like. It's not delegation as a virtue. It's delegation as the only mechanism by which an organisation past a certain size can produce output proportional to its headcount.
The founder bottleneck is, in the end, a story about the gap between what an org chart claims and what a calendar reveals. The good news is that closing the gap doesn't require new hires, new tooling, or a new offsite. It requires the founders to do less of the work that built the company in the first place. That is the hardest skill they will be asked to learn. It is also the only one that scales.
