Leadership should build capability that survives without constant rescue, not make one person the operating system.
Some leaders become very good at being needed.
Not intentionally, always.
Sometimes it happens because they are competent. They answer quickly. They see the issue before everyone else. They calm the room. They make the call. They unblock the work. They remember the context. They carry the tension. They translate the strategy. They know where the bodies are buried, metaphorically, legally, and sometimes in the project folder.
Useful, obviously.
Also dangerous.
Because after a while, the team does not have a leader.
It has a central nervous system with a calendar invite.
Everything routes through one person.
Questions. Decisions. Confidence. Permission. Escalations. Morale. Interpretation. The little “can you just sense-check this?” messages that look harmless until they become the entire operating model.
From the outside, this can look like strong leadership.
The leader is responsive.
Present.
Trusted.
Essential.
Which is lovely, until you realise “essential” can be another word for “structural bottleneck with a flattering job title.”
The heroic spec
The heroic leader expectation sounds noble.
Be the one who knows.
Be the one who decides.
Be the one who motivates.
Be the one who holds the room steady.
Be the one who sees the future.
Be the one who protects the team.
Be the one who fixes the thing when the thing becomes weird, political, emotional, urgent, ambiguous, or all of the above because apparently modern work enjoys variety.
Written as an operating spec, it becomes absurd.
One human must act as decision engine, emotional regulator, escalation pathway, strategic interpreter, motivational source, conflict absorber, quality filter, rescue system, and symbolic parent for the work.
Every day.
Under pressure.
While also doing their own job.
No problem.
Very scalable.
Obviously fine.
This is where leadership advice often becomes slightly unhinged. It praises the person carrying the system instead of asking why the system needs to be carried that much.
Dependence can look like trust
This is the tricky part.
A dependent team can feel close.
People come to the leader because they trust them. They want their view. They value their judgment. They feel safer when the leader is involved.
That is not bad.
Trust matters.
But trust becomes fragile when it turns into waiting.
Waiting for approval.
Waiting for clarity.
Waiting for rescue.
Waiting for the leader to absorb the discomfort that the team has not learned how to hold.
Waiting for the person at the centre to restart the system every time it stalls.
At that point, the leader has not built capability.
They have built dependency.
And dependency has a cost.
It slows decisions. It weakens ownership. It concentrates risk. It makes the leader tired in a very specific way: not just busy, but metabolically responsible for everyone else’s uncertainty.
That is not leadership maturity.
That is over-functioning with better stationery.
The goal of leadership is not to be the person everything runs through. It is to build the conditions where capability survives without constant rescue.
Leaders still matter
Now, the boundary.
This is not an argument for leader absence.
It is not “just empower your team” written on a mug and left unattended in a workshop.
Leaders matter.
A lot.
Transformational leadership research has long shown that leaders can shape motivation, meaning, trust, development, and performance. Empowering and shared leadership research also suggests that teams can benefit when leadership functions are distributed and people have more ownership, voice, and decision space.
But that does not mean the leader disappears.
It means the leader’s job changes.
Less permanent rescuer.
More condition designer.
Less answer machine.
More capability builder.
Less emotional infrastructure.
More architect of trust, decision rights, feedback loops, learning routines, and useful autonomy.
The leader still sets direction.
Still makes hard calls.
Still protects standards.
Still handles risks the team should not have to carry alone.
But they do not become the entire operating system.
That distinction matters.
Because “be a better leader” often gets interpreted as “carry more.”
More emotional availability.
More strategic clarity.
More coaching.
More decisiveness.
More inspiration.
More resilience.
More capacity to absorb everyone else’s friction without occasionally walking into the sea.
But carrying more is not always leadership.
Sometimes it is the sign that the system has not learned to stand.
Build the team’s legs
A self-sustaining team is not leaderless.
It is not a group of people floating around in beautiful autonomy, making decisions through vibes and shared documents nobody updates.
It has structure.
It has standards.
It has feedback.
It has authority boundaries.
It has ways to resolve conflict.
It has ways to learn.
It knows which decisions belong where.
It knows when to escalate and when to move.
It knows how to disagree without immediately needing the leader to turn into a human seatbelt.
That is what makes it self-sustaining.
Not independence as abandonment.
Independence as designed capability.
The leader’s job is to reduce unnecessary dependence over time.
That may mean naming decision rights clearly.
Building coaching into the system, not just into the leader’s calendar.
Creating feedback loops the team can use without waiting for annual performance theatre.
Making information visible enough that people do not need to ask for permission just to understand the work.
Teaching the team how to hold tension, not just smoothing tension every time it appears.
Developing future leaders before a vacancy turns succession into panic with a spreadsheet.
None of that is soft.
It is operational.
A team that cannot move without the leader is not agile.
A team that cannot decide without the leader is not empowered.
A team that cannot learn without the leader is not developing.
A team that cannot stay coherent without the leader is not strong.
It is attached.
The test
The real test of leadership is not how well the system performs when the leader is in the room.
That is the easy version.
The real test is what keeps working when the leader steps away.
Do decisions improve or freeze?
Does conflict become useful or go underground?
Does ownership deepen or wait politely?
Does learning continue or pause until the next one-on-one?
Does the system keep thinking?
That is the leadership question.
Not “how indispensable am I?”
That is ego with a calendar problem.
The better question is:
What still depends on me that should now belong to the system?
That question can sting.
Good.
Useful questions often arrive without a hospitality certificate.
But it is the right question if the goal is not to be admired for carrying the weight.
The goal is to build something that can carry more of itself.
A leader should matter.
They should not be the system.
Leadership should reduce the system’s dependence on the leader over time.
This essay draws on research into transformational leadership, empowering leadership, shared leadership, motivation, and team learning. Bass’s work on transformational leadership provides the foundational leadership frame, while Judge and Piccolo’s and Wang and colleagues’ meta-analytic work support the broader claim that transformational leadership can relate to performance across contexts. Ahearne, Mathieu, and Rapp’s work on empowering leadership supports the idea that leaders can design more ownership and capability into teams. Pearce and Sims, Carson and colleagues, and Nicolaides and colleagues support the importance of shared leadership and distributed leadership functions in team effectiveness. Deci, Olafsen, and Ryan’s work on self-determination theory in organisations supports the role of autonomy, competence, and relatedness in work motivation. Edmondson’s psychological safety research supports the importance of team environments where people can speak, learn, and take interpersonal risks. These sources do not prove any proprietary self-sustaining leadership model; they support the narrower claim that effective leadership can build conditions for capability, autonomy, trust, and shared responsibility rather than permanent leader-dependence.