Twelve executives can spend ninety minutes arguing over a C-suite role and leave without a decision. Not because they lack opinions. Because nobody agreed who actually got to decide.
Harvard Business Review has described this pattern as a decision-rights design problem rather than a vague alignment issue. Past a certain scale, the gap between who is supposed to decide and who is allowed to decide widens every quarter.
Most leadership teams call the result an alignment problem. Often it is not. Companies do not only slow down because strategy is unclear. They slow down because designed authority and felt authority quietly diverge.
Where permission actually lives
Somewhere between the org chart and the live meeting, “who decides this” defaults to whoever has been in the room longest. Usually the founder who never intended to own the issue forever.
This is the pattern behind pricing, hiring and vendor decisions that keep landing on one desk. A team learns once or twice that a decision made without sign-off gets quietly re-litigated. So people stop solving problems. They become excellent at forwarding them.
Decision rights are not a values statement and not a RACI chart nobody rereads after the workshop. RACI assigns responsibility. It does not automatically transfer permission.
A vice president can be “accountable” on paper and still wait for a nod nobody promised. The live test is simple: does the closest person to the decision have standing to make it, or does every consequential choice float upward?
Founders rarely choose to become bottlenecks
Founders are often appointed as bottlenecks one unchallenged escalation at a time. The organisation discovers that founder review is safer than owned judgment. The founder discovers that the organisation will not move without that review. Both sides reinforce the other.
That is why “delegate more” is incomplete advice. Tasks can move while permission stays centralised. Titles can multiply while felt authority remains thin.
The result is not only founder overload. It is organisational speed disappearing into a queue outside one office.
Repair the contract, not the calendar
Start with one recurring decision family rather than the whole company. Write a five-part contract:
- Owner. One person makes the decision.
- Inputs. What evidence and consultation are required.
- Boundary. The risk, financial or reputational limits of autonomous action.
- Escalation. The condition that genuinely needs a higher-level call.
- Review. When the organisation examines the outcome and learns.
Then run the next decision through that route. If it returns, diagnose the architecture before reclaiming the decision. Was ownership fake? Was the boundary unclear? Did culture punish independent judgment?
Felt authority grows when people see that ownership is real, mistakes are reviewable and good judgment does not require constant founder theatre.
What this has to do with coaching and scale
This is not an abstract governance exercise. It is the operating condition behind founder dependency, slow leadership teams and decision overload. Entrepreneur Flight Deck treats founder attention and team decision rights as connected layers of the same system.
If authority exists on paper but not in practice, the company will keep converting growth into queueing behaviour. If felt authority is redesigned, work starts moving sideways instead of always moving up.
Where does authority exist on paper but not in practice?
Map the decision that keeps returning before redesigning the whole organisation.
Read the decision-architecture pillarWays to work with Aman