How Do I Stop Managers Rescuing Poor Performers Instead of Managing Them?

Rescue can look like good management

This is why it is so dangerous. The manager looks helpful. Responsive. Committed. Protective of the customer. Protective of the team. And often they are all of those things. But ask:

“Is this helping the employee become more capable?”

Or:

“Is this simply preventing the consequences of their underperformance from becoming visible?”

That is the distinction.

Support should build capability

Support says:

“Let’s work out what is getting in the way.”

“What do you think?”

“What have you tried?”

“What do you need?”

“What are you going to do next?”

Rescue says:

“Leave it with me.”

Support keeps responsibility with the employee. Rescue transfers it to the manager.

Managers often rescue because they can do it faster

This is understandable. The manager knows the work. They can fix the mistake in ten minutes. Teaching the employee may take an hour. So they think:

“I’ll just sort it this time.”

Then next time comes. And next time. And next time. The fastest solution today creates tomorrow’s dependency.

Ask who is carrying the problem ball

When the employee brings a problem, who leaves carrying it? The employee? Or the manager? That question is incredibly revealing. If the manager repeatedly leaves with the next action, the employee is learning that difficult work can be handed upwards.

Do not make the manager the shock absorber

Some managers become the permanent shock absorber between poor performance and the rest of the business. They: fix; cover; smooth; apologise; rework; stay late; fill the gap. Eventually senior leadership may believe the team is performing better than it really is. Because the manager is absorbing the difference.

Rescue hides the evidence

This is a major problem. If the manager fixes every miss before anyone sees it, what evidence remains? Very little. Then when the manager eventually says: “This person has been underperforming for months,” the business asks:

“Where is the evidence?”

The answer is:

“I kept fixing it.”

That is precisely why rescuing is so damaging.

Let the gap become visible

This does not mean allowing customers to suffer unnecessarily. It means recording what happened. What was expected? What actually happened? What intervention became necessary? Who had to compensate? Now the underlying performance gap remains visible even if the business still had to protect the outcome.

Protect the customer and still manage the performance

These are not mutually exclusive. You may need to step in to protect: a major customer; a legal obligation; a safety issue; a serious commercial risk. Fine. But after the incident, return to the performance issue. Do not let the emergency intervention become the end of the story. Ask:

“Why did I need to step in?”

Then manage that.

Debrief the rescue

Whenever a manager genuinely had to intervene, ask afterwards:

“What happened?”

“What did you miss?”

“What should you have done earlier?”

“What will you do next time?”

“What part of this will you own from now on?”

Otherwise the rescue becomes training for repetition.

Do not repeatedly do someone’s job for them

At some point the question has to become:

“Why am I doing this part of your role?”

That can feel confronting. But it may be exactly the right question. Managers are not employed to permanently carry the work of underperforming employees.

Managers often rescue to avoid a difficult conversation

This is another big cause. Fixing the work can feel easier than saying:

“This is not meeting the standard.”

So the manager chooses the operational fix over the management conversation. Today feels easier. Tomorrow becomes harder.

Ask what conversation the manager is avoiding

Whenever you see repeated rescue, ask:

“What conversation should have happened here?”

Perhaps: the missed deadline; the poor preparation; the recurring error; the lack of ownership; the behaviour; the capability gap. Usually there is one.

The employee may not realise how serious the gap is If management continually fixes things behind the scenes, the employee may genuinely think they are doing fine. Then six months later they are shocked by formal performance concerns. That is unfair. The employee needs to see the gap.

Clarity is part of management.

Rescue can create learned helplessness

If someone repeatedly experiences: problem appears; manager takes over; manager fixes it, what incentive is there to build stronger judgement? Over time they may stop trying to solve difficult issues themselves. Not necessarily consciously. The system has taught them what works.

Change what happens when the problem arrives

Instead of:

“Give it to me.”

Ask:

“What do you think is going on?”

“What have you tried?”

“What are your options?”

“What do you recommend?”

“What are you going to do?”

Now the employee has to think.

Do not answer too quickly

Managers who know the answer can barely tolerate the silence. They ask:

“What do you think?”

Three seconds pass. Then they answer it themselves. Wait. Let the employee struggle a little. Thinking is part of the development.

Give enough support, not all the support

Perhaps the employee genuinely needs help. Give: context; training; guardrails; experience; feedback. But do not automatically take ownership. The objective is to increase capability.

Distinguish skill gaps from effort gaps

This matters. Someone may not know how. That needs development. Someone may know how but repeatedly not apply themselves. That is different. Do not use endless coaching to solve an effort problem.

Distinguish capability from care

Ask whether the person gives a fuck. Are they trying? Preparing? Responding to feedback? Taking responsibility? Raising risks? If yes, investment may be worthwhile. If not, the issue may be less about skill and more about ownership.

Do not reward avoidance

If the employee delays a difficult task long enough and the manager eventually does it, what has the system rewarded? Delay. That is not what you want.

Keep the action with the employee

At the end of the conversation, ask:

“So what are you going to do?”

Then:

“By when?”

Make sure the answer belongs to them. Do not finish with:

“I’ll take care of it.”

Follow up

Support without follow-up is weak. What happened? Did they do it? What did they learn? What still needs work? This is accountability.

