Organisations learn from leaders even when leaders are not deliberately teaching them anything.

If a difficult decision repeatedly gets taken upward, people learn that difficult decisions belong upward.

If a recommendation is regularly revisited once a senior leader enters the room, people learn that commitment should wait.

If acting independently creates more exposure than escalating, people learn to escalate.

Eventually, nobody needs to issue an instruction.

The organisation learns to wait.

This is one of the less visible ways organisational dependency becomes self-reinforcing. A leader may be trying to protect standards, reduce risk or keep work moving under pressure. Their interventions can be entirely rational. But repeated often enough, those interventions begin changing the behaviour of the people around them.

The organisation starts learning where uncertainty should go.

And once that learning becomes embedded, the leader may find themselves carrying even more of the very load they were trying to manage.

Organisations learn from consequences, not slogans

Many organisations say they want decisions made at the lowest appropriate level.

They talk about empowerment, accountability, ownership and trust.

But people do not learn primarily from statements like these. They learn from what actually happens when they act.

Suppose a manager makes a difficult call within their formal authority. The decision is later revisited by a senior leader, not because the process required it, but because the outcome feels uncomfortable. The manager may technically retain the same delegation afterwards.

Behaviourally, something has changed.

The next time a similar decision appears, the manager knows there is a second decision hidden inside the first:

Can I make this call, or do I need to make sure the senior leader is comfortable first?

If the safest option is to check upward, formal authority becomes less relevant than practical consequence.

The organisation learns accordingly.

That is why empowerment initiatives can fail even when delegations are clear. If the consequences surrounding independent judgement still favour escalation, people will continue escalating.

Not because they are weak.

Because they are paying attention.

Waiting can become rational behaviour

Waiting is often treated as a cultural problem.

People are described as hesitant, risk-averse or unwilling to take ownership. Leaders become frustrated that decisions are not being made quickly enough. Teams are told to be more proactive.

Sometimes those descriptions are fair.

But there is another possibility.

The organisation may have taught people that waiting is sensible.

Consider the difference between two environments.

In the first, a manager makes a reasonable decision within their authority. If the outcome is imperfect, the organisation examines the reasoning, learns from it and supports the decision-making process unless there was negligence or clear misconduct.

In the second, the same manager makes a reasonable decision and later discovers that a senior leader would have preferred something different. The decision is reopened. The manager has to explain why they acted without checking. Future discretion becomes more cautious.

The formal delegation may be identical in both environments.

The behavioural lesson is completely different.

In the second environment, asking first is not bureaucracy.

It is protection.

The leader may never intend to create dependency

This pattern does not require an authoritarian leader.

Quite often it develops around capable, conscientious leaders who care deeply about outcomes.

They notice risk others miss. They have more experience. They understand stakeholder sensitivities. They know how quickly a seemingly small problem can become serious.

So they intervene.

They ask another question. They suggest a change. They take a difficult conversation themselves. They review the draft. They join the meeting. They make the final call when the group cannot settle it.

In isolation, each intervention may improve the immediate outcome.

But organisations learn through repetition.

If difficult situations consistently improve once the senior leader becomes involved, people begin involving them earlier.

Soon the leader is no longer merely solving exceptions.

Their involvement has become part of the organisation's method for handling uncertainty.

This is where good leadership can unintentionally become load-bearing infrastructure.

The organisation becomes more cautious before it becomes less capable

Dependency rarely appears as an obvious collapse in capability.

The early change is usually caution.

People still know how to do the work.

They still have ideas.

They may still understand the decision better than anyone else.

What changes is their willingness to commit without senior reassurance.

You can see it in small behaviours:

– recommendations become more tentative; – papers contain more caveats; – meetings end with “we should check” rather than a decision; – teams seek endorsement before acting within existing authority; – difficult customer matters move upward sooner; – exceptions are treated as inherently senior; – decisions that could be made now are held until a particular person is available.

None of these behaviours necessarily looks dramatic.

Together, they change decision flow.

The organisation starts becoming slower precisely because everyone is trying to avoid making the wrong call.

Senior intervention changes the economics of judgement

People make decisions partly by weighing risk.

If acting independently carries personal exposure while escalating carries little cost, escalation becomes the economically sensible response.

This matters because leaders often experience the result as a capability problem.

They think:

Why won't people just make the decision?

But from the employee's perspective, the question may look different:

Why would I take the full consequence of this decision when involving the senior leader costs me almost nothing?

That is a structural problem, not merely a confidence problem.

Unless the organisation changes the relative consequences of independent judgement and escalation, telling people to “step up” is unlikely to have much effect.

They will continue doing what the system rewards.

The loop can become self-confirming

This is where the pattern becomes especially difficult to break.

A leader under sustained pressure begins making more decisions themselves because consultation feels slower and ambiguity feels riskier.

People around them observe that difficult matters are increasingly resolved at the top.

They respond by escalating earlier.

The leader receives even more difficult matters.

They conclude that the surrounding team is not exercising enough judgement.

That conclusion appears to justify maintaining tighter control.

The team sees the tighter control and becomes even more cautious.

The loop now produces its own evidence.

The leader can point to repeated escalation as proof that people are not ready.

The organisation can point to repeated senior intervention as proof that senior involvement is necessary.

Both observations may be factually correct.

Neither explains how the pattern developed.

This is how dependency becomes invisible

A mature dependency pattern can look surprisingly orderly.

People know who to involve.

The senior leader is responsive.

Difficult issues reach someone capable.

Decisions are eventually made.

There may be no obvious governance failure.

The organisation can therefore believe the system is working.

And in one sense, it is.

The danger lies in what the system is consuming to keep working.

It may be consuming disproportionate amounts of one person's judgement, availability, memory, confidence and authority.

As long as that person continues carrying the load successfully, the dependency can remain hidden behind performance.

This is another version of capability masking condition.

The organisation sees that outcomes are still being delivered.

It does not necessarily see how narrow the path to those outcomes has become.

What leaders reinforce matters more than what they say

A leader can tell people they are trusted while repeatedly overriding them.

They can encourage ownership while joining every difficult decision.

They can say “you don't need my permission” while behaving in ways that make people feel safer obtaining it.

