The pattern
You hired experienced people. You delegated. You told your leadership team you trusted them to make decisions. And yet, somehow, the important ones still end up with you.
A hire that needs sign-off. A pricing call that requires your input. A customer escalation that only you can resolve. A strategic trade-off between two functions that has been sitting unresolved for three weeks because neither side wants to make the call without you.
The calendar fills with decisions. The team gets slower. You get busier. And the company — despite growing — starts to feel less in control, not more.
This is the founder bottleneck. And it is one of the most common, most costly, and most misdiagnosed operating problems in scaling companies.
Why it gets misdiagnosed
The instinctive diagnosis is a time management problem. The founder needs to delegate better, say no more often, protect their calendar, be more disciplined about which meetings to attend.
This diagnosis is wrong — or at least incomplete. Time management is a symptom. The disease is structural.
The founder is the decision bottleneck because the organisation has not built the system that would allow decisions to be made without them. Not because the founder is controlling. Not because the team lacks capability. But because nobody has done the work of making decision ownership explicit.
Without a defined decision architecture, every ambiguous decision defaults upward — to the most senior person available. In a founder-led company, that is always the founder.
This is not irrational behaviour. It is the logical outcome of an operating model that has never specified who owns what, at what threshold, with what authority.
How it develops
In the early stages, founder centrality in decisions is not just acceptable — it is correct. A five-person company with a founding team in the same room does not need a decision rights framework. Speed and alignment come from proximity. The founder’s judgment is the operating system.
Then the company scales. Fifteen people become thirty. Thirty become sixty. New functions are added — finance, operations, marketing, customer success. Leaders are hired to run them. The org chart expands.
But the decision model does not evolve at the same pace.
The implicit expectation — that the founder will be involved in important decisions — was never formally updated. There are no explicit rules about which decisions each leader owns outright, which require consultation, and which require escalation. So when an important decision arises, the default is to involve the founder. Not because the leader cannot make the call, but because there is no documented authority that says they can — and in the absence of that authority, the path of least resistance is upward.
The founder, meanwhile, has hired capable people precisely to make these decisions. The frustration is mutual. The cause is structural.
What decision rights actually means
Decision rights is a term that sounds bureaucratic and feels abstract until you see what happens when they are defined. Then it becomes obvious.
Decision rights define, explicitly, three things for every category of operating decision:
Who decides. Not who is consulted, not who should be informed — who makes the call. One person, named, with the authority to decide and the accountability that follows from it.
What threshold changes the answer. Most decisions have a scale dimension. A hire under a certain salary band is made by the function head. Above that band, it requires CFO sign-off. Above a higher threshold, it requires board approval. These thresholds are not arbitrary — they reflect the financial impact and reversibility of the decision. When they are defined explicitly, the escalation path is clear and the ambiguity disappears.
What information is required to decide. Many decisions get escalated not because the leader lacks authority, but because they lack the information they need to decide with confidence. Defining the information requirements for a decision class — and making that information routinely available — removes a second category of unnecessary escalation.
None of this requires a management consultant or a six-month organisational design project. It requires a structured conversation about the operating decisions that matter and a written record of who owns each one.
The decisions that need defining first
Not every decision needs a formal rights framework — routine operational calls should be made by whoever is closest to them. The decisions that create founder bottleneck are a specific, identifiable set.
People decisions. Hiring, firing, performance management, and promotion. These are the decisions most commonly escalated to founders because their impact is high and their reversibility is low. Every people decision above a certain level should have a defined owner and a defined threshold.
Commercial decisions. Pricing, discounting, contract terms, and customer exceptions. These decisions recur constantly in a scaling business. Without explicit ownership, every exception becomes a founder decision — and a commercial operation that generates multiple exceptions per week will consume a disproportionate amount of founder time.
Resource allocation. Budget approvals, headcount additions, and investment in new initiatives. These decisions are often escalated not because the founder needs to approve them, but because the criteria for approval have never been made explicit. Defining the criteria — not just the threshold — allows leaders to pre-qualify decisions before they reach the escalation point.
Cross-functional trade-offs. The decisions that create the longest bottlenecks are those where two functions have competing interests and neither has the authority to resolve the conflict. Sales wants to extend a customer’s payment terms. Finance wants to protect cash. Neither function head has the explicit authority to overrule the other. The decision sits, unresolved, until the founder steps in.
This category of decision — the cross-functional trade-off — is the one that most requires explicit ownership. Defining which function leads on which category of trade-off, and what the escalation path is when functions cannot agree, eliminates the most persistent source of founder bottleneck.
What changes when decision rights are defined
The change is not primarily about the founder’s calendar, though that improves. The more important change is in how the organisation moves.
Decision velocity increases. Decisions that previously took two weeks of informal escalation take two days. Not because people are working harder, but because the path to a decision is clear and nobody is waiting for permission to take it.
Accountability sharpens. When decision ownership is explicit, the connection between a decision and its outcome is direct. The person who made the call owns the result. This is not punitive — it is the operating condition under which people develop genuine judgment rather than institutional caution.
The founder’s attention shifts. When routine and mid-level decisions are genuinely owned by others, the founder’s involvement concentrates on the decisions that actually require their judgment — strategic, irreversible, high-stakes. This is where founder attention has highest leverage. Recovering it from the operational backlog is one of the most valuable things a scaling company can do.
The organisation builds capability. Leaders who are genuinely empowered to make decisions develop faster than leaders who are nominally empowered but practically dependent on founder approval. Decision rights are not just an efficiency mechanism — they are a leadership development mechanism.
The diagnostic
Four questions identify the problem quickly:
- In the last month, how many decisions that were made by you could have been made by a direct report if the authority had been explicit?
- When a cross-functional disagreement arises between two of your leadership team, what is the defined process for resolving it — and does that process work without your involvement?
- Does each of your direct reports know, specifically, which decisions they own outright, which require consultation, and which require your sign-off?
- When a decision gets escalated to you, is it because it genuinely requires your judgment, or because the ownership was unclear?
If the honest answers are uncomfortable, the operating model has a decision rights gap. And that gap will widen as the company grows — because the volume of decisions scales with complexity, and a system that cannot distribute decision ownership breaks under that volume.
Why this matters for everything else
Decision rights are not a standalone operating fix. They are the foundation on which the rest of the operating model works.
A leadership cadence only functions if the leaders in the room have genuine authority to make the calls the cadence requires. A metrics hierarchy only drives behaviour if the people reviewing the metrics can act on what they see. An accountability loop only closes if the owner of the variance has the decision authority to correct it.
Without explicit decision rights, every other operating mechanism degrades. Leaders review but defer. Actions are assigned but not owned. The cadence produces recommendations rather than decisions.
Defining who decides what — written down, specific, and maintained — is not a constraint on leadership judgment. It is the infrastructure that makes judgment usable at scale.
Defining explicit decision rights across three newly acquired businesses — each with different leadership cultures, informal authority structures, and competing interpretations of who owned what — was one of the first operational moves in the post-acquisition integration. The detail is in the multi-acquisition integration case study.