Back to Insights
Leadership

The Founder Bottleneck Is a Decision Bottleneck

By Abdul Kunateh · 3 min read · October 20, 2026

Decisions Sit on Two Axes

Every decision in a business can be placed on two axes: how much it costs to get wrong, and how hard it is to undo. A founder bottleneck forms when decisions that score low on both of those axes still have exactly one person who is allowed to make them, regardless of their actual stakes.

This is a decision-rights problem, not a time-management problem. Hiring another person does not fix it if every meaningful choice still has to pass through one desk before anything moves. A founder's calendar full of approvals is the symptom. The cause is that decision rights were never explicitly assigned anywhere else.

Setting Thresholds, Not Just Categories

A general category like "purchasing decisions" or "hiring decisions" is too broad to act on. What actually moves authority off a founder's desk is a specific number attached to a specific type of decision: a dollar amount, a discount percentage, a refund ceiling, a headcount limit for a single role. Below the threshold, the decision belongs to someone else outright. Above it, it still comes to the founder.

Picture a hypothetical four-location retail business where the owner currently approves every refund personally. A workable threshold might read: store managers can approve refunds up to a stated amount without checking in; anything above that amount, or anything involving a repeat complaint from the same customer, comes to the owner. The number does the work that a vague instruction like "use your judgment" cannot, because it tells the manager exactly where their authority ends.

What Input a Decision Requires

Not every decision below a threshold should be made in total isolation, and not every decision above it needs the founder to decide alone. A decision right should specify not just who decides, but what input, if any, is required first. A manager might be able to approve a vendor substitution alone, but be required to check current inventory levels before doing so. A founder might retain final say on a new senior hire, but be required to get input from the two people that hire would work most closely with before deciding.

Separating the question of who decides from the question of what input is required avoids two common failure modes: decisions made alone that should have included someone with relevant context, and decisions that stall because "input required" quietly became "approval required" without anyone saying so directly.

What Happens When a Decision Gets Deferred

A decision right that exists only on paper is tested the first time someone is unsure whether a situation falls inside or outside their threshold. What happens next determines whether the right holds. If the default response to uncertainty is to kick the decision upward, the threshold has effectively been withdrawn, because people will always resolve ambiguity by asking rather than by risking a wrong call.

A more durable rule treats deferral as a specific, named event rather than a silent default: a deferred decision gets a stated reason, a stated deadline for resolution, and a record of who it is now waiting on. Decisions that drift without any of those three tend to sit unresolved far longer than anyone intended, quietly reverting to whoever is willing to finally make the call under pressure, usually the founder.

Writing the Rights Down

None of this requires a lengthy governance document. A short, living list, one line per decision type, naming the threshold, the required input if any, and who holds the right above and below that line, is enough to start. The list will be wrong in places at first. That is expected, and far more useful than no list at all, because a wrong threshold can be corrected once someone actually tests it, while an unwritten one can never be tested at all.

This also means tolerating a different error rate. A manager given a real, numbered threshold will occasionally make a choice the founder would not have made. That cost is usually far smaller than the cost of remaining the only person in the business who can decide anything, no matter how small.

Ready to talk about your own business?

Start a Conversation
© 2026 Kunateh Impact Operations Consulting. All rights reserved.