The inconsistency is rarely deliberate.

But behaviour is usually the more powerful signal.

That means leaders need to pay attention not only to the decisions they make, but to the organisational lesson attached to those decisions.

When you step in, what does the team learn?

When you override something, what principle becomes clearer?

When you take a decision back, does the person understand why this particular issue required senior judgement?

When you support a reasonable decision you would personally have made differently, what does the organisation learn about authority?

These moments shape the real operating model.

Not every escalation should be pushed back down

The answer is not to reject escalation automatically.

Some decisions should move upward.

Some risks genuinely require senior accountability. Some issues have consequences broader than the authority of the person closest to the work. Some decisions require specialist judgement or an enterprise-wide perspective.

Good organisations know the difference.

The problem is not escalation itself.

The problem is when the boundary between legitimate escalation and learned dependency becomes unclear.

A useful test is to ask:

What does senior involvement provide here that cannot reasonably sit at the current level?

If the answer is enterprise accountability, unique expertise or genuinely broader consequence, escalation may be appropriate.

If the answer is reassurance, habit or protection from being second-guessed, something else is happening.

The organisation has to make independent judgement safer

If leaders want decisions to remain distributed, they need to create conditions in which reasonable judgement can survive contact with imperfection.

That does not mean lowering standards.

It means distinguishing between a poor process and an outcome that simply was not the one a senior leader would have chosen.

It means allowing people to exercise authority without requiring them to predict the personal preferences of every person above them.

It means making decision principles visible enough that people can act without needing constant reassurance.

It means backing reasonable decisions after they are made, particularly when they fall within agreed boundaries.

And it means using mistakes to improve judgement rather than automatically using them as evidence that authority should be taken back.

Without those conditions, distributed authority remains fragile.

A practical test: what happens after someone decides without you?

One of the simplest ways to assess the pattern is to watch what happens when someone makes a difficult decision without involving the usual senior person.

Ask five questions.

1. Is the first reaction curiosity or correction? Curiosity examines the reasoning. Correction immediately teaches people that the destination matters more than the judgement process.

2. Is disagreement treated as evidence that the person exceeded their authority? A different decision is not automatically an unauthorised decision.

3. Does the decision stay made? If reasonable decisions are routinely reopened, people will learn to seek endorsement before committing.

4. Is the person better equipped for the next decision? The organisation should transfer principles and context, not merely replace the answer.

5. Does senior involvement become less necessary over time? Healthy support should progressively increase independent capability. Dependency requires the same support repeatedly.

These questions reveal whether the organisation is genuinely distributing judgement or simply distributing work while keeping practical control concentrated.

The warning sign is not escalation

Escalation is part of organisational life.

The warning sign is when the organisation begins escalating before it has really tried to decide.

That is when waiting has become learned behaviour.

And once the organisation has learned to wait, the leader's workload is no longer only a consequence of the organisation's design.

The leader's own repeated responses may now be helping reproduce the conditions that create the load.

That is not a reason for blame.

It is a reason to examine the loop.

Because the important question is no longer simply:

Why does everything keep coming to me?

It is:

What has the organisation learned from the way I respond when it does?

That is often where the path out of dependency begins.

One of the most dangerous assumptions organisations make about leadership pressure is that the warning sign will be poor decisions.

Often it is not.

A leader under sustained pressure may continue making sound calls. They may remain decisive, responsive and highly effective. They may move quickly through ambiguity, resolve difficult issues and keep the organisation performing.

From the outside, they can look focused.

From the inside, something else may be happening.

The leader may be consulting less. They may be spending less time exposing their reasoning to others. They may be taking more decisions themselves because it feels faster, safer or more reliable. Their tolerance for uncertainty can reduce. Their behavioural range can narrow.

The decisions can still be good.

The organisation can still be becoming more dependent.

That distinction matters because deterioration in organisational capability can begin long before deterioration in decision quality becomes visible.

Pressure can change the pathway, not the outcome

Most leadership systems are designed to detect failure after it becomes visible.

A decision is wrong. A deadline is missed. A stakeholder relationship deteriorates. A project fails. A leader becomes exhausted or disengaged.

Those outcomes are relatively easy to notice.

What is harder to see is a change in how the same successful result is being produced.

Imagine a leader who normally seeks input from several people before making an important decision. They challenge assumptions, invite dissent, ask others to test the issue and then make the call.

As pressure increases, that process can begin to compress.

There is less time. More issues are arriving. The leader already knows the context. They have handled similar situations before. They can reach a good answer faster by relying on their own judgement.

So they do.

The decision may still be correct.

But fewer people were involved in reaching it.

Fewer people saw how the trade-offs were assessed.

Fewer people exercised their own judgement.

The leader solved the immediate problem while the organisation received less opportunity to build capability around it.

The result can therefore improve or remain stable while the underlying decision system becomes more concentrated.

Focus and narrowing can look remarkably similar

This is one reason the pattern is difficult to identify.

Leaders under pressure often describe themselves as more focused.

They are cutting through noise. Reducing unnecessary discussion. Moving faster. Protecting time. Getting closer to the critical issues.

Sometimes that is exactly what is happening.

Strong leadership often requires prioritisation, speed and clarity.

The question is whether focus is improving the quality of attention or narrowing the range of behaviour available to the leader.

A useful distinction is:

Focus removes distraction. Narrowing removes options.

A focused leader can still choose when to consult, when to delegate, when to tolerate ambiguity and when to slow a decision down.

A narrowed leader may increasingly default to the same response because pressure has made alternatives feel too costly.

Consultation feels slow.

Delegation feels risky.

Debate feels inefficient.

Waiting for someone else to build confidence feels impossible.

So the leader increasingly carries the judgement themselves.

The behaviour can look decisive.

The organisation experiences greater concentration.

Good decisions can hide a weakening system

This is where individual capability can mask organisational condition.

If a capable leader continues making good decisions, the organisation has little immediate incentive to question how those decisions are being produced.

There may be no crisis.

Performance remains acceptable.

Customers are still served.

Executives remain confident.

The leader may even be praised for staying across the detail during a difficult period.

