July 10, 2026

The Founder Bottleneck

Every decision routes through the founder; the team stalls waiting on answers. Fix it with a 3-tier decision-rights matrix and an escalation threshold.

This is a representative example illustrating the method below. It is a composite scenario, not a specific named client engagement.

The constraint

A twenty-person services company had grown past the point where one person could hold every call in their head, but no one had told the org chart. Every substantive decision — pricing exceptions, staffing on a client, whether to expense a tool, how to respond to a client escalation — routed through the founder. When she was in meetings, the team waited. When she was on a plane, work stopped.

Revenue was up. Capacity was not.

What was actually happening

The team was fully capable. They were also fully trained, through months of casual precedent, that decisions made without the founder tended to be redone with her later. So they stopped making them. What looked like a leadership problem ("my team won't take ownership") was really an authority-design problem: nobody had ever written down which decisions belonged to whom, or below what threshold nobody needed to ask.

The absence of a rule is itself a rule. Its rule was: ask.

The decision

Stop diagnosing this as a culture or hiring issue. It's a decision-rights issue. Two artifacts, deployed together, eliminate roughly ninety percent of the bottleneck: a decision-rights matrix and an escalation threshold.

What got built

A three-tier decision-rights framework, published, referenced weekly, and enforced at the point of escalation (i.e., the founder started sending things back with "this is a Tier 2, you own it" instead of ruling on them).

Tier 1 — Founder-owned. Strategy, hiring above a defined salary, entering or exiting a market, changes to pricing structure, any client-facing commitment above a defined dollar value, anything that would appear in a board deck. Consulted: leadership team. Informed: full team.
Tier 2 — Function-lead-owned. Delivery approach on an active client, tool choices within an existing category, hiring below the defined salary line, spending within the function's approved budget. Consulted: peers whose work is affected. Informed: founder, monthly.
Tier 3 — Individual-owned. Anything below the escalation threshold. Executed, logged, reviewed only if outcome is off-standard. Not escalated.

Alongside the tiers, one number: the escalation threshold. Below this number of dollars, hours, or client-impact risk, no one asks. The threshold was set generously on purpose — high enough that the vast majority of daily decisions cleared it. In this case, the initial numbers were five hundred dollars of unbudgeted spend, four hours of unplanned team time, and any single-client issue with no cross-client or reputational spillover.

What changed

Within a quarter, the founder's calendar had recovered roughly twelve hours a week — not because decisions became fewer, but because most of them stopped being hers. Team members who had looked passive turned out to have strong opinions; they had simply been trained not to voice them until asked. The velocity of small decisions — the ones that don't feel important individually but compound into weekly output — roughly doubled.

The threshold, importantly, did not cause bad decisions. It caused decisions to be made by the people closest to the information, which is where they should have been made all along.

The artifact you can use today

Here is the framework in the exact form it deploys. Copy it, edit it for your context, publish it to your team this week:

For each recurring decision type in your business (pricing, hiring, tool spend, client commitments, staffing changes, refunds, exception approvals), decide which of the three tiers it lives in.
Set the escalation threshold in writing. It should be uncomfortably high — if it feels safe, it is too low. Below the threshold, no permission is required and no one is CC'd.
Publish both. Not to a wiki no one reads — to the same place the team looks daily. If you use a shared doc, pin it. If you use a channel, pin it there.
Enforce at the point of escalation, not the point of decision. When someone brings you a Tier 2 or Tier 3 decision, refuse it. Say "you own this, decide, tell me what you decided." Do this for six weeks. The pattern breaks.

Is this you?

Symptoms: your team is competent but slow. You are the last read on things you don't need to read. Small decisions wait for you across time zones. You have said the phrase "I don't know why they didn't just decide" more than once this month. If any two of those are true, the constraint is decision rights, not talent.