Managers sometimes rescue because standards are unclear

If the manager has never clearly said what good looks like, they may not feel confident challenging the gap. Fix the standard. What does success look like? What behaviour is expected? What does done mean? Then the performance conversation becomes easier.

Rescue often hides weak delegation

The manager says:

“They can’t do it.”

But did they ever genuinely delegate it? Was the outcome clear? Did the person have authority? Did the manager let them practise? Or did the manager keep taking the work back at the first wobble? Sometimes the employee never had a real chance to build capability.

Do not mistake one failed attempt for proof

Someone tries. Gets it wrong. Manager says:

“See? I knew I’d have to do it myself.”

That may be premature. Was the mistake recoverable? Was the reasoning sensible? What did they learn? Development needs repetition. But do not mistake endless repetition for development The opposite problem exists too.

If the same mistake happens again and again after clear coaching, something else is going on. Do not keep calling it development forever. Repeated evidence should change the conversation.

Ask whether rescue is now compensating

This is the key threshold. Support becomes compensation when the manager repeatedly fills the same gap and the employee does not become more capable. At that point, ask:

“Are we still developing this person, or are we simply making the role work around them?”

That is a very different question.

Look at the effect on the manager

Rescuing has a cost. The manager: works longer; has less time for their own role; becomes frustrated; loses strategic capacity; starts resenting the employee. Eventually they may burn out. A performance gap below them becomes a capacity problem above them.

Look at the effect on the team

Other employees notice too. They see who gets rescued. Who gets away with things. Who carries the extra work. That can damage fairness quickly.

Good employees may become the secondary rescuers

This is particularly dangerous. The manager does not fix everything themselves. Instead they give the work to the reliable employee. Now the high performer becomes the shock absorber. That is how poor performance starts costing you your best people.

Do not punish reliability with more rescue work

If someone is good, do not continually reward them with:

“Can you just fix this?”

Development opportunities are one thing. Permanent compensation for somebody else is another.

Use evidence

Track: what was expected; what missed; how often; what support was given; what intervention was needed; what changed afterwards. Now you can see whether support is working.

Ask whether the gap is shrinking

This is a simple test. After coaching, is the employee: more capable? more reliable? more independent? If yes, keep going. If not, investigate why.

Make the employee see the impact

Sometimes people do not understand what their gap causes. Explain.

“When you miss this, Sarah has to stay back.”

“When you don’t raise the issue, I have to step in with the customer.”

“When this report is incomplete, Finance has to redo it.”

Now the consequence becomes real.

Do not use shame

Impact is useful. Humiliation is not. The aim is awareness and responsibility. Not embarrassment.

Require early warning

One way to reduce rescue is to insist that risk is raised early. If the employee knows they will miss a deadline, they need to say so before the deadline. Then management has options. Late silence creates emergencies. Emergencies invite rescue.

Teach renegotiation

If the commitment genuinely needs to change, renegotiate it consciously. What changed? What is the new date? What else is affected? That is far better than waiting until failure forces the manager to take over.

Remove unnecessary dependencies

Sometimes the employee keeps failing because the system makes them dependent. No authority. No access. No information. Fix those problems. Then see what happens.

Give appropriate authority

You cannot require ownership while keeping every meaningful decision with the manager. If the employee needs authority to perform the role, give it. Within sensible boundaries.

Managers need permission not to rescue

This sounds strange, but some managers believe senior leadership expects them to ensure the result at any cost. So they compensate. Make it clear:

“I expect you to protect the business, but I also expect you to manage the performance gap rather than permanently hide it.”

That changes the standard.

Senior leaders should ask better questions

When a manager says: “I had to fix this again,” do not only praise the heroics. Ask:

“Why did you have to fix it again?”

“What conversation has happened?”

“What is changing?”

Otherwise leadership rewards rescue.

Stop celebrating fire-fighting

Businesses often praise the person who saves the day. Good. Sometimes they deserve recognition. But ask why the fire keeps happening. If the same manager is constantly saving the same situation, perhaps the deeper issue is not heroism. It is failure to fix the cause.

Make management behaviour visible

In one-on-ones with managers, ask: Which employee problems are you carrying? Which tasks have you taken back? Which performance gaps are you compensating for? Which conversations are overdue? That reveals rescue patterns quickly.

Coach managers on the difference between care and responsibility

You can care deeply about an employee. Still expect them to carry their role. Care does not require taking away responsibility. Often the most respectful thing is to let the person experience the weight of their own commitment.

Do not let sympathy erase the standard

A manager may know the employee is having a difficult time. That matters. Use judgement. Provide appropriate support. But keep clarity around what the role ultimately requires. Compassion and standards can coexist.

A practical rescue-or-support test

Ask: Who owns the problem? If it belongs to the employee, keep ownership there where reasonably possible. Am I adding capability or removing responsibility? That is the core distinction. Is the employee doing the thinking? Or am I? Who owns the next action? Watch the handover.

Have I had the necessary performance conversation? If not, why not? Am I protecting the business from a one-off risk? Fine. Or am I repeatedly compensating for the same gap? That requires a different response. Is the employee becoming more capable? Look at the evidence.

Who else is carrying the cost? Manager? Colleagues? Customer? What happens if I keep doing this for six more months? That question can be very revealing.