But underneath that performance, several things can be changing.

Other people receive fewer opportunities to exercise judgement.

Senior consultation becomes more selective.

Decision authority concentrates in practice even when formal delegations remain unchanged.

Teams learn that difficult situations are more likely to be resolved by the leader than through their own judgement.

The leader accumulates even more experience because they continue receiving the hardest problems.

The capability gap between the leader and the surrounding organisation can then widen.

The system becomes more dependent precisely because the leader continues performing so well.

This is an uncomfortable paradox.

The leader's strength can delay recognition of the organisation's weakness.

The organisation adapts to the leader's adaptation

Pressure does not affect only the leader.

People around the leader observe what produces progress.

If the leader becomes more involved in difficult decisions, teams learn to involve them earlier.

If consultation narrows, people may stop bringing competing views because they sense the leader wants resolution rather than exploration.

If the leader repeatedly takes over ambiguous decisions, others may become less inclined to exercise judgement themselves.

None of this requires a formal instruction.

The organisation adapts to what the leader repeatedly does.

That creates a reinforcing loop.

Responsibility and ambiguity concentrate around the leader.

The increased load puts the leader under pressure.

Under pressure, the leader narrows the way they work and pulls more judgement inward.

Others observe that pattern and escalate more.

The organisation becomes more dependent.

The leader receives even more load.

What began as a response to pressure can therefore become one of the mechanisms that sustains it.

Decisiveness can become expensive

Organisations rightly value decisive leaders.

A leader who can move through uncertainty and make a sound call is enormously valuable, particularly when time matters.

The structural problem appears when decisiveness becomes the organisation's preferred substitute for distributed judgement.

If every difficult issue eventually reaches the person most capable of resolving it, the system can look highly effective while becoming increasingly fragile.

The leader's decisiveness then carries two costs.

The first is visible: the cognitive load of continuing to make difficult decisions.

The second is less visible: the opportunity cost of everyone else not making them.

Each decision the leader absorbs is one less repetition available to somebody else.

Each exception they personally resolve is one less opportunity to clarify the authority or principles that could guide similar decisions in future.

Each time they provide the answer without exposing the reasoning, the organisation receives the result but not the capability that produced it.

The organisation can therefore become faster today and slower tomorrow.

The question is not whether the leader should step back

A simplistic response would be to tell the leader to delegate more, consult more or stop taking on so much.

That may miss the cause of the behaviour entirely.

If the leader is narrowing because the surrounding system is producing excessive ambiguity, unclear authority or repeated escalation, simply asking them to behave differently does not remove the pressure.

It can make the organisation feel less supported without increasing its ability to act.

The structural question is:

What is making the leader's narrower behaviour rational?

Perhaps the consequences of a wrong decision genuinely sit with them.

Perhaps information is fragmented and they are the only person with enough context.

Perhaps delegated decisions are repeatedly revisited by more senior leaders.

Perhaps teams do not have enough experience because difficult problems have historically been concentrated elsewhere.

Perhaps the organisation rewards speed more heavily than capability development.

Perhaps the leader has learned that involving more people creates delay without materially improving the decision.

Those conditions matter.

You cannot reliably widen leadership behaviour while leaving the conditions that narrowed it untouched.

Watch for the change in pattern

The most useful signals are often comparative.

Do not ask only how a leader behaves today.

Ask how their behaviour has changed under sustained load.

Do they consult fewer people than they used to?

Do they make more decisions personally?

Do they spend more time correcting work than developing the people doing it?

Have they become less willing to tolerate experimentation or disagreement?

Are they joining more meetings because they no longer trust the issue will be resolved without them?

Are they increasingly described as being 'across everything'?

Does the organisation feel faster when they are involved and noticeably slower when they are not?

None of these observations proves there is a problem.

But together they can indicate that pressure is changing not only the amount of load a leader carries, but the way they lead while carrying it.

A useful diagnostic question: is this focus or narrowing?

When a leader is operating under significant pressure, one useful question is:

Is this focus, or has the range of available leadership behaviour started to narrow?

There are several ways to test the difference.

Can the leader still choose to slow a decision down when learning matters more than speed?

Can they allow somebody else to reach a different conclusion without immediately taking control?

Can they tolerate a reasonable mistake as part of capability development?

Can they explain the principles behind a decision rather than simply providing the answer?

Can they distinguish between an issue that genuinely requires their judgement and one that merely feels easier to handle themselves?

The question is not whether they always behave expansively.

No leader should consult endlessly or delegate indiscriminately.

The issue is whether they still have meaningful choice.

Pressure becomes structurally significant when the leader's response becomes increasingly automatic.

The risk is bigger than burnout

Leadership pressure is often discussed primarily as a wellbeing issue.

That matters, but it is incomplete.

A leader can remain energetic, committed and productive while their behavioural range narrows.

They may not feel burned out.

They may feel effective.

The organisation may agree.

Yet the system around them can still be losing independence.

That is why the consequences of concentrated leadership load cannot be understood only by looking at the person carrying it.

The leader and the organisation begin shaping each other.

The organisation concentrates difficult judgement around the leader.

The pressure changes how the leader responds.

The leader's response changes how the organisation behaves.

That behaviour creates further dependency.

Over time, it becomes increasingly difficult to separate the structural problem from the behavioural response.

Strong leaders should leave more capability behind them

The objective is not to make leaders less decisive.

It is not to remove expertise or pretend that every decision can be distributed equally.

It is to ensure that the organisation becomes more capable through exposure to strong leadership rather than more dependent on access to it.

That requires attention to what happens around the decision, not only whether the decision was correct.

Who saw the reasoning?

Who exercised judgement?

Who gained context?

Whose authority became clearer?

Who will be better equipped to handle the next version of the problem?

Those questions shift leadership from simply producing answers toward producing organisational capability.

And they provide a different way to assess pressure.

The warning sign is not only that a leader is carrying too much.

It is that carrying too much is beginning to change the way the organisation makes decisions.

At that point, the issue is no longer simply leadership workload.

The load has started reshaping the system that created it.

An organisation can look resilient right up until one person is unavailable.

