Stop Stepping In: Five Questions That Build a Team of Problem-Solvers

Firefighting managers are rarely criticised. They are the ones who unblock the invoice, calm the client, rewrite the report at 7pm and remember the detail everyone else missed. In many UK organisations, this is what leadership looks like: visible, responsive, tireless. The trouble is that the same manager often becomes the reason the team cannot solve problems without them. Every rescue teaches the team that escalation works. Every escalation confirms the manager's belief that only they can fix it. The cycle is comfortable and costly.

At Coaching for Leaders, we work with managers who are praised for exactly the behaviour that keeps their teams dependent. The shift is not to stop caring. It is to change the default from rescue to capability-building.

Why rescue feels safer than coaching

Rescue produces a quick thank-you. Coaching produces a pause, a silence and sometimes a worse first answer. In a busy workplace, the first is easier to justify. Firefighting is visible; capability-building is not. A manager who steps back may be accused of being less supportive, especially in a culture that equates being busy with being committed. The reward system is skewed. The manager who solves is thanked today; the manager who builds problem-solvers is thanked in six months, if at all.

Five questions to move from rescue to release

1. What have you already tried, and what did you learn?

Use this when someone brings a problem they own. It respects their effort and reveals where the thinking stopped. It also prevents you from offering a solution they have already tested. Follow up with: 'What would you try first if I were not available?' The second question is often the one that builds resourcefulness. If the answer is nothing, you have found a capability gap, not a motivation problem.

2. What would a good outcome look like, and who owns it?

Managers often take ownership by accident. The team member describes a problem; the manager starts solving; the team member becomes an observer. This question resets the boundary. Try: 'If I were on leave next week, what would you want to have achieved?' It clarifies the outcome and makes ownership explicit. If the answer is vague, ask for a concrete finish line: a decision, a customer response, a handover or a revised plan.

3. What are the options, and what are the trade-offs?

This moves the conversation from a problem to a set of choices. Ask for three options, with one risk or cost attached to each. 'Give me three ways forward and the trade-off you would accept.' The manager's role is then to test judgement, not to supply the answer. If the options are weak, ask what a more experienced colleague might consider. If the options are strong, say so. That is coaching, not abdication.

4. What do you need from me: a decision, a resource, or a sounding board?

This is especially useful in busy teams where 'can I have five minutes?' can mean anything from approval to reassurance. The question forces a useful distinction. A decision needs your authority. A resource needs your influence. A sounding board needs your attention, not your answer. If the reply is 'I do not know', ask: 'What would help you decide?' Then wait. The silence is doing the work.

5. What will you do next, by when, and how will we know it has worked?

End every coaching conversation with a commitment, not a summary. This is not a trap; it is a handover. Write it down, agree the check-in and make the follow-up real. In a busy workplace, the follow-up is the difference between a useful conversation and a pleasant one. If the person cannot name a next step, the problem may need a different intervention: clearer priorities, more training or a direct performance conversation.

When to step in, and when to step back

Coaching is not a substitute for leadership judgement. Step in when the risk is material: safety, safeguarding, legal or regulatory exposure, reputational damage or an irreversible decision. Step in when the person lacks the authority, experience or information to act. Step back when the issue is recurring, the risk is low to medium, the person has the skills and failure is recoverable. A useful test: if the worst outcome is a bruised ego and some rework, coach. If the worst outcome is a breach, an injury or a lost client, intervene and explain why.

Making the shift stick in a busy workplace

Change does not need a new programme. It needs a small, repeatable habit. Use the one-to-one you already have: ten minutes, one problem, one question. Keep a rescue log for a month. Note when you stepped in, why, and whether it was genuinely urgent. Look for patterns: the same person, the same issue, the same week. Agree a triage rule with the team: for non-urgent issues, bring the problem plus two options; for urgent issues, call. Praise the process, not just the rescue. When someone brings options, say so. When you hold back, count to ten before filling the silence.

Expect discomfort. The first time you do not solve the problem, it will feel like neglect. The team may test you. Stay consistent. In a busy NHS team, a local authority service or a professional services firm, the diary is the enemy. Attach coaching to work that is already happening: handovers, project reviews and client debriefs. That is how a coaching habit survives a full inbox.

A final word

Rescue is not leadership if it is repeated. The aim is a team that can solve problems without you in the room. That is not a retreat from responsibility; it is the work of building capacity. The firefighter's dilemma is real. The answer is not to stop putting out fires. It is to spend less time holding the hose and more time teaching the team where the extinguishers are.