The Invisible Bottleneck
Ask a CEO what's slowing their company down, and you'll hear: hiring, funding, product-market fit, competition.
Ask the people actually doing the work, and you'll hear something different: "I can't get decisions made."
Every time someone sends a Slack message asking "who should I talk to about this?" — that's a decision rights failure. Every time a project stalls waiting for approval from someone who doesn't know the context — that's a decision rights failure. Every time two teams make conflicting decisions because nobody defined who had authority — that's a decision rights failure.
Decision rights are the most important infrastructure in a scaling company. And almost nobody builds them intentionally.
What Decision Rights Actually Are
Decision rights define three things:
- Who can make which decisions — not by job title, but by decision type
- What information they need to make those decisions well
- What happens when the decision is above their authority — the escalation path
This sounds simple. It's not. Because in a 20-person company, decision rights are implicit. The CEO decides everything important. Everyone else handles the small stuff. And it works fine.
Then you hit 50 people. Then 100. Then 200. And the implicit system that worked at 20 becomes the single biggest bottleneck in the company.
The Three Decision Failures
1. The Vacuum
Nobody knows who has the authority to decide. So nobody decides. The project stalls. Eventually someone escalates it three levels up, and the CEO makes a decision about something they have no context on.
2. The Collision
Two people both think they have the authority to decide. They make conflicting decisions. Their teams execute on both. The company wastes resources and confuses customers.
3. The Funnel
Everything funnels up to a small group of decision-makers. They become the bottleneck. They're in back-to-back meetings all day. They make decisions too fast because they have to. Quality drops. Speed drops. The people below them feel disempowered.
All three failures have the same root cause: decision rights were never explicitly designed.
Building Decision Architecture
Step 1: Catalog Your Decisions
List every recurring decision in the company. Not one-time strategic choices — the decisions that happen weekly, monthly, quarterly. Things like:
- Pricing exceptions
- Hiring for a role
- Vendor selection under $X
- Feature prioritization
- Customer escalations
- Budget reallocation within a department
Most companies have 30-50 of these recurring decisions. And most have never written them down.
Step 2: Assign Owners
For each decision, designate:
- The decider: One person (never a committee) who has the authority to make the final call
- The advisors: People who must be consulted before the decision
- The boundary: Dollar amount, scope, or risk level that defines when this person can decide vs. when they must escalate
Step 3: Define Escalation Paths
When a decision exceeds someone's authority, the path should be clear and fast. Not "schedule a meeting with leadership" — a defined protocol.
Good escalation paths have:
- A trigger: Clear criteria for when to escalate
- A destination: Exactly who you escalate to
- A timeline: How fast the escalation needs resolution
- A default: What happens if the escalation isn't resolved in time
That last one is critical. Without a default, escalations become black holes where decisions go to die.
Step 4: Publish and Train
Decision rights only work if everyone knows them. They need to be:
- Written down in a place everyone can find
- Reviewed in onboarding for every new hire
- Updated quarterly as the organization evolves
- Actually enforced (if you override the system, you undermine it)
The Speed Test
Here's a simple diagnostic: pick any active project in your company. Find the last decision that took more than 48 hours to make. Now trace why.
Almost always, you'll find one of three things:
- Nobody knew who had the authority to decide
- The person who could decide didn't have the information they needed
- The decision exceeded someone's authority but there was no clear escalation path
Fix those three things — across the organization — and you'll see decision velocity increase dramatically. Not by working harder. By removing structural friction.
A Note on Trust
Some leaders resist formalizing decision rights because it "feels bureaucratic." They prefer a culture of trust where people just figure it out.
Trust is essential. But trust without structure is just hope. And hope is not an operating system.
The best organizations have both: high trust and clear structure. The structure doesn't replace trust — it enables it. When people know their boundaries, they move faster within them.
Decision rights are the foundation. Build them early. Update them often. Everything else in your operating system depends on them.
-E