A senior executive takes leave. A founder steps away for a week. A long-serving manager is sick. A key technical person resigns. Someone who normally answers the difficult questions is suddenly not there.

Then the organisation starts to behave differently.

Decisions wait. Meetings are postponed. People check whether something can be held until the person returns. Customers are told that somebody will come back to them. Work continues, but with more caution. Exceptions sit unresolved. Informal workarounds appear.

The absence can look like the problem.

Often it is not.

The absence is the test. The dependency was already there.

When a capable person is present every day, their judgement can conceal how much the organisation has come to rely on them. They answer quickly, connect information across functions, remember the history, resolve ambiguity and know which risks matter. Their capability keeps the system moving.

That makes the dependency difficult to see.

Performance can remain high while organisational independence quietly declines.

Capability can mask condition

A highly capable person can compensate for structural weakness for a long time.

They know who to call. They remember why a past decision was made. They recognise an issue before anyone else does. They can interpret incomplete information and make a call without needing the organisation to formalise every rule.

None of those things is inherently a problem.

The problem emerges when the organisation stops building enough alternative pathways because the person is consistently available to bridge the gaps.

Instead of clarifying authority, people ask them.

Instead of strengthening decision rules, people ask them.

Instead of distributing critical knowledge, people ask them.

Instead of resolving ambiguity closer to the work, people ask them.

Over time, the person’s helpfulness stops being an individual behaviour and becomes part of the operating model.

That is why key-person dependency is often underestimated. Leaders look for a single irreplaceable specialist or founder whose departure would create an obvious crisis. But dependency can be much more ordinary than that.

It can sit in the person who:

– approves exceptions that supposedly belong elsewhere; – carries the relationship history nobody has documented; – knows which stakeholders need to be consulted before a decision is made; – resolves cross-functional conflict because formal ownership is unclear; – translates between technical and commercial teams; – knows when a policy can be flexed and when it cannot; – becomes the default escalation point because people trust their judgement.

The person may not even appear indispensable on the organisation chart.

Operationally, they can still be load-bearing.

Absence changes behaviour before it stops work

A useful mistake to avoid is assuming dependency exists only when work completely stops.

Most organisations are more adaptive than that.

People find ways around the missing person. They defer some decisions. They become more conservative on others. They escalate to somebody more senior. They ask another experienced colleague. They reduce the scope of what they are willing to commit to.

So the first sign of dependency is often not failure.

It is behavioural change.

Ask what happens when the person is unavailable:

– Do decisions take longer? – Does authority move upward? – Do people become less willing to make exceptions? – Are meetings rescheduled because the person “needs to be there”? – Does customer or stakeholder communication become less certain? – Does somebody else inherit a sudden spike in escalations? – Do teams discover that important knowledge exists mainly in one person’s memory?

These are continuity signals, but they are also operating-model signals.

They show where responsibility may be distributed formally while judgement, confidence or authority remains concentrated in practice.

“We can cope without them” is not the same as resilience

Many leadership teams test dependency with a simple question:

Could we keep operating if this person left?

That is useful, but incomplete.

Most organisations can keep operating.

The better question is:

What would change in how the organisation operates?

Would decisions move more slowly?

Would more matters reach the executive team?

Would risk tolerance fall?

Would staff spend more time searching for context?

Would customers experience inconsistency?

Would other senior people absorb the load?

Would teams narrow what they are prepared to decide themselves?

A system can continue functioning while becoming materially more dependent, slower or more fragile.

That is why resilience should not be defined simply as continued activity.

A resilient organisation retains enough distributed judgement, knowledge and authority that the absence of one person does not materially distort how work gets done.

Dependency is rarely only about knowledge

Succession and continuity planning often focus first on knowledge transfer.

Document the process. Write the handover. Build the procedure. Cross-train somebody else.

Those actions matter, but they may not address the deeper dependency.

The organisation may know what the person does and still depend on them for judgement.

That distinction matters.

A procedure can explain the normal case. It may not tell somebody how to respond when two priorities conflict, when a customer request falls outside policy, when a stakeholder is politically sensitive, or when the consequences of a wrong decision are unclear.

Those situations are precisely where decision authority and organisational trust become visible.

If the backup person knows the information but still feels they need permission to act, the dependency has not really moved.

It has only been documented.

The real test is whether judgement can travel

Key-person dependency becomes less dangerous when capability can travel through the organisation rather than remaining attached to an individual.

That does not mean every person should be interchangeable. Nor does it mean removing expertise, hierarchy or senior judgement.

It means making deliberate choices about where different forms of dependence are acceptable and where they are not.

For a genuinely specialist technical decision, concentration may be rational.

For ordinary exceptions, recurring customer issues or routine cross-functional trade-offs, repeated dependence on one senior person may indicate something else: authority has not moved with responsibility, decision rules are weak, or trust has not developed far enough for judgement to sit closer to the work.

The objective is not to eliminate dependence entirely.

It is to prevent unexamined dependence from becoming the organisation’s default way of operating.

A practical absence test

One of the simplest ways to examine the issue is to choose a person who is widely relied on and ask five questions.

1. What routinely waits for this person? Look beyond tasks. Include decisions, approvals, introductions, interpretations and conflict resolution.

2. What moves upward when they are unavailable? This reveals whether their absence redistributes judgement or simply pushes it higher.

3. What do other people know, but still not feel authorised to decide? This separates a knowledge gap from an authority or trust gap.

4. Which relationships depend on the person rather than the role? Customers, stakeholders, partners and internal networks can create dependency even when formal processes look robust.

5. What capability would the organisation need to strengthen so their absence changed less? The answer may be documentation. But it may also be clearer authority, stronger decision rules, broader stakeholder relationships or more confidence in distributed judgement.

Those questions turn absence from a contingency-planning exercise into an organisational design diagnostic.

The warning sign is not that someone matters

Good organisations contain people who matter enormously.

Expertise matters. Trust matters. Relationships matter. Experience matters.

The warning sign is not that losing somebody would hurt.

The warning sign is that ordinary organisational functioning has quietly adapted around their constant availability.

When that happens, the person is no longer simply contributing capability.

They are carrying part of the system.

And the longer they carry it successfully, the easier it is for everyone else to mistake performance for resilience.

