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?