Why senior leaders become the organisation’s accidental routing layer.

Many organisations have a person who knows how everything really works. They understand the history behind the architecture, the promise made to a customer, the political constraint inside a partnership and the reason a previous attempt failed. When something becomes ambiguous, that person gets involved.

At first this feels efficient. The decision is made quickly. The immediate risk disappears. People learn that the safest route through uncertainty is to send it upward.

Eventually the senior leader becomes an accidental routing layer: the point through which unrelated decisions, trade-offs and conflicts must pass before work can continue.

It usually begins as a strength.

The pattern does not emerge because the leader is controlling or the team is incapable. It often begins because the leader is experienced, responsive and unusually good at joining the dots.

But every fast rescue teaches the system something. The team learns which questions earn immediate senior attention. Managers learn that escalation transfers both risk and responsibility. Other executives learn to use the same person as an informal integration mechanism.

The signals are observable.

The routing-layer problem rarely appears as a line on an organisation chart. It shows up in behaviour:

• Work pauses until a particular leader attends the meeting.
• Decisions return upward after apparently being delegated.
• Managers bring problems without a recommendation.
• Cross-functional disagreements become executive arbitration.
• The same category of escalation appears repeatedly.
• The leader’s calendar fills with coordination rather than genuinely senior work.

None of these events is alarming on its own. Together they describe an organisation that has located judgement in a person rather than in its management system.

Delegating harder does not fix it.

A common response is to tell managers to “take more ownership.” That asks them to absorb more risk without changing the conditions that made escalation rational.

If outcomes remain unclear, decision boundaries overlap and quality standards live in the leader’s head, the organisation will continue to route work toward the person holding the missing context. The behaviour is not a confidence problem. It is a system response.

Replace the person with an operating path.

Classify the decisions

Look at what reached the leader over the previous month. Group it by type: strategy, people, technical risk, customer commitment, resources or cross-functional conflict. Repetition reveals where the system lacks an owner, standard or escalation contract.

Move context to the work

Ask what information only the senior leader possessed. Strategy, economics, customer history and risk tolerance should be made available before a decision is needed. Context is an organisational asset, not executive private property.

Define the boundary

For recurring decisions, make clear who decides, who contributes, what is fixed and what should trigger escalation. A useful boundary reduces both hesitation and accidental overreach.

Change the escalation contract

Require an escalation to include the intended outcome, relevant evidence, options considered, a recommendation and the risk of waiting. This keeps ownership with the person closest to the work while still making senior help available.

Close the loop

When an escalated decision is resolved, ask what should change so the next version does not need the same route. A decision can solve the immediate problem. A learning loop improves the organisation.

The leader’s new job

The goal is not to remove senior leaders from consequential decisions. It is to reserve their attention for decisions that genuinely require their scope, authority or judgement.

The practical measure is not how many decisions a leader makes. It is how much decision-making capacity the organisation gains around them.

If the leader steps away for two weeks, does important work continue with appropriate speed and quality? Where it does not, the interruptions are not merely inconveniences. They are signals pointing toward the next improvement in the operating system.