The question is therefore not only, “Who could we not afford to lose?”

It is also:

“Whose absence would change the way this organisation makes decisions?”

That is where dependency becomes visible.

There is a point at which organisational dependency stops being primarily about the person carrying the load and starts changing the behaviour of everyone around them.

It rarely arrives as a formal decision. Nobody announces that difficult questions should now go through one particular leader. There is no new delegation instrument, reporting line or procedure. The organisation simply learns, through experience, that involving that person produces a better or safer outcome.

A decision feels uncertain: ask them. Two teams disagree: bring them in. A stakeholder is unhappy: see what they think. Something unusual appears that does not quite fit the process: check with them first.

Each interaction can be entirely reasonable. But repeated often enough, ask them can become an unwritten organisational rule.

That matters because the effect is no longer confined to the workload of one capable person. It begins changing how other people exercise judgement, use authority and respond to uncertainty.

A decision can be delegated without really leaving

Organisations often appear to distribute decision-making more effectively than they actually do.

A manager may formally have authority to approve something. A team might have a clear delegation. A process may explicitly identify who owns the decision. Yet before acting, someone still walks down the corridor, sends a Teams message or adds a familiar leader to the meeting.

Just checking what you think.

Sometimes that is good judgement. Consultation is not inherently evidence of dependency, and complex decisions often benefit from another perspective.

The distinction lies in what happens next.

If the conversation helps someone think and they subsequently make the decision themselves, capability may be developing. If the conversation is actually seeking reassurance that the decision is safe, something different may be happening.

The authority has been delegated.

The confidence to use it has not.

Over time, this can create an organisation in which decision rights look distributed on paper while practical decision-making remains concentrated around a much smaller number of people.

People learn where the safest answer lives

This behaviour is not necessarily caused by weak or unwilling employees. In many cases, people are responding intelligently to the environment around them.

Suppose two people can make a decision.

One option is to exercise your own judgement and accept the consequences if the decision turns out to be wrong. The other is to spend five minutes checking with the person whose judgement the organisation already trusts.

If both options take roughly the same amount of effort, the second can feel considerably safer.

This becomes even more powerful when the organisation has a low tolerance for mistakes, unclear delegations or a history of second-guessing decisions after they are made. People quickly learn that formal authority does not necessarily provide practical protection.

The question stops being:

Am I authorised to decide this?

It becomes:

Who needs to be comfortable with this before I decide?

Those are very different operating environments.

One distributes authority.

The other distributes responsibility while allowing confidence and practical control to remain concentrated elsewhere.

The capable leader becomes a source of organisational certainty

For the person being consulted, the pattern can initially feel positive.

People value their judgement. They are trusted. They have influence beyond the boundaries of their formal role. Their involvement helps colleagues move forward.

But something subtle happens when enough people begin using the same person to reduce uncertainty.

The leader becomes a source of organisational certainty.

They are no longer simply contributing expertise. Their involvement itself begins making a decision feel legitimate.

That creates a different form of load.

The leader does not necessarily have to do the work. They may not own the project, write the document or manage the people involved. They simply need to be available often enough for others to test decisions against them.

A ten-minute conversation here. A message there. A request to join the final fifteen minutes of a meeting. A document sent across with “Can you just have a quick look before this goes?”

None appears particularly significant.

Collectively, they can consume enormous amounts of cognitive capacity.

More importantly, they can prevent the organisation from learning to generate that certainty elsewhere.

Decision drag does not always look like delay

We often recognise decision drag when decisions obviously take too long. Papers move through excessive approval layers, meetings repeatedly defer an issue or executives become bottlenecks because everything requires formal sign-off.

But dependency can produce a quieter form of decision drag.

Work may still appear to move reasonably quickly because the trusted person is responsive.

They answer the message. They review the document. They attend the meeting. They make the call.

The underlying dependency therefore remains largely invisible.

You see it when the person becomes unavailable.

A decision that normally takes an afternoon suddenly waits two days. A meeting concludes without resolution because somebody wants to check with them. A team holds an email because they are unsure whether the wording will be supported. A customer issue sits unresolved because the person who normally knows how far the organisation can move is on leave.

The absence has not necessarily created the problem.

It has revealed where practical decision capacity was already concentrated.

Reassurance can become part of the workflow

This is one of the reasons simply documenting delegations does not necessarily distribute decision-making.

People need more than permission to act. They need sufficient context, capability and organisational confidence to use that permission.

If someone has repeatedly learned that difficult decisions are safer after consultation with a particular leader, removing the consultation step does not automatically create confidence. It can simply make the person feel more exposed.

This is why some attempts at empowerment fail.

The organisation announces that decisions should be made at the lowest appropriate level. Leaders are told to step back. Teams are encouraged to take ownership.

Yet the conditions surrounding the decision remain unchanged.

The consequences of getting something wrong may still be unclear. Senior leaders may still revisit decisions they dislike. Information may still be unevenly distributed. Decision boundaries may remain ambiguous. People may technically have authority without understanding the principles that should guide its use.

Under those conditions, ask them is not irrational behaviour.

It is risk management.

Capability can weaken without anybody losing skill

There is another consequence.

If one person repeatedly provides the final judgement on difficult situations, others receive fewer opportunities to develop that judgement themselves.

This does not mean they become less intelligent or less competent. It means the organisation gives them fewer repetitions.

Judgement develops partly through making decisions, seeing what happens, receiving feedback and adjusting. If difficult or ambiguous decisions consistently migrate toward somebody more experienced, the surrounding team can become highly capable at ordinary work while remaining dependent when circumstances move beyond the routine.

That creates an uncomfortable cycle.

The experienced leader continues receiving the hardest problems because they are best equipped to handle them.

Because they continue receiving the hardest problems, they accumulate even more experience.

Others receive fewer opportunities to build comparable judgement.

The capability gap widens.

The organisation then has even more reason to send the next difficult problem to the experienced leader.

What looks like evidence that the person is uniquely capable may therefore be partly the result of an operating model that continually gives them the opportunities from which capability develops.

This is not an argument against consultation

The solution is not to stop people asking for advice.

