The Leadership Trap of Being the Person Who Always Steps In
Rescue behaviour can solve the immediate problem while preventing people and systems from learning.
Stop stepping in: the leadership trap of always rescuing
YouTubeThis article is inspired by real leadership coaching conversations. All identifying details, including names, genders, roles, teams, organisational structures, projects and business context, have been removed, generalised or combined to protect privacy. Any transcript excerpts have been edited for clarity and anonymity while preserving the underlying leadership lesson.
The instinct to step in
There is a phrase I hear often from very capable people, and I have used it plenty of times myself: "I'll just do it."
It usually comes from a good place. Something needs to move. The person understands the problem, knows how to solve it, and can probably get it done faster than explaining it to someone else. In the moment, stepping in looks efficient and responsible. Often it works, which is exactly why the habit is so difficult to question.
One of my coaching conversations recently was with someone who had every reason to stay closely involved in a piece of work. They had the context, the experience and the capability to drive it. The work would probably have been safer with them at the centre of it.
And I found myself encouraging them to step back.
Not because they had failed, and not because the work did not matter. The reason was that other people around the work needed something more valuable than assistance. They needed ownership. They needed the chance to make decisions, carry the responsibility, and experience what happens when the answer is not immediately supplied by the most experienced person in the room.
The edited version of what I said was roughly:
"The natural response for a capable leader is often, 'I'll go and do it.' Instead, can you stay informed and supportive without becoming the person who owns the outcome?"
That distinction between support and rescue became the centre of the conversation.
Support or rescue?
We often call something delegation when it is really task distribution. The senior person still holds the decisions, still stays close enough to correct the direction, and still becomes the safety net whenever the work gets uncomfortable. The other person is doing more, but they are not necessarily owning more.
Real delegation feels different because it contains risk. The person may make a decision you would not make. They may take longer. They may struggle with something you would have solved quickly. They may even make a mistake that you could have prevented.
That discomfort is part of the development.
If I remove every difficult moment before somebody has to work through it, I also remove part of the evidence they need to build confidence in their own judgement. And if the team learns that sufficiently difficult work will always be taken back by the most experienced person, then we have not built capability. We have built a dependency with a very competent person at the centre of it.
The same rescue pattern appears at an organisational level. Something is not thought through properly early enough, the problem grows, urgency arrives, and suddenly capable people are pulled in from every direction. Priorities move. Extra effort is applied. The immediate situation gets saved.
Again, the rescue works.
But what did the organisation learn? If poor qualification, weak ownership or an unrealistic decision is always followed by a heroic recovery effort, we can accidentally protect the original behaviour from its consequences. The people who made the early decision may never feel the real cost because someone else absorbs it later.
That led me to another question in a separate conversation:
"Are we comfortable allowing people to own the consequences of their decisions, or do we automatically step in and rescue the situation?"
I do not mean that leaders should sit back and watch something fail simply to prove a point. There are moments where stepping in is absolutely the right decision. Customers, colleagues and important outcomes should not become teaching aids for leadership theory.
The question is whether intervention has become the default, and whether we ever pause to ask what the intervention is teaching the system.
What should they stop carrying?
This also connects to capacity. I used to think about capacity mostly as an efficiency problem: how do we help someone carry more, remove blockers, streamline the work, or make them faster? I still ask those questions, but with senior people I increasingly find myself asking something else first: what should this person stop carrying?
That is a very different question.
Experienced people are magnets for organisational gaps. They know more, move faster, and have built trust, so work naturally accumulates around them. Every time they successfully absorb another problem, the organisation gets another reason to send the next one their way. Eventually we call them indispensable, even though their indispensability may partly be evidence that we have not built enough capability around them.
One of the smallest conversations I had recently brought this home in a different way. Someone was clearly unwell but was still trying to stay engaged. Telling them to rest would have been easy. The more important part was removing the perceived consequence of resting.
I said, in edited form:
"Nothing is urgent. Log off and look after yourself. If anyone needs support, send them to me."
The second sentence is what mattered. If we tell people to disconnect while making them feel that everything will fall apart in their absence, we have not really given them permission to disconnect. Leadership sometimes means taking the short-term load so that somebody can genuinely step away.
Judging the intervention
That may sound contradictory to the rest of this article. On one hand I am saying leaders should stop rescuing. On the other, I am describing a moment where I deliberately stepped in. I think that tension is exactly the point.
There is no universal rule that says intervention is good or bad. The real judgement is why you are stepping in and what your intervention creates afterwards. Are you protecting someone who genuinely needs support, or are you preventing someone from developing? Are you safeguarding an important standard, or are you compensating for a weak decision that will simply repeat next month? Are you the only person who can carry this, or are you the person who finds it hardest to let somebody else try?
For the people I was coaching, the shift was not "do less." It was to become more intentional about when they step in. Sometimes the right answer is yes. Sometimes it is no. Sometimes it is, "I will support you, but I am not taking this back."
My own follow-up is to watch my intervention instinct more closely. Before I step into something, I want to ask whether I am uniquely required, whether I am protecting something that genuinely matters, or whether solving it myself simply feels faster and more comfortable.
Because being the person who always steps in feels useful. Often it even looks like strong leadership from the outside.
But if every hard problem eventually ends up with the same person, the organisation may be becoming more dependent at exactly the moment it thinks it is becoming more resilient.
The question I want to keep asking is simple: if I step in here, what might I be preventing someone else, or the system itself, from learning?
Continue exploring
- Article
The Higher You Go, the Less It Should Be About Having the Answer - AI Skill
Delegation Planner - Free resource
Handing over the decision
