Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Manager Trap Of Overworking High Performers
Transcript
- Lucas: There is a specific kind of panic that sets in around week three of any new project cycle. You have deadlines looming, stakeholders are asking for updates, and suddenly you realize you only have two people on the team who can actually deliver what was promised. So, what do you do? You go to your highest performers. Luna: And you hand them everything. Because they never miss a deadline, right? Lucas: Exactly. And it feels like good management in the moment. You are protecting the timeline, you are ensuring quality, and you are rewarding competence. But if you look at the data from the last few quarters, specifically looking at engagement surveys from October through September, there is a clear correlation between this behavior and early-stage attrition among top talent. Luna: So we are essentially punishing our best workers for being reliable? Lucas: We are exploiting their reliability until it breaks. I want to talk about the 'heroic overwork' trap today. It is one of the most common failures I see in first-time managers because it masquerades as dedication. You think you are building a culture of excellence, but you are actually building a culture of dependency and exhaustion. Luna: It feels safer to rely on the people who get things done than to risk waiting for others to catch up. Lucas: That is the immediate reward loop. When you assign the critical task to Sarah or Marcus, you know it will be done by Tuesday. If you assign it to the developing employee, you might not get it until Friday, or it might need three rounds of edits. So you choose the path of least resistance. But here is the hidden cost: the high performer stops seeing growth opportunities because they are too busy executing known solutions. Luna: They become execution machines instead of strategic thinkers. Lucas: Precisely. And the developing employee never gets the chance to prove themselves on high-stakes work. They stay in the shadows, doing low-visibility maintenance tasks, while your stars are running marathons every sprint. By mid-year, the stars are exhausted and bored, and the rest of the team is disengaged because they feel like second-class citizens who aren't trusted with real problems. Luna: It creates a resentment gap that is incredibly hard to bridge later. Lucas: It does. And the worst part is that the manager feels justified. They tell themselves, 'I am just keeping the ship steady.' But in reality, they are creating a single point of failure. If your two best people get sick, or quit, or hit a personal crisis, your entire project portfolio collapses because no one else has practiced the core competencies required to run the business. Luna: So the manager isn't leading; they are just hoarding trust. Lucas: That is a brutal way to put it, but it is accurate. Trust is being withheld from the wider team. Let me give you a concrete example from a software engineering team I advised recently. They had a lead engineer who was essentially carrying forty percent of the technical load. Every bug fix, every feature launch, she touched. She was promoted twice in three years, which should be a win, right? Luna: On paper, yes. But what happened off paper? Lucas: She burned out within eighteen months. She didn't quit immediately, but her performance dipped. She started making careless errors. And because the manager had spent all that time relying on her, he hadn't developed anyone else. So when she went on medical leave for six weeks, the team couldn't function. The project missed its quarter target, and the department looked incompetent despite having the brightest person in the room. Luna: The system failed because it wasn't designed to survive without one person. Lucas: Right. And that manager now has to explain to his boss why the team is fragile. He has to scramble to hire, train, and onboard someone new, all while dealing with the fallout of the missed deadline. Meanwhile, the other engineers watched this happen and realized that their potential wasn't being nurtured. They saw that the only way to get noticed was to volunteer for impossible workloads, which reinforces the toxic cycle. Luna: It’s a self-fulfilling prophecy where only the desperate or the elite get ahead. Lucas: Exactly. And it distorts performance metrics. If you only look at output volume, the hero looks amazing. But if you look at team health, knowledge transfer, and succession readiness, the hero looks like a liability. A true leader measures their success by how many people they can replace, not by how indispensable they make themselves. Luna: So how do we break that cycle? Especially when the pressure is on. Lucas: You have to deliberately assign high-risk, high-visibility projects to developing talent. This sounds counterintuitive. Your instinct is to protect the project by giving it to the safe pair of hands. But you must resist that. You need to create psychological safety for the developing employee to fail safely. That means you, as the manager, absorb the risk, not them. Luna: You become the shield while they do the work. Lucas: Yes. And you provide frequent check-ins, not to micromanage the output, but to remove obstacles. If they hit a wall, you help them navigate it. You celebrate the learning, even if the final product isn't perfect. This builds confidence in the wider team and frees up your high performers to focus on innovation rather than just putting out fires. Luna: It requires a lot more patience upfront, doesn't it? Lucas: It does. You have to trade short-term efficiency for long-term resilience. And honestly, it’s uncomfortable. You will feel like you are slowing down. You will worry about the quality. But remember, if you don't invest in the depth of your bench, you are gambling with your career stability. A manager who cannot develop talent is ultimately replacing themselves with a consultant or a temp agency. Luna: Which is expensive and rarely works as well as internal growth. Lucas: Always. Now, before we dig deeper into the mechanics of equitable delegation, I want to mention something quick. If these conversations have helped you navigate a tricky management situation or just given you a fresh perspective on your team, consider supporting the show directly. A couple of dollars a month is genuinely what keeps these independent productions going without ads cluttering the feed. You can find us at buy me a coffee dot com slash fexingo. It makes a real difference in how often we can bring you these deep dives. Luna: Yeah, and it lets us keep digging into the specifics without worrying about sponsor requirements dictating the topics. Lucas: Appreciate it. Anyway, let's get back to the practical side. How do you identify who is currently trapped in the heroic cycle? It’s usually visible in the calendar and the communication channels. Luna: Who is always available after hours? Who is the go-to for every emergency? Lucas: Spot on. Look at who is responding to Slack messages at nine PM. Look at who is attending meetings that aren't strictly necessary for their role. These are signs of overextension. The high performer is trying to be helpful, but they are also signaling that they are the bottleneck. You need to intervene gently. Tell them, 'I value your expertise, but I need you to step back from this specific workflow so you can focus on strategic planning.' Luna: Frame it as a promotion of responsibility, not a demotion of workload. Lucas: Exactly. Reframe it as 'strategic bandwidth.' You are pulling them out of the weeds so they can grow. Simultaneously, you must start pairing them with junior members. Not just to teach, but to share the load. Make it a requirement that no major deliverable goes out without a peer review from someone who hasn't seen it before. This forces knowledge transfer and prevents silos. Luna: It turns individual brilliance into collective capability. Lucas: That is the shift. From heroics to hygiene. Hygiene sounds boring, but it is sustainable. When you distribute the load, you also distribute the stress. Everyone feels ownership. Everyone feels capable. And when someone calls in sick, the machine keeps turning because ten people can drive it, not just one. Luna: It changes the dynamic from 'us versus the problem' to 'we are solving this together'. Lucas: Yes. And it protects your high performers from resentment. They stop feeling like the designated scapegoats for poor planning. They start enjoying their work again because they have time to think, not just react. That is where innovation happens. You can't innovate when you are drowning in operational noise. Luna: So the metric for a healthy team isn't just speed, but redundancy. Lucas: Redundancy is strength. In aviation, redundancy saves lives. In management, it saves careers. If you are a manager reading this, ask yourself: if my best player walked out tomorrow, would my team collapse? If the answer is yes, you have a structural problem, not a personnel problem. Fix the structure, and you retain the talent. Luna: It’s scary to let go of control, but necessary for scale. Lucas: It is. And the irony is that by letting go, you gain more control over the long term. You create a predictable, scalable engine rather than a chaotic rollercoaster. Next time you feel that panic rising as a deadline approaches, pause. Don't default to the hero. Ask who else needs this challenge. Challenge yourself to trust the process, and trust your team to rise to it. Luna: Because the greatest gift a manager can give is the opportunity to grow, not just the comfort of being saved. Lucas: Well said. Think about your current project list. Who is doing the heavy lifting? Is it the same names every time? If so, it might be time to shake up the deck. What’s one task you could hand off today that you’ve been holding onto?