Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why High Performers Burnout From Being The Fixer
Transcript
- Lucas: There is a specific kind of exhaustion that hits high performers when they realize they are the only ones who can actually fix things. It starts as pride—being the go-to person for the hardest problems—and ends as a cage where you cannot delegate because no one else will do it right. Luna: Right, and it’s ironic because the very skill that got them promoted, their individual contribution, becomes the thing that blocks their next move. Lucas: Exactly. We call it the hero trap. You become so essential to the daily operations that stepping away feels like negligence. But in reality, staying in the weeds is killing your potential for higher-level leadership roles. Luna: I saw this with a friend at a fintech startup. She was the best coder on the team, but she couldn't get promoted to engineering lead because the VP said she was too busy writing code to manage people. Lucas: That is the classic structural conflict. If you are still coding while managing, you are not building systems; you are just applying more effort to the same broken process. The company gets short-term relief but long-term fragility. Luna: So how do you break that cycle without making the team feel like you are abandoning them or dropping quality? Lucas: You have to reframe what success looks like. For an individual contributor, success is output. For a manager, success is leverage. You need to measure how many problems your team solves without you, not how many you solve yourself. Luna: That requires a huge mindset shift. Most managers equate visibility with value. If I’m not putting out fires, am I actually doing anything? Lucas: Visibility is not value. Silence is often better. If your team runs smoothly and you are not visible, that means you built a system that works. If you are constantly visible saving the day, the system is failing. Luna: But then there is the fear that if you let someone else handle it, they might mess up. And that mess-up reflects on you as the manager. Lucas: That is the cost of entry for leadership. You have to accept that mistakes will happen under your watch. The question is whether those mistakes teach the team or just waste time. Luna: So you allow small failures as tuition fees for their growth? Lucas: Precisely. But you have to design the failure so it doesn’t blow up the business. You pick low-stakes tasks first. Let a junior associate handle a client email. If they make a typo, it’s fine. If they write nonsense, you correct it privately and move on. Luna: It feels counterintuitive to slow down to speed up, but I see how it builds capacity over time. Lucas: Think about it like investing. Your time is capital. If you spend all your capital on immediate returns—fixing today’s bug—you have nothing left for long-term growth, like training the next lead. Luna: And yet, when the quarterly review is looming, everyone wants the immediate return. Pressure makes us revert to old habits. Lucas: True. That is why you need explicit rules. I worked with a project manager who instituted a two-person rule. No task leaves her desk unless a second person has touched it. It forced delegation immediately. Luna: That sounds strict. Did the team resist having to double-check each other's work? Lucas: Initially, yes. They thought it was micromanagement. But once they realized it freed them from her constant interruptions, they embraced it. It shifted the dynamic from waiting for approval to peer collaboration. Luna: So the barrier isn’t capability; it’s the expectation that the manager is the bottleneck. Lucas: Spot on. We train our teams to look up. We need to train ourselves to look sideways. To trust that the lateral handoff is stronger than the vertical rescue. Luna: It also changes how we hire. We tend to hire people who can do the job now, not people who can grow into it later. Lucas: That is a common mistake. You hire for proficiency, not potential. But if you want to escape the hero trap, you need to hire for curiosity and coachability, even if their current skills are slightly behind. Luna: Because a curious person can learn the tool, but a proficient person might just repeat the same mistake forever. Lucas: Exactly. Proficiency is static. Curiosity is scalable. You can scale curiosity across a team. You cannot scale a single genius. Luna: This ties back to psychological safety. If people are afraid to try new things, they will just defer to the expert—the hero. Lucas: Yes. Safety is the prerequisite for delegation. If my team thinks I will judge them harshly for a minor error, they will never take ownership. They will wait for me to do it perfectly. Luna: So the manager’s job is to absorb the shock of those early errors so the team can learn. Lucas: Correct. You take the hit publicly if needed, but you debrief privately. You separate the person from the process. The error is data, not character flaw. Luna: That takes a lot of emotional discipline. It’s easier to just snap and do it yourself. Lucas: It is. And that is why high performers struggle. They are used to controlling outcomes. Leadership requires accepting uncertainty. Luna: It’s the difference between playing chess and playing whack a mole. Lucas: Love that analogy. whack a mole is reactive. Chess is strategic. You stop chasing every mouse and start thinking three moves ahead. Luna: So how do you know when you’ve actually succeeded? When is the team ready to operate without you? Lucas: When you can take a week off and the metrics don’t dip. Or better yet, when they improve because the team finally owns the process. Luna: That is the ultimate test. Freedom through structure. Lucas: Exactly. You build the machine, then you step out of the driver’s seat. Now, before we dive deeper into the mechanics of building that machine, I want to mention something important. Luna: Yeah, we talk a lot about supporting our teams, so supporting the show itself is pretty key to keeping these conversations going. Lucas: We deliberately run zero ads on these episodes. If you want to support that choice directly, the link is buy me a coffee dot com slash fexingo. Luna: It really helps keep the production independent and allows us to dig into topics like this without corporate influence. Lucas: Thanks for considering it. Let’s get back to the framework. Once you decide to delegate, you need a clear handoff protocol. Luna: What does a good handoff look like? Is it just sending an email with instructions? Lucas: No. Email is for confirmation. Handoff is for context. You need to explain the why, not just the what. What is the goal? What are the constraints? What does success look like? Luna: So you’re transferring decision-making authority, not just tasks. Lucas: Precisely. If you give them the task but keep the decision-making, you are still micromanaging. Give them the outcome, let them figure out the path. Luna: That’s scary for some managers. What if they choose a different path than you would have? Lucas: Then you let them walk it. As long as it leads to the same destination, the path doesn’t matter. Their path might even be faster next time. Luna: It builds their confidence and gives you a new perspective on efficiency. Lucas: Always. Innovation comes from diverse approaches, not just copying the leader’s style. Luna: So documentation becomes critical. You need a knowledge base so the team isn’t reliant on your memory. Lucas: Yes. If it’s not written down, it doesn’t exist. Build a wiki, a playbook, whatever works. Make institutional memory accessible. Luna: That shifts the culture from hero-worship to system-reliance. Lucas: And that is how you scale. You stop relying on superhumans and start relying on smart processes. Luna: It’s hard to let go, but necessary for growth. Lucas: Absolutely. The goal is to make yourself obsolete in the daily grind so you can focus on the future. Luna: Do you think companies reward this enough? Or do they still praise the hero? Lucas: Mostly they praise the hero. Until the hero burns out and quits. Then they scramble to find someone else who can do the same thing. Luna: A vicious cycle. Breaking it requires intentional leadership. Lucas: It does. Start small. Delegate one thing this week. Watch what happens. You might be surprised by what your team can handle. Luna: Lessons learned: trust your team, document everything, and measure leverage, not hours. Lucas: Good summary. The real work begins when you stop trying to be the answer and start trying to be the guide.