Support and rescue can look remarkably similar
Both may involve helping somebody. Both may come from good intentions. Both may solve today's problem. But the long-term effect is very different. Support says:
“Let's think this through.”
“What do you think is really going on?”
“What have you tried?”
“What are your options?”
“What do you recommend?”
“What are you going to do?”
Rescue says:
“Just give it to me. I'll sort it out.”
Support keeps the thinking and responsibility largely with them. Rescue transfers it to you. That distinction matters enormously.
Watch the problem ball
I use the idea of a problem ball. Someone brings you a problem. They throw the ball. If you catch it, you now own it. Perhaps you solve it brilliantly. But the other person has also learned something: When the problem gets difficult enough, give it to the boss.
Do that often enough and you build a very efficient system for getting every difficult problem to you. Then leaders wonder why nobody beneath them seems independent. Perhaps because nobody beneath them is being allowed to carry enough weight.
The fastest solution today can create tomorrow's dependency
This is the trap for capable leaders. You really can do it faster. You have more experience. You know the customer. You know the history. You can see the answer. So taking over feels efficient. Today it probably is. But speed is not the only measure of good management.
Sometimes the slower conversation develops a manager who can solve the next ten similar problems without you. That is a much better return. Easy choices, hard life. Hard choices, easy life. The easy choice is:
“I'll do it.”
Problem disappears. Your manager feels relieved. You feel useful. The harder choice is to stop and ask questions. Let them think. Let them wrestle with uncertainty. Let them make a sensible decision. Perhaps even let them make a sensible mistake. That may feel slower today.
But if their judgement improves, your life becomes easier tomorrow. Easy choices, hard life. Hard choices, easy life.
Ask whether the issue really belongs with you
Before stepping in, ask: Whose problem should this actually be? Does it belong within the manager's role? Do they have the authority to handle it? Is this something they reasonably should be able to learn? If yes, think very carefully before taking it away. You may need to coach. You may need to add experience. But that does not mean you need to own the next action.
There are times when you absolutely should step in
Leadership development does not mean leadership abandonment. There are circumstances where stepping in is entirely appropriate.
Serious safety risk
If delay or poor judgement could put someone in danger, intervene. Development can wait.
Legal risk
If the issue creates significant legal exposure or requires authority the manager does not have, step in appropriately.
Ethical risk
If something raises a serious ethical concern, senior involvement may be required.
Something genuinely outside their authority
You cannot expect somebody to make a decision they are not authorised to make.
A genuine crisis
If delay could cause serious harm to the business, customer or people, intervention may be necessary.
A very new manager facing something genuinely unfamiliar
Sometimes people simply do not yet have enough experience. Sit alongside them. Show them how to think about it. That is different from permanently doing it for them.
Risk should determine how much you intervene
Not all decisions carry the same consequence. A sensible mistake in an internal meeting agenda is one thing. A mistake involving employee safety is another. So ask: What happens if they get this wrong? Low consequence? Perhaps let them handle more. Moderate consequence? Coach and set guardrails.
High consequence? Stay closer. Very high consequence? You may need to take or share the decision. Good leadership is not blindly letting go. It is matching your involvement to the risk.
Capability matters too
The same issue may need different leadership responses depending on who is handling it. An experienced manager who has handled five similar situations may need:
“What do you recommend?”
A new manager may need:
“Let's work through this together.”
The objective is still development. But the support should reflect where the person actually is.
Authority matters
Before criticising somebody for escalating, ask whether they genuinely had the authority to act. Businesses often tell managers:
“Own it.”
Then punish them when they make decisions. Or require approval for every meaningful action. If the issue belongs with them, make sure the authority belongs with them too. Otherwise escalation may be entirely rational.
Ask for their thinking before you give yours
This is one of the simplest disciplines. Before answering, ask:
“What do you think?”
Then:
“What have you already done?”
“What evidence do you have?”
“What are your options?”
“What are the risks?”
“What do you recommend?”
You may discover they already have a perfectly sensible answer. And if they do not, now you can see where their thinking needs development.
Add experience without stealing ownership
You may know something they do not. Share it. Perhaps:
“You may want to consider the contractual risk here.”
Or:
“There is some history with this customer you need to know.”
Or:
“One thing I would test before deciding is X.”
That is useful support. You are adding experience to their thinking. You are not necessarily taking the decision away.
Challenge assumptions
Sometimes the manager's recommendation is weak. Fine. Ask:
“What makes you think that?”
“What might you be missing?”
“What happens if that assumption is wrong?”
“What other option could you consider?”
Again, you are developing judgement. The goal is not merely to make sure they arrive at your answer. It is to improve how they reach an answer.
Sometimes a sensible mistake is worth allowing
This makes many leaders uncomfortable. If the consequences are manageable and the person's reasoning is sensible, there may be value in letting them make the call. Even if you would have chosen differently. They may be right. They may be wrong. Either way, they gain experience.
If every imperfect outcome results in: “You should have asked me first,” what will they learn? Ask first. Forever.
Do not allow reckless mistakes in the name of development
There is a difference between: a sensible judgement that turns out badly and: an obviously reckless decision. Development does not require pretending those are the same. You can give autonomy within guardrails. Good judgement includes understanding consequences.
Watch whether helping has become compensating
This is a particularly important question: At what point am I no longer supporting this person and instead doing important parts of their job for them? If you repeatedly compensate for their gap, you may never discover whether they can genuinely grow into the role. You keep the department functioning. But the manager themselves may not be developing.
Do not become the substitute manager
If one of your managers has a problem in their team, develop the manager. Do not automatically manage the team for them. Otherwise the organisational chart says you have four direct reports, but in reality you have quietly acquired everybody underneath those four as well. No wonder senior leaders become overwhelmed.
Beware becoming the court of appeal
Another version of stepping in is when somebody dislikes their manager's answer and comes to you. Perhaps an employee. Perhaps a customer. If you casually overturn the manager's decision, everyone learns something. The employee learns:
“If I don't like my manager's answer, I can appeal.”
The customer learns:
“If I make enough noise, I can go higher.”
The manager learns:
“My authority isn't really real.”
And you become the decision-maker for another level of the business.
Sometimes the manager's decision should be overturned
Of course. Managers are not infallible. If the decision is genuinely wrong or new information changes things, intervene. But involve the manager. Explain what changed your view. Help them understand what they missed. Then ask:
“How would you think about this next time?”
Do not casually swipe them aside and take control.
Discomfort is not always a reason to intervene
Managers need to experience some uncomfortable things. Having the difficult conversation. Dealing with the unhappy customer. Explaining a missed commitment. Making a judgement call. Recovering from a mistake. Sitting with uncertainty. Those experiences develop them.
If you rescue someone the moment they become uncomfortable, you may remove the exact experience from which their development would have come.
Ask whether you are stepping in for them or for yourself
This can be uncomfortable. Sometimes leaders rescue because they care. Sometimes because the customer genuinely needs protecting. And sometimes because the leader cannot tolerate watching someone else struggle. Or because being the person with the answer feels good.
Being the white knight is satisfying. Everybody needs you. Everybody is grateful. You feel valuable. But being needed is not the same as leading well.
Indispensability is not always evidence of success
If every problem still requires you, that may not prove how brilliant you are. It may prove that insufficient capability has been built around you. Strong leaders are not measured only by how many problems they personally solve.
They are also measured by how many people around them can now solve problems that once needed the leader. That is what I call building shoulders.
Build shoulders underneath you
If you are the head, you need shoulders beneath you. Managers who can: think; decide; carry responsibility; have difficult conversations; solve problems; learn from mistakes; follow through. You cannot build those shoulders while repeatedly taking the weight back from them.
Pay attention to the end of the conversation
This is critical. You can have a brilliant coaching conversation. Ask wonderful questions. Help them think. Then right at the end say:
“Leave it with me.”
And there it is. The rescue. So ask: Who leaves carrying the problem ball? Who owns the next action? Ideally, if the problem belongs in their role, they do.
A practical support-without-rescue conversation
When a manager brings you an issue, try: 1. What is actually happening? Get the facts. 2. What have you already done? See whether they have acted. 3. What do you think is causing it? Ask for judgement. 4. What options do you see? Make them think beyond the first answer. 5. What are the risks?
Develop commercial and managerial awareness. 6. What do you recommend? Make them own a position. 7. What do you need from me? Support only where genuinely needed. 8. What are you going to do? Keep the action with them. 9. By when? Create a real commitment. 10. When will we review it?
Stay appropriately connected without taking over.
If you do step in, do not waste the learning opportunity
Sometimes you had to intervene. Fine. Come back afterwards. Ask:
“What did you notice?”
“What did you learn?”
“What would you do next time?”
“What part of this can you own from now on?”
“What authority or knowledge was missing?”
The goal is to reduce the chance that the same situation automatically comes back to you again.
Review why escalation was necessary
After stepping in, ask: Was the manager missing capability? Authority? Information? Confidence? Experience? Was the system unclear? Did I previously train them to escalate? Each answer suggests a different development action. Do not just survive the incident. Improve the conditions for next time.
The manager should need you at a higher level over time
This is one of the clearest signs of growth. Six months ago they needed help with ordinary customer complaints. Now they handle them. They used to need you for staffing conversations. Now they conduct them. They once brought every operational problem. Now they bring only high-risk or unusual ones. They still use you. But at a higher level. That is exactly what should happen.
Ask what your intervention teaches
Every response is training. When someone brings you a problem and you solve it, you are teaching something. When you ask for their recommendation, you are teaching something. When you overturn their decision without discussion, you are teaching something. When you let a sensible decision stand, you are teaching something. So ask:
“What did my response teach them to do next time?”
That is a powerful leadership question.
A simple step-in test
Before intervening, ask: Is there serious safety, legal or ethical risk? If yes, intervene appropriately. Is this genuinely outside their authority? If yes, senior involvement is reasonable. Could delay cause serious harm? If yes, act with the urgency required.
Is the manager too inexperienced for this particular situation? Support more closely. Is the potential mistake recoverable? If yes, consider letting them carry more. Have they thought properly about it? Ask for evidence, options and recommendation. Am I stepping in simply because I can do it faster?
Be careful. Am I removing a useful learning experience? If yes, reconsider. Who should own the next action? Keep that clear. That is the boundary.
Leadership development is not leadership abandonment
You do not develop people by throwing them into situations they cannot reasonably handle and saying:
“Good luck.”
Nor do you develop them by shielding them from every difficult situation. Good leadership sits between those two extremes. Enough support. Enough authority. Enough challenge. Enough room to think. Enough room to learn. And intervention when the risk genuinely requires it.
The question is not “Can I solve this?” Of course you can. That is often why you are the senior leader. The better question is:
“Should I solve this?”
Or even better:
“How can I help this person become capable of solving this themselves?”
Sometimes the answer is that you need to step in. When you do, step in. But do it consciously. And whenever the risk allows, stand beside the manager rather than in front of them. Because every unnecessary rescue teaches dependency. Every well-coached problem develops judgement.
Every appropriately held boundary strengthens ownership. And every manager who learns to think, decide and follow through becomes another strong set of shoulders beneath you.
