Growth doesn't fix the bottleneck. It multiplies it. Here's why — and what actually stops it.
Most founders assume that hiring is how you solve a decision bottleneck. More people means more capacity, which means decisions can be made faster and lower down. That's the logic. And it's wrong.
What actually happens is this: every new hire adds one more person who needs a decision made for them — or made near them — before they can move. If the decision-making system was already broken before they arrived, they don't improve it. They join it. And now there are more people waiting.
The team isn't waiting because they lack confidence. They're waiting because nobody built the path that lets them move without asking.
The pattern we see consistently is this: a business grows from eight to twenty people and the founder becomes more involved in decisions, not less. They assumed growth would distribute the load. Instead it concentrated it — because every new hire added one more dependency on the founder before work could move.
This isn't a people problem. The hires are usually capable. It's a structural problem: the system was never built to route decisions anywhere other than up.
When a founder is making every decision themselves, the friction is visible. They feel it. The time cost is personal. At some point the pain becomes acute enough to hire someone — often a manager or a senior person who's supposed to "own" an area.
But ownership without authority is just responsibility with no tools. The manager arrives, takes the title, and then discovers that the decisions still route to the founder. Not because the founder doesn't trust them. Because there's no written agreement about what they're actually allowed to decide.
So the manager does what any reasonable person does: they ask. And the founder answers. And the pattern continues, now with an additional layer of indirection.
The headcount grew. The decision load didn't shift. It just acquired a middleman.
Ownership without authority is just responsibility with no tools.
The fix is not to push the founder out of decisions. That usually creates a different kind of chaos — work moving in directions the founder didn't sanction, errors surfacing late because nobody looped them in on things that actually needed their view.
The fix is to build the system that routes decisions correctly in the first place. A Decision Rights Framework. Written authority thresholds by role. An explicit, documented permission for the team to move without asking — on the things they're allowed to move without asking on.
Once that exists, the load distributes naturally. Not because people suddenly feel empowered. Because they know, in writing, what they're allowed to do. The ambiguity is gone. The escalation path is defined. And the founder is only in the loop on the things that actually need them.
Decision rights frameworks fail for the same reason SOPs fail: they're written once and then ignored. The document exists. The behaviour doesn't change.
The version that works is the one that gets embedded into the operating cadence — reviewed in the weekly sync, referenced when a new decision type comes up, updated when the business changes shape. It becomes the first place people look when they're uncertain, not a document that lives in a folder nobody opens.
The test is simple: can any person in your business, right now, tell you what decisions they're allowed to make without asking? If the answer is no, the system doesn't exist yet. And every hire you make before you build it makes the problem one person larger.
Every engagement starts with a diagnosis. A clear look at what's breaking and what it would take to fix it — before we scope anything.