Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Hidden Cost of Good Intentions in Team Management
Transcript
- Lucas: You know, I was talking to a director at a logistics firm last week, and she described a moment that haunts her. She had a junior analyst who was struggling with a quarterly report. It wasn't just slow; it was structurally flawed. So what did the director do? She took the laptop, sat down next to him, and finished the spreadsheet herself. It saved two days of work. The report went out on time. But six months later, that analyst still couldn't build a pivot table without asking for help. Luna: That sounds like the classic savior complex. You think you're helping, but you're actually disabling them. Lucas: Exactly. And here is the twist: the director thought she was being supportive. She saw stress in the room and tried to remove it. But by removing the struggle, she also removed the learning. Today, we are talking about the specific trap of over-helping, and why letting your team make small mistakes is often better than fixing them instantly. Luna: It's so easy to confuse kindness with competence. Just because someone looks stressed doesn't mean they need you to take over. Lucas: Right. Let's break down the mechanics of this. When a manager steps in to fix a problem immediately, three things happen. First, the employee learns that their effort doesn't matter because the boss will clean it up. Second, the manager's own capacity gets clogged with low-leverage work. And third, you create a single point of failure where everyone relies on you. Luna: So it's not just bad for the employee's growth, it's actually dangerous for the business continuity. Lucas: Precisely. If you are the only person who knows how the reporting system works because you've been fixing everyone else's errors for three years, you have built a fragile system. And if you get hit by a bus, or even just take a vacation, the whole department collapses. Luna: I see this with consultants all the time. The junior associate is stuck, and the senior partner jumps in to rewrite the slide deck. Then the associate never learns how to structure the argument. Lucas: And the partner ends up doing eighty percent of the actual delivery work while the associate watches. It's a terrible trade-off for career progression. The question becomes, how do you stop doing this? Because for most new managers, the instinct to fix is visceral. You see a problem, you want to solve it. It feels good to be the hero. Luna: But heroics are usually a sign that the system is broken, or that you haven't delegated properly. Lucas: Here is a concrete framework I use called the 'Three-Question Pause.' Before you offer to help, you ask the employee three questions. Number one: What have you tried so far? Number two: Where do you feel stuck? And number three: What kind of support would actually help you move forward? Luna: That forces them to articulate the problem instead of just waiting for you to absorb it. Lucas: It does. And often, by the time they answer those three questions, they realize they already know the solution. Or they realize they need something very specific, like an introduction to another colleague, rather than you taking over the task. It shifts the dynamic from 'boss fixes worker' to 'coach guides player.' Luna: What if the stakes are higher though? Like if missing the deadline costs the company real money? Lucas: That is the critical distinction. For high-stakes, zero-tolerance errors, you absolutely intervene. But for routine operational friction, you let them wrestle with it. Most daily work falls into that second category. We tend to treat every small hiccup like a crisis, which trains our teams to be anxious and dependent. Luna: So you're saying we should normalize small failures as part of the learning curve. Lucas: Yes. And this requires a shift in how you view efficiency. Short-term efficiency looks like you doing the work fast. Long-term efficiency looks like your team doing the work well, even if it takes them longer initially. It's the difference between paying rent and building equity. Luna: I love that analogy. Paying rent is just covering the immediate cost. Building equity is investing in future capacity. Lucas: Exactly. Now, there is a nuance here that trips people up. This isn't about neglect. You still need to provide resources, clear expectations, and regular feedback. You just shouldn't provide the unless it's a true emergency. Let them draft the email. Let them build the prototype. Let them present the data. Luna: It feels counterintuitive because we're trained to reward speed. But speed without durability is just wasted motion. Lucas: Right. And consider the psychological impact on the employee. When you fix their work silently, you send a subtle message that you don't trust their capability. Even if you say nothing, they notice. Over time, that erodes their confidence. They start thinking, 'My boss is really good at this. I'm probably not going to get it right anyway.' Luna: That imposter syndrome is self-fulfilling. If you don't give them the chance to succeed on their own terms, they can't prove they can do it. Lucas: Let's talk about the feedback loop. When an employee makes a mistake that you didn't fix, what happens? Ideally, they learn. But they also come to you with the problem and the proposed solution. That is a much higher quality interaction than coming to you with just the problem. Luna: So you end up spending less time managing problems and more time coaching solutions. Lucas: That is the goal. You become a strategic advisor rather than an operational firefighter. And honestly, it frees up your mental energy. You can focus on the things that only a manager can do, like aligning cross-team priorities or advocating for budget, instead of debugging code or formatting slides. Luna: It’s really about scaling yourself. You can only manage so many tasks directly before you hit a ceiling. Lucas: Absolutely. Your leverage comes from enabling others, not from doing more yourself. There is a concept in organizational behavior called 'productive struggle.' It suggests that cognitive growth happens when we encounter obstacles that are just outside our current comfort zone. If you remove the obstacle, you remove the growth opportunity. Luna: So by stepping in too early, you're keeping them in their comfort zone permanently. Lucas: Yes. And they stay mediocre because they never stretch. Meanwhile, you are exhausted because you are carrying the weight of their potential. It's a lose-lose scenario. Luna: It’s funny how much we protect our employees from discomfort, thinking we’re being nice. But we’re actually robbing them of resilience. Lucas: Resilience is built through repeated exposure to manageable failure. If your team never fails, they never learn how to recover. And in today's market, recovery speed is a competitive advantage. Luna: So the metric shouldn't be 'how few errors did we make?' It should be 'how quickly did we learn from them?' Lucas: Spot on. Now, I want to mention one practical tactic. When you feel the urge to jump in, try writing down the advice you were going to give, but don't send it. Wait twenty-four hours. Usually, by the next morning, you'll realize that the employee has already figured it out, or that the problem wasn't as big as you thought. Luna: The twenty-four hour rule is a great brake on reactive management. Lucas: It gives you time to shift from emotional reaction to strategic response. And it signals to your team that you respect their process enough to wait. Luna: It builds trust faster than any team-building exercise ever could. Lucas: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, if you found value in this conversation, consider buying me a coffee dot com slash fexingo to keep the show running. Lucas: We appreciate it. Now, back to the topic. One final thing to watch out for is the 'echo chamber' effect. If you only delegate to your strongest performers, you might accelerate their growth, but you leave your struggling employees further behind. Luna: So you have to be intentional about giving stretch assignments to the people who need them most, not just the ones who are already winning. Lucas: Exactly. The biggest gap in most teams isn't between the stars and the rest. It's between the stars and the silent majority who are waiting for permission to lead. Give them the space to make mistakes, and you might be surprised by who rises. Luna: It’s a challenge, but it’s the only way to build a truly independent team. Lucas: It is. And ultimately, your success as a manager is measured by how well your team functions when you aren't in the room. If they can solve problems, learn from errors, and support each other, you have done your job. Luna: Stop fixing, start guiding. It’s harder in the moment, but infinitely better in the long run. Lucas: Agreed. Thanks for listening. Let us know which of your past mistakes taught you the most.