Every organization has people who always find a way.
When a deadline begins to slip, they recover it.
When information is missing, they remember it.
When departments fail to coordinate, they become the bridge.
When something unexpected happens, everyone turns toward the same person.
And somehow, the work gets done.
Organizations often describe these people as indispensable.
The praise is usually deserved.
But hidden inside that praise is a warning.
If success depends on one person repeatedly rescuing the work,the person may be exceptional—but the system is fragile.
The indispensable person
Imagine a school administrator who knows every family, remembers every exception, understands every informal agreement and notices problems before anyone else sees them.
Or an operations manager who knows which supplier to call, which process can be bent, which department needs to be warned and how to get a stalled project moving again.
Or the founder of a community initiative who holds the relationships, the history, the funding logic and the trust of everyone involved.
These people create enormous value.
They may be the reason the organization survived its earliest years.
But over time, their commitment can begin concealing what the organization still needs to learn.
Everyone becomes accustomed to the rescue.
Questions travel to the same person.
Decisions wait for the same person.
Problems remain invisible until that person notices them.
And because the work keeps getting done, the underlying weakness can remain hidden for years.
When competence becomes infrastructure
Organizations are supposed to have infrastructure.
Clear responsibilities. Accessible information. Dependable routines. Useful feedback. Ways to make decisions and recover from mistakes.
But when those things are weak, a highly capable person often becomes the infrastructure instead.
The calendar lives in their head.
The process lives in their inbox.
The standards live in their personal judgment.
The relationships exist because they maintain them.
The quality control happens because they check everything.
The organization appears coordinated, but the coordination is being produced manually by one person.
This arrangement can look impressively efficient—until that person becomes overloaded, takes a holiday, changes roles or leaves.
Then the organization discovers that it did not own the capability.
It was borrowing it.
The hidden cost of heroic work
Heroic effort produces short-term relief.
It can also create long-term consequences.
- Decisions slow down because people wait for the person they trust.
- Others stop developing judgment because difficult situations are routinely taken away from them.
- Knowledge remains private because explaining it feels slower than solving the problem directly.
- Recurring failures are repaired without changing the conditions that keep producing them.
- The most capable person becomes the organization's greatest bottleneck.
Eventually, the hero may become exhausted.
But the deeper problem is that everyone else has been prevented from becoming more capable.
Not intentionally.
Usually, the pressure of the moment made rescue feel like the responsible choice.
There was no time to explain.
No room for someone else to struggle.
No tolerance for a slower first attempt.
So the hero stepped in again.
And each successful rescue made the next rescue more likely.
Heroics and leadership are not the same
Strong leaders often behave heroically when circumstances require it.
There are moments when someone must take responsibility, make the difficult decision or carry more than their share.
The problem is not the exceptional effort.
The problem is allowing exceptional effort to become the normal operating model.
A hero closes the gap.
A leader asks why the gap keeps appearing.
A hero knows what to do.
A leader makes that knowledge available to others.
A hero protects the outcome.
A leader develops more people who can protect it.
A hero saves the day.
A leader builds an organization that needs fewer days to be saved.
Build shared capability
Moving beyond heroic dependence does not mean reducing the influence of capable people.
It means using their capability differently.
Instead of asking them to keep carrying the work, ask them to help make the work carryable by others.
Begin with the invisible work.
- What are they noticing that others do not notice?
- What information do they hold that others cannot easily access?
- What decisions repeatedly return to them?
- What relationships depend entirely on their personal involvement?
- What problems do they quietly prevent before anyone else knows they existed?
That is where the real operating system is hiding.
The goal is not to turn every judgment into a checklist.
Complex work will always require experience, interpretation and trust.
But the organization can make expectations clearer, information more visible and responsibility more distributed.
It can allow more people to practise making decisions.
It can move feedback closer to the work instead of waiting for one person to inspect everything at the end.
It can make important relationships organizational rather than purely personal.
The objective is not to make exceptional people less important.It is to make what they know more valuable.
Design for absence
One of the clearest tests of a system is what happens when an important person is not available.
Does the work continue?
Can someone find the information?
Do people understand who can decide?
Can the organization recognize a problem before it becomes a crisis?
Does responsibility move—or does everything simply wait?
Absence exposes architecture.
It reveals whether authority was genuinely distributed, whether knowledge was made accessible and whether people were trusted to develop judgment.
This does not require creating a bureaucracy around every task.
Often, it begins with a few practical changes:
- Clarify the outcome people own, not merely the tasks they perform.
- Make critical information visible where the work happens.
- Identify recurring decisions and move them closer to the people affected.
- Allow others to handle difficult situations while support is still available.
- Review each rescue and ask what would prevent the same emergency next time.
Most importantly, stop treating every imperfect first attempt as evidence that only the hero can do the work.
Capability grows through responsibility.
If we never allow people to carry meaningful weight, we should not be surprised when they remain unable to carry it.
Make it inevitable
Organizations need committed people.
They need individuals who care deeply, act decisively and refuse to let important things fail.
But the greatest contribution those people can make is not rescuing the organization forever.
It is helping the organization become more capable because they were there.
The strongest leader does not remain the only person who understands.
The strongest founder does not remain the only person who can be trusted.
The strongest team does not collapse when its most experienced member steps away.
The work continues because knowledge has moved, judgment has developed, relationships have widened and responsibility has become real.
That is not a loss of importance.
It is the evidence of impact.
The best system does not need a hero.
It creates more people who can act with courage, competence and ownership when the moment requires it.