That would replace one simplistic rule with another.

Strong organisations contain consultation, challenge, peer review and escalation. Leaders should seek expertise when it improves a decision, and inexperienced people should not be expected to navigate every complex situation without support.

The structural question is different:

What happens to capability after the consultation?

Does the person leave better equipped to handle a similar situation next time?

Is the reasoning behind the decision made visible?

Are principles being transferred, or merely answers?

Does authority become easier to exercise after each interaction?

Or does every new variation of the problem return to the same person?

Good consultation should progressively increase organisational capability.

Dependency produces consultation that must continually be repeated.

Watch what happens when the answer is “What do you think?”

One of the simplest ways to observe the pattern is to change the response.

When someone asks a trusted leader what they should do, instead of immediately providing the answer, the leader asks:

What do you think?

The reaction can be revealing.

Sometimes the person already has a well-developed position. They are genuinely seeking another perspective and can explain their reasoning clearly. That is healthy consultation.

Sometimes they have a view but are reluctant to commit to it. The issue may be confidence, perceived risk or uncertainty about how much authority they really have.

And sometimes the question exposes that the organisation has become accustomed to outsourcing the judgement itself.

Each situation requires a different response.

But all of them provide more useful information than simply answering the original question.

The question underneath “ask them”

By the time ask them becomes an unwritten rule, the organisation has moved beyond a workload issue.

It has created a behavioural pattern.

People have learned where uncertainty should travel.

That pattern can survive restructures, new delegations, revised processes and repeated calls for empowerment because it is reinforced every time involving the trusted person produces a safer outcome.

Changing it therefore requires more than telling the leader to become less available or telling everyone else to take greater ownership.

The organisation has to understand what people are actually seeking when they ask.

Sometimes it is expertise. Sometimes it is context. Sometimes it is permission. Sometimes it is reassurance. Sometimes it is protection from the consequences of being wrong. And sometimes it is simply habit.

Those differences matter because distributing decision-making requires addressing the reason the decision keeps returning, not merely redirecting the request.

A useful place to start is therefore not:

Why does everyone keep asking this person?

It is:

What does involving this person provide that the organisation has not yet learned to provide another way?

Once that question can be answered, the dependency becomes much easier to see.

And once it can be seen, it can begin to be redesigned.

One of the easiest ways to become indispensable at work is to be useful when something goes wrong.

A problem appears that does not fit neatly within somebody's role, so you step in. A decision is stuck between two areas, so you help resolve it. A customer relationship becomes difficult, and because you know the history, you make the call. Someone is unsure how to interpret a policy, so they ask what you think. A deadline is approaching and the normal process is not moving quickly enough, so you find another way through.

None of these actions is inherently problematic. In many cases, they are exactly what we expect from capable leaders. Organisations need people who can exercise judgement, work across boundaries and respond when circumstances do not fit the process.

The difficulty emerges when an exceptional response to a particular situation becomes the normal response to an entire category of situations. The leader continues being helpful. The immediate problems continue being solved. But gradually, the organisation begins to incorporate that person's helpfulness into the way work gets done.

What started as assistance becomes expectation. What became expectation eventually becomes dependency.

Most dependency begins with a sensible decision

Organisational dependency rarely starts with someone deliberately deciding that all difficult problems should be routed through one person. It develops through hundreds of small decisions that make complete sense at the time.

Imagine a manager whose team encounters an unusual customer issue. The formal process does not provide a clear answer, but the manager has dealt with something similar before. They step in, make a judgement and resolve the issue. The customer is satisfied, the team can move on and the organisation avoids an unnecessary escalation.

The next time something similar happens, the team remembers what worked. Rather than beginning again with an uncertain process, they ask the manager. This is rational. They already know the manager understands the issue and can probably resolve it quickly.

After several repetitions, however, something has changed. The team is no longer simply benefiting from the manager's experience. It has begun incorporating access to that experience into its normal method of handling uncertainty.

The process might still say that team members have authority to resolve these matters themselves. The organisational chart might show responsibility distributed appropriately. Nothing formal necessarily changes.

But behaviour does.

A new operating rule has emerged without anybody writing it down: when this gets difficult, ask them.

The organisation learns from what works

We usually think of organisational learning as a positive thing. Teams learn better methods, develop expertise and improve processes based on experience. But organisations also learn workarounds.

If involving a particular person consistently makes a problem disappear, people learn to involve that person. If an executive responds more confidently when one trusted leader has reviewed a proposal, people learn to obtain that leader's approval before presenting it. If a customer becomes easier to manage when their longstanding contact intervenes, colleagues learn to bring that person back into the relationship whenever tension rises.

These behaviours do not require a formal instruction. They are reinforced simply because they work.

This is particularly powerful when the alternative feels slower or riskier. A team member might technically have authority to make a decision, but asking an experienced leader first feels safer. Two departments might theoretically be capable of resolving an issue between themselves, but involving the person who knows both directors gets an answer faster. A stakeholder relationship might officially belong to the organisation, but everyone knows who the stakeholder actually trusts.

Over time, the difference between the formal operating model and the real operating model grows.

On paper, responsibility is distributed.

In practice, uncertainty continues travelling toward the same people.

Helpfulness can prevent capability from developing

This creates an uncomfortable paradox for good leaders.

The better they are at stepping in, the less pressure there may be for the surrounding system to improve.

Consider a recurring problem between two functions. Each time it becomes serious, a senior leader intervenes. They understand both sides, know the personalities involved and can usually negotiate an acceptable outcome. Their intervention prevents disruption, protects relationships and keeps the work moving.

From an immediate performance perspective, this is valuable.

But if the leader resolves the issue every time, the organisation may never have to answer a harder question: why can't these two functions resolve this without them?

Perhaps decision rights are unclear. Perhaps the teams are measured against competing objectives. Perhaps neither manager has enough authority. Perhaps information is not shared at the right point in the process. Perhaps the relationship between the two leaders has deteriorated.

The senior leader's intervention can compensate for any of those weaknesses. Because the intervention works, however, the structural problem can remain untouched.

This is how capable people sometimes become buffers between an organisation and the consequences of its own design.

