The most exhausting decisions are rarely the biggest ones.
They’re the ones that should not have come back to you in the first place.
The small approvals.
The unclear tradeoffs.
The “just to be safe” escalations.
The decisions where everyone has an opinion, but nobody seems to own the final call.
That is where a lot of CEO fatigue comes from.
Not from the volume of work.
From being the final stop for decisions the system never made ownable.
At first, it looks responsible
A team wants alignment.
A leader wants context.
Someone wants to avoid creating risk.
Someone else says, “This touches a few areas, so we should bring it up.”
It sounds reasonable.
And often, it is.
Once.
The problem starts when this becomes the pattern.
More decisions come back up.
More meetings need the CEO in the room.
More leaders wait for confirmation before moving.
More teams prepare options instead of closing decisions.
The company still looks active.
People are working hard.
The calendar is full.
Updates are moving.
Documents are being shared.
But execution slows because too many decisions are still open.
And when decisions stay open, they travel upward.
At first, it looks responsible
This is not always a communication problem
Many CEOs misread the issue at first.
They think they have a communication problem.
Or a meeting problem.
Or a confidence problem.
Or a talent problem.
Sometimes they do.
But often, the real issue is simpler.
The organization has not made it clear who owns the decision, what authority they actually have, and what level of risk they are allowed to carry.
So people escalate.
Not because they are weak.
Not because they lack initiative.
Not because they need another reminder to “take ownership.”
They escalate because the system makes escalation safer than decision.
That distinction matters.
Because if escalation is safer than decision, people will keep escalating.
Even good people.
Especially good people.
Escalation often hides risk transfer
Good people know when a decision could create consequences.
They know when another function may disagree.
They know when the founder may have a strong view.
They know when the wrong move will be remembered longer than the slow one.
So they do the rational thing.
They bring it up.
They ask for alignment.
They wait.
And slowly, the CEO becomes the place where unresolved risk goes to be absorbed.
Not every escalation is bad.
Some decisions should move upward.
Some tradeoffs are genuinely strategic.
Some calls require the CEO.
But when escalation becomes normal, the operating model has changed.
The company is no longer asking:
“Who owns this decision?”
It is asking:
“Who needs to be comfortable before we move?”
That is a very different question.
And it creates a very different company.
Escalation hides risk transfer
The product release example
Here is a common one.
A product team wants to change the release date.
Engineering says the product is not ready.
Sales says the customer expectation has already been set.
Customer success says another delay will damage trust.
Finance wants predictability.
Product wants to protect quality.
Everyone has a valid point.
So the decision goes to the CEO.
That may make sense once.
But if this keeps happening, the issue is not the release date.
The issue is that the organization does not know who has the authority to make that tradeoff.
Who owns the final call?
What inputs are required?
What risk is acceptable?
What would make this decision escalate?
What would make it stay with the owner?
Without those answers, the company creates a pattern.
The work is owned locally.
The risk is owned by the CEO.
That gap is where escalation lives.
Capable teams become hesitant
Once that gap exists, people feel it.
They may not name it clearly.
But they adjust their behaviour around it.
They become more careful.
They seek more alignment.
They ask for more input.
They involve more people.
They slow down before the visible risk point.
This is how capable teams become hesitant.
Not because they forgot how to decide.
Because the decision boundary is unclear.
Ownership without decision boundary creates tension.
Responsibility without authority creates frustration.
Authority without clarity creates inconsistency.
And unclear escalation rules create dependency.
Ownership is a structural condition
Ownership is not a motivational state
This is why telling people to “take more ownership” rarely fixes the issue.
Ownership is not a motivational state.
It is a structural condition.
Manuel De Vits, who will be joining me as a future guest on Decision Load, wrote something recently that stayed with me:
“The edge comes when tech supports judgment, not replaces it.”
People need to know what they own.
They need to know what they can decide without returning upward.
They need to know what tradeoffs are theirs to make.
They need to know when escalation is required, and when escalation is avoidance.
Otherwise, the CEO remains the hidden owner.
Even when the org chart says otherwise.
This is one of the most expensive forms of execution drag.
It does not look dramatic.
It looks like responsible people trying not to make the wrong move.
It looks like alignment.
It looks like collaboration.
It looks like another meeting.
But underneath, the system is saying:
“Do not fully decide until authority appears.”
And in many companies, authority still means the CEO.
That is not scale.
That is controlled dependency.
A better question
The practical question is not:
“How do we stop people escalating?”
The better question is:
“What decisions keep coming back up, and why are they not structurally owned?”
A few useful questions:
What types of decisions keep returning to the CEO?
Who appears to own them on paper?
What authority is missing in reality?
What risk are people trying to move upward?
What would need to be clarified so the decision can close without escalation?
This is also the lens I use in a focused Decision Stability diagnostic with CEOs and senior operators.
In 30 minutes, we look at where decisions are returning upward, where ownership lacks authority, and which recurring escalations are creating execution drag.
The goal is not to eliminate escalation.
The goal is to make escalation meaningful again.
Escalation should signal a true strategic tradeoff.
Not unclear ownership.
Not missing authority.
Not fear of consequence.
Not a system that still borrows the CEO’s judgement for decisions others are supposed to own.
The real point
When everything escalates, nothing is really owned.
And when nothing is really owned, the CEO becomes the operating system.
That may work for a while.
But it does not scale.
Your team may not be slow.
They may be working inside a decision system that never fully gave them the authority to close.
♻️ Repost for a leader who is tired of being the final stop for every unresolved decision.
Follow me, Marko Ladis, for more leadership insights on Decision Stability.