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.