Their effectiveness does not cause the structural weakness, but it can make that weakness easier to tolerate.

The hidden operating model

Every organisation has formal systems: reporting structures, delegations, procedures, policies, workflows, governance arrangements and documented responsibilities.

It also has an informal operating model.

That model consists of what people have learned about how things actually get done.

Who needs to be consulted even though the process does not require it? Who can get a decision unstuck? Who knows the history? Who can persuade a difficult stakeholder? Who can tell you whether an executive is likely to support something before you formally submit it? Who understands how two systems interact even though nobody owns the connection between them?

This informal knowledge can be enormously valuable. No organisation can document every nuance of human judgement and relationships.

The problem is not that an informal operating model exists. The problem is when too much of it becomes concentrated around particular individuals.

At that point, a person's usefulness has become something more consequential. Their presence is now helping the organisation compensate for gaps in authority, process, knowledge, relationships or capability.

Remove the person and those gaps do not disappear.

They become visible.

Why indispensable can be a warning sign

Being described as indispensable is usually intended as a compliment. It signals trust, competence and importance.

There is, however, a structural question hidden inside the word.

Why is this person indispensable?

Sometimes the answer is entirely appropriate. They possess specialist expertise that the organisation intentionally concentrates in a particular role. They hold formal accountability for decisions that should not be distributed. They are performing work that genuinely requires their position or professional capability.

But sometimes indispensability has a different source.

The person knows things nobody else knows. They hold relationships nobody else can manage. They routinely make decisions other people could make but do not feel safe making. They mediate conflicts the structure repeatedly produces. They translate between teams that have never developed an effective way of working together. They rescue processes whenever normal conditions break down.

In those circumstances, indispensability is not simply a measure of the person's value.

It is also information about the organisation.

The more necessary one individual becomes to ordinary organisational continuity, the more important it is to understand what their presence is compensating for.

The cost appears gradually

This kind of dependency rarely produces an immediate crisis. That is another reason it can persist.

Instead, the effects accumulate.

A leader's calendar becomes increasingly fragmented because people need small amounts of their judgement throughout the day. Decisions queue when they are unavailable. Delegated work returns for reassurance. Meetings expand because their presence is considered necessary. Holidays require preparation disproportionate to the formal responsibilities of the role. Problems that should be resolved elsewhere remain dormant until the leader becomes available.

Eventually, the organisation may conclude that the leader has a time-management problem.

From the leader's perspective, the experience can be confusing. They may already have delegated substantial amounts of work. Their team might be capable and experienced. They may have good systems for managing their calendar and priorities.

Yet capacity does not seem to return.

The reason may be that tasks were never the primary source of the load. The organisation was consuming something else: access to their judgement, confidence, relationships, memory and ability to resolve uncertainty.

Those demands are harder to see on a workload report.

They are also harder to delegate one by one.

Saying no does not necessarily fix the system

Another common response is to tell the leader to establish better boundaries.

Again, there are circumstances where this is useful. Leaders do not need to attend every meeting, answer every question or rescue every problem.

But boundaries alone do not redistribute organisational capability.

If a leader simply stops answering questions without ensuring that somebody else has the context and authority to answer them, the dependency remains. It has merely become inaccessible. If they withdraw from a stakeholder relationship without transferring trust, the relationship can deteriorate. If they stop mediating a recurring conflict without addressing why the conflict keeps occurring, the organisation inherits the unresolved problem.

The objective is therefore not to make a helpful leader less helpful.

It is to understand what kind of help has become structurally necessary, and then decide whether that dependency should continue.

Some responsibilities should remain concentrated. Others should be deliberately transferred. Some knowledge needs to be documented. Some judgement needs to be developed in other people. Some relationships need broader organisational ownership. Some processes need redesign. And occasionally the organisation needs to acknowledge that a role has expanded well beyond what it originally intended.

That is a more demanding response than simply telling someone to say no more often.

It is also much more likely to create durable capacity.

Look for the repeated rescue

A useful way to find these dependencies is to look for repetition.

Not every intervention matters structurally. Leaders will always encounter unusual circumstances that require experience or senior judgement.

The more revealing situations are the ones that keep returning.

What problem do you repeatedly solve?

What decision repeatedly comes back to you?

Which relationship repeatedly requires your involvement?

Which meeting seems unable to proceed without you?

Where are you repeatedly translating between people or functions?

What stops moving when you are unavailable?

These patterns tell us something that a position description cannot. They show where the organisation's formal design and its actual behaviour have separated.

The question is not whether you should have helped the first time. You probably should have.

The question is what the organisation learned from your help.

When help becomes infrastructure

Strong organisations need helpful people. They need leaders who notice gaps, exercise judgement and step beyond narrow role boundaries when circumstances require it.

The objective is not to eliminate that behaviour. An organisation in which everyone responds to ambiguity with that's not my job would create a different and equally serious problem.

But there is a difference between a leader helping the organisation and the organisation quietly designing itself around the assumption that the leader will always help.

One is adaptive behaviour.

The other is dependency.

The transition between them can be difficult to see because there is rarely a moment when somebody deliberately makes the decision. It happens through repetition. A successful intervention becomes a familiar solution. The familiar solution becomes an expectation. The expectation becomes part of how work gets done.

Eventually, the leader's willingness to help is no longer simply a personal quality.

It has become part of the operating model.

And that leaves a useful question for both leaders and organisations:

What keeps working because someone keeps stepping in — and what would have to change if they stopped?

Most leadership roles come with a job description. It sets out responsibilities, reporting lines, accountabilities and expectations. It describes the team you will lead, the decisions you will make and the outcomes you will be responsible for delivering.

Then you start doing the job, and over time another role begins to form around the one you were actually hired to do. You become the person people call when something is unclear, the person who remembers why a decision was made three years ago, or the person who knows which stakeholder needs a phone call before an announcement goes out. You might be the one who can calm a difficult customer, interpret an ambiguous policy, get two teams talking again or navigate the process that everyone knows does not quite work.

None of this necessarily appears in your position description. Yet, gradually, the organisation can become dependent on you doing it.

The role you hold and the load you carry are not always the same

