I train managers across Philippine companies for a living. I’m Jordan Imutan, and I run LeadDaily, a management-execution practice that helps managers apply what they already know on the actual Monday-morning problem in front of them, instead of sitting through one more workshop they’ll forget by Friday. One habit shows up in almost every team I sit in on: the manager who jumps in and solves the problem for the employee, instead of helping the employee solve it themselves.
It looks like good leadership. The manager is fast, decisive, available. The problem gets fixed in minutes instead of hours. Everyone moves on.
But watch the same team a month later, and the same problem comes back — to the same manager’s desk. Nothing was actually learned the first time, because nothing was actually handed over.
The rescue feels like help. It functions like a tax.
Every time a manager solves a problem instead of coaching someone through it, they are not saving time. They are borrowing it from their future self, with interest. The employee learns one lesson very clearly: when something gets hard, hand it up. The manager becomes the single point of failure for every decision that matters, and the team’s actual capability never grows past whatever the manager personally has bandwidth to carry.
Forrester’s 2025 workplace research found that 54% of employees now describe their manager as a coach, up from 50% the year before — and the employees who experience real coaching are roughly 8 times more likely to be highly engaged, and 1.7 times more likely to stay with the company. The gap between a manager who fixes and a manager who coaches is not a soft, feel-good distinction. It shows up directly in retention and output.
Why managers rescue, even when they know better
It is rarely laziness or ego. It is almost always one of three things: the deadline is real and coaching takes longer than fixing today; the manager was never shown what coaching actually sounds like, so “helping” defaults to “doing”; or the manager has been burned before by delegating and watching the result come back wrong, so they stopped trying.
All three are solvable. None of them require a personality change. They require a different first move.
The first move: ask before you answer
The shift is smaller than it sounds. When someone brings you a problem, the rescuing response is to ask “what’s wrong?” and then start solving. The coaching response is to ask “what have you already tried?” and then “what do you think the next step is?” before you say anything close to an answer.
This does three things at once. It surfaces how much the person already understands, which is usually more than the manager assumes. It gives the manager a chance to correct direction without taking over the wheel. And it puts the decision — and the ownership of the outcome — back where it belongs.
A supervisor I worked with in a logistics company used to personally re-route every delayed shipment herself, every time, because “it was faster if I just did it.” The team’s planners never built the judgment to re-route on their own, because they never had to. Six months after she switched to asking two questions before touching the problem — what’s the constraint, and what’s your call — her planners were resolving 70% of delays without escalating to her at all. She didn’t become a softer manager. She became a less necessary one, in the best possible sense, and that is what freed her to actually run the operation instead of patching it.
What this is not
Coaching is not standing back while someone fails badly on something that matters. It is not refusing to answer a direct, reasonable question just to prove a point. If the building is on fire, you put it out. The distinction is between problems where the cost of the person figuring it out is worth paying — which is most problems, most of the time — and the rare one where it genuinely is not.
Most managers already know this distinction intellectually. The habit of rescuing survives anyway, because nobody ever sat them down and asked: on the last ten problems your team brought you, how many did you actually need to solve yourself?
The question worth asking this week
Pick one recurring problem that keeps landing on your desk from the same person or the same team. Before you touch it next time, ask yourself: if I don’t solve this today, who on my team is closest to being able to solve it — and what is the one question I could ask them instead of the one answer I’m about to give?
If you want to think through that specific situation, send me a message — I’m glad to help you work out what the right next question actually is. No pitch, just a conversation.
Next reads from the LeadDaily blog:
• Your Managers Keep Avoiding Difficult Conversations — And It’s Quietly Killing Performance — https://jordanimutan.com/2026/05/05/your-managers-keep-avoiding-difficult-conversations-and-its-quietly-killing-performance/
• Breaking Barriers: How Filipino Middle Managers Can Overcome Cultural Conflict and Avoidance — https://jordanimutan.com/2024/12/28/breaking-barriers-how-filipino-middle-managers-can-overcome-cultural-conflict-and-avoidance/
• Fix the System, Not the People: Why Micromanagement Fails and What to Do Instead — https://jordanimutan.com/2025/06/21/fix-the-system-not-the-people-why-micromanagement-fails-and-what-to-do-instead/
• You Think People Aren’t Taking Ownership. They Think It’s Not Safe To. — https://jordanimutan.com/2026/03/21/you-think-people-arent-taking-ownership-they-think-its-not-safe-to/
• Stop Micromanaging. Start Leading. How Systems Create Trust and Ownership — https://jordanimutan.com/2025/06/26/stop-micromanaging-start-leading-how-systems-create-trust-and-ownership/
#Leadership #ManagementTraining #Coaching #PhilippineSMEs #PeopleDevelopment
