Canonical definition
What is the founder bottleneck?
The founder bottleneck is the structural pattern where decisions, approvals, and exception calls concentrate on the founder's desk. It persists after hiring because approval authority did not transfer with the role. The seat changed; the deciding right did not.
In one sentence
The pattern where every consequential call routes to one desk by default.
What this means for the owner
If every exception waits for you, the first thing to inspect is not workload. Check decisions, approvals, context, escalation paths, client memory, and standards. The business may be using you as the operating system.
Do not start with another hire, another tool, or a stronger delegation speech until the authority transfer is clear.
What it actually does
The bottleneck shows up across four authority surfaces:
- Hiring authority. Senior offers route to the founder for review and sign-off, regardless of who built the hiring loop.
- Spending authority. Discretionary spend over a threshold collects on the founder's desk even when the threshold is below market discretion.
- Customer-escalation authority. Top-customer exception requests route to the founder rather than the account owner.
- Exception authority. Anything outside the policy returns to the founder for the call, even when the policy is fuzzy enough that exceptions should be the manager's domain.
What it is not
- Not a workload problem. Hours will not catch up. The system produces the bottleneck independent of effort.
- Not a personality problem. The pattern is structural. A different founder in the same structure produces the same bottleneck.
- Not a hiring problem. Hiring good people does not remove the bottleneck if authority does not transfer with the role.
- Not a process problem alone. Better processes help, but the deciding question (who carries the call?) is upstream of process.
- Not a delegation problem alone. Delegation that hands the task but retains the standard is not delegation. It produces the same bottleneck under a different name.
Three common patterns
Pattern 1
The senior hire that disappeared.
A senior hire appears to own the operating cadence, but exceptions still return to the founder. The role exists. The authority transfer is incomplete.
Pattern 2
The exception that became the rule.
A customer exception gets approved as a one-off. Then similar exceptions keep coming back. The policy did not move because exception authority still sits with the founder.
Pattern 3
The spending threshold that nobody respected.
Managers had a written spend limit but still routed ordinary invoices back to the founder. The threshold was not the issue; the trust transfer was incomplete.
When to use it
Recognise the founder bottleneck when:
- Your team waits for you to decide things you could not possibly remember in detail.
- You have senior hires who escalate exceptions you wish they would handle.
- You hired good people but you are still the constraint.
- Your calendar collects routine approvals before they can move.
- Vacations produce phone calls that cannot wait.
The bottleneck framing is wrong when:
- The founder is intentionally in every decision (small studio, single-name advisory).
- The pattern is actually owner dependence at the structural level, not daily operational bottleneck.
- The team escalates because the policy is genuinely fuzzy, not because authority is unclear.
Common questions
- What removes a founder bottleneck?
- Four authority transfers in sequence: hiring authority, spending authority, customer-escalation authority, exception authority. Each transfer needs a named receiver, a stated standard, and a non-reversal commitment from the founder.
- Why doesn't hiring senior people fix it?
- Senior hires get the title but often not the rights. The structural authority must transfer alongside the role. Without that, the receiver is a more expensive version of the same bottleneck.
- How long does it take to remove?
- Three to twelve months depending on starting maturity. The slow part is the founder's non-reversal commitment, not the authority transfer itself.
- Is the founder bottleneck the same as owner dependence?
- Related but distinct. The founder bottleneck is the daily operational version. Owner dependence is the structural valuation version. Fixing one often surfaces the other.
- When should an owner bring this into Business Problem Review?
- When decisions, approvals, and exceptions still collect on the owner after hiring or delegation. Bring the repeat escalations, decision list, approval thresholds, and examples of work that stops without you.