We tend to think about leadership load in terms of the formal responsibilities attached to a position: team size, budget, operational complexity, strategic accountability and regulatory exposure. Those things certainly create load, but some of the most consequential leadership load is informal. It accumulates through relationships, history, judgement, trust and repeated problem-solving.

Perhaps you are the person who can get Finance to move quickly because you know who to speak to. A senior executive might regularly ask you to sense-check difficult decisions because they trust your judgement. Your team may have learned that bringing an issue to you is faster than navigating the formal process, while clients might insist on dealing with you because you have carried the relationship for years. There may even be important organisational history that nobody properly documented but you still remember.

Individually, these things can look like evidence that you are good at your job. Often they are. The issue is not that capable people become trusted or that experienced leaders develop valuable relationships. The issue begins when personal capability quietly becomes organisational dependency.

Useful people attract more usefulness

Organisations rarely set out to create this kind of dependency. It usually develops for perfectly rational reasons. Someone proves reliable, so they are given more responsibility. They solve a difficult problem, so people bring them the next one. They build trust with an important stakeholder, so they become the natural point of contact. They understand a complicated process, so colleagues ask them rather than spending hours trying to interpret it themselves.

Each decision makes sense in isolation. Repeated over months or years, however, something structural can happen. Work begins to route through the person rather than through the organisation. Their judgement becomes a control mechanism, their relationships become infrastructure, their memory becomes organisational knowledge and their availability becomes part of the operating model.

The difficult part is that none of this necessarily looks like failure. Quite the opposite. The person continues solving problems, decisions continue being made and important relationships remain intact. From the organisation's perspective, the arrangement can appear to be working extremely well.

That apparent success is precisely what can conceal the weakness underneath it.

When high performance conceals structural weakness

Consider a leader who seems indispensable. They know the major customers, can answer almost any operational question, are routinely approached by their team for advice and have the confidence of senior executives. When a complicated problem emerges, things seem to move once they become involved.

It is easy to look at that situation and see exceptional leadership. It may well be exceptional leadership. But there is another question worth asking: what has the organisation become dependent on that person carrying?

That question shifts the focus from the individual's performance to the structure supporting it. Could someone else make the same decisions with reasonable confidence? Does the team understand the principles behind the leader's judgement, or have they simply learned to ask them? Are important stakeholder relationships held by the organisation or primarily by one individual? Is critical knowledge captured and accessible? If that leader disappeared for six weeks, would responsibility transfer cleanly, or would decisions, relationships and unresolved problems begin accumulating around the empty chair?

These are not questions about whether the leader is capable. They are questions about whether the organisation has successfully converted individual capability into organisational capability.

The invisible second job

This is why some leaders eventually find themselves carrying what amounts to two roles. There is the visible role they were employed to perform: leading the team, delivering strategy, managing performance, meeting targets, attending meetings and making the decisions formally assigned to them.

Alongside it, an invisible role can develop. It consists of remembering context, interpreting ambiguity, connecting people, rescuing difficult situations, translating between functions, escalating issues, reassuring others, troubleshooting exceptions and holding together the spaces between formal responsibilities.

That second role rarely arrives as a deliberate assignment. It accumulates one exception, one relationship, one workaround and one “Can you just take a look at this?” at a time. Eventually, a leader can spend a significant proportion of their capacity maintaining organisational continuity without either the leader or the organisation fully recognising that this is what they are doing.

From the outside, the person simply looks busy. From the inside, they may experience something different: despite building a capable team and trying to distribute work, everything important still seems to find its way back to them.

Why this is not simply a delegation problem

The conventional response to an overloaded leader is often that they need to delegate more. Sometimes that is entirely appropriate, but delegation is an incomplete answer when the underlying problem is structural.

A leader cannot simply delegate a relationship that exists primarily because of years of personal trust. They cannot transfer judgement if nobody else has been given the context or authority required to exercise it. Institutional memory cannot be delegated if it has never been captured, and responsibility cannot be distributed effectively when decision rights remain ambiguous. Telling somebody to let go achieves very little if the organisation continues routing uncertainty back to them whenever circumstances become difficult.

This helps explain why capable leaders can remain overloaded even after making genuine efforts to delegate. They may have successfully transferred tasks while continuing to carry the judgement, risk, relationships and exceptions behind those tasks. The visible work has moved, but much of the underlying load has not.

That distinction matters because otherwise we risk diagnosing an organisational design problem as a personal productivity problem.

Looking beyond formal responsibility

A more useful conversation therefore starts with something broader than What are you responsible for? It also asks: What are you carrying that the organisation has never formally recognised?

The answer might include decisions that other people technically have authority to make but continue bringing back to you. It might include relationships that cannot yet function effectively without your involvement, knowledge that exists primarily in your head, conflicts you repeatedly mediate because the operating structure does not resolve them, or exceptions that require your judgement because the formal process works only when circumstances are normal.

It can also include less visible forms of load. A team may have come to rely on one leader to provide reassurance whenever uncertainty rises. Senior colleagues may depend on that person to translate between competing priorities. Customers may expect access to them because that is how trust has historically been maintained.

None of these things automatically indicates dysfunction. Leadership inevitably involves judgement, relationships, ambiguity and trust. The structural concern is concentration. When too much organisational continuity depends on one person's presence, responsiveness, memory or judgement, leadership load is no longer only a question of how much that individual can handle. It has become a question about how the organisation itself operates.

The job description is only the beginning

A position description tells us what an organisation intended a leader to carry. It does not necessarily tell us what the organisation has gradually learned to depend on them carrying.

That difference matters for succession because a replacement can inherit the formal role without inheriting the informal infrastructure surrounding it. It matters for resilience because a team can appear well staffed while still being highly dependent on one person's judgement. It matters for decision speed because authority can be distributed on paper while decisions continue travelling back to the same individual. And it matters for leadership wellbeing because someone can become overloaded by responsibilities that are largely invisible when their workload is assessed.

This is why asking a heavily relied-upon leader to become more efficient, manage their time better or delegate more can sometimes miss the problem entirely. Before trying to change the person, it is worth examining the system that has formed around them.

The more revealing question may be:

What wasn't in the job description — but now depends on them anyway?