The Dependency Spiral
The pattern in which capable people compensate for weaknesses in the system until the organisation becomes dependent on them to function
IN ONE LINE
The more the system relies on someone to compensate for what it cannot do, the less it learns to do without them.
Three minutes.
What it is
It usually starts with someone being useful.
A capable person sees something that needs doing and steps in. They make the decision, fix the work, chase the answer or fill the gap. It is quicker than fixing whatever allowed the problem to happen in the first place.
The work gets done.
So next time, they step in again.
Each intervention makes sense. But something else is happening underneath it. The system gets another successful result without developing the capability that should have produced it.
The individual becomes a little more necessary. The people around them become a little less able to operate without them. More work and more decisions begin to flow towards the person who can be trusted to get things done.
Eventually, the organisation has solved one problem by creating another.
The hero becomes the infrastructure.
This can happen anywhere. A CEO becomes so operationally embedded that the business cannot function without them. A team stops making decisions unless a particular manager is present. A function relies on knowledge that exists almost entirely in one person’s head. A board depends on one NED to provide the challenge that should exist across the board.
The people are different. The mechanism is the same.
The organisation has concentrated too much of its ability to function in too few people.
What creates it
Capability. Dependency often forms around highly capable people for an obvious reason: they can solve the problem. Their competence makes stepping in rational.
Weak infrastructure. Processes, roles, systems, skills or decision rights are not strong enough to carry the work independently, so somebody compensates.
Speed. Fixing the immediate problem is faster than fixing the system. Under pressure, today’s result wins.
Retained authority. Decisions continue travelling upward because the organisation has never made clear what can safely be decided without senior involvement.
Rewarding the result rather than how it was produced. The organisation sees that the work got done. It does not see the dependency created in getting it done. The Codex is particularly explicit about this at CEO level: boards measure output, investors reward results, and the rational response can be for the CEO to keep delivering personally.
How to recognise it
There are people everybody knows they cannot afford to lose. Their absence would not merely be inconvenient. Important parts of the organisation would struggle to function.
Decisions keep travelling upwards. Work reaches senior people that should be resolvable much closer to where it happens.
The most capable people are permanently overloaded. Their competence attracts more work, which leaves them less time to build capability around them.
Senior people are doing surprisingly junior work. They are writing the deck, correcting the document, chasing the numbers or checking work that should not require their attention.
Delegation happens, but authority doesn’t travel with it. Someone else owns the task until an important decision appears, at which point the work comes straight back.
New people arrive with high expectations and gradually become less autonomous. They learn that important work will be checked, changed or taken back anyway.
Things move faster when a particular person gets involved. This feels like evidence of their value. It may also be evidence of the organisation’s dependency.
At its worst, the organisation starts confusing dependence with performance.
The person who is holding everything together looks indispensable because they are.
That is precisely the problem.
What it gets mistaken for
Most often, exceptional leadership.
The person works extraordinary hours, knows everything, catches problems before they become visible and can unblock almost anything.
From the outside, this can look like enormous personal effectiveness.
It can also be mistaken for a weak team. If the leader continually has to step in, it seems reasonable to conclude that the people below them are not capable enough.
But the direction of causality is not always that simple.
When work is repeatedly corrected, decisions are retained above and authority is never genuinely transferred, people adapt. They ask before acting. They wait for approval. They invest less in decisions they expect someone else to remake.
The Codex describes this as learned helplessness produced by the system, rather than a personal failing.
Sometimes the person rescuing the system is also preventing it from learning how not to need rescuing.
Why it persists
Because in the short term, it works.
The decision gets made. The client gets an answer. The document gets fixed. The deadline is rescued.
Removing the dependency initially feels slower and riskier than continuing to use it.
There is also very little incentive to challenge something that appears to be producing results. The individual is praised for delivering. The organisation benefits from the rescue. Everyone has a reason to repeat the behaviour.
Until the person is unavailable.
Only then does the structural risk become obvious.
The commercial consequence is particularly stark at CEO level: if the business has effectively become the CEO, it carries key-person risk and cannot be sold on the same basis as a business capable of operating independently.
What becomes possible
The goal is not to make your best people less important.
It is to make them important for better reasons.
When dependency reduces, senior people can spend more time on the work that genuinely requires their judgement rather than compensating for gaps below them. Decisions move closer to the people with the information to make them. Knowledge spreads. Capability grows because people are allowed to exercise it.
The organisation also becomes more resilient. Holidays stop being operational events. Someone leaving is painful rather than catastrophic. Growth does not require the same handful of people to stretch indefinitely.
And something important happens to the people who were previously indispensable.
They get room to grow too.
The prize is not an organisation that needs its best people less. It is an organisation that needs less of them for things other people should be able to do.
Where to start
Don’t start by telling the indispensable person to delegate more.
Look at what keeps coming back to them.
For one week, notice every task, decision, correction and escalation that reaches someone significantly more senior or capable than the work should require.
Then ask:
Why did this need this person?
Was information missing? Was authority unclear? Was capability genuinely absent? Was the quality bar unknown? Was it simply quicker to ask the person who always knows?
Don’t immediately push the work back down.
Find the condition that keeps pulling it up.
The aim is not to remove the person from the loop. It is to understand why the loop needs them.
Last updated October 2026
