Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / The Manager's Dilemma of Overworking Star Performers
Transcript
- Lucas: There is a specific kind of exhaustion that does not come from working harder, but from being trusted too much. We talk a lot about the difficult boss who micromanages or takes credit, but today we are looking at the reverse: the manager who accidentally destroys their best employee by never letting them go. Luna: Right, the competence curse. You solve one problem, so you get assigned every other problem until there is nothing left of your actual job. Lucas: Exactly. Let’s look at Sarah, a fictional but painfully real mid-level marketing director I spoke with recently. Her company hired her to stabilize a chaotic campaign team. She fixed the workflow, implemented new tracking software, and delivered a quarter where revenue jumped by twelve percent year-over-year. Luna: And what did her boss do? Promote her? Lucas: He gave her a nice bonus, sure. But then he started routing all the unstructured, high-stress client crises directly to her inbox. He told her, 'You’re the only one who gets this.' Within six months, Sarah was working eighty-hour weeks, missing her own strategic planning sessions, and quietly updating her resume. Luna: So the manager used her competence as a shortcut instead of fixing the system she built. Lucas: Precisely. And the manager thought he was being supportive. He saw her success and thought, 'She’s good at putting out fires, let her put out all the fires.' But in doing so, he stripped her of the time needed to actually lead. This is not malice. It is managerial laziness disguised as trust. Luna: It’s the difference between delegating a task and dumping a burden. One builds capacity, the other depletes it. Lucas: That distinction is critical. When a manager delegates a task, they are trying to develop a skill in their report. When they dump a burden, they are trying to relieve their own anxiety. The signal is usually in the feedback loop. If the manager never asks how you managed the crisis, but only asks if it is solved, they are treating you as a tool, not a teammate. Luna: How do you spot the early signs before you hit that eighty-hour wall? Lucas: Look at the ratio of your core responsibilities versus ad-hoc requests. If more than thirty percent of your week is spent on unplanned, high-pressure issues that were not originally yours, you are in the danger zone. Another sign is if your manager starts asking for your opinion on things that should be handled by lower-level staff because they know you can fix it quickly. Luna: So you become the default solution for everything, which means you stop doing the deep work that actually moves the needle. Lucas: Yes. And that is the hidden cost. Your career stagnates because you are busy keeping the ship afloat, not navigating it. Meanwhile, your colleagues are learning less because they are waiting for you to handle the hard parts. It creates a dependency cycle that harms the whole team. Luna: It’s ironic. The person who helps the company the most is often the one who suffers the most professional damage in the long run. Lucas: It is tragic, but it is also solvable. For the employee, the first step is to start documenting the handoff. When you take on an extra crisis, you explicitly note: 'I am handling this, but here is the process so someone else can do it next time.' You force the visibility of your labor into a reusable format. Luna: So you are turning your heroics into institutional knowledge. That protects you if you leave, and it pressures the manager to train someone else. Lucas: Exactly. And for the manager reading this, or listening to learn how to avoid this pitfall, you have to actively protect your high performers from their own competence. You need to say no to the ad-hoc requests that come to them. You need to be the buffer, not the funnel. Luna: But that feels risky for the manager. If they say no to the crisis, who fixes it? Lucas: If nobody fixes it immediately, that is a feature, not a bug. It forces the organization to see the gap in resources or training. If you always shield your star performer by taking the load yourself or redirecting it to another star, you hide the problem. The pain needs to be visible so leadership allocates budget for hiring or process improvement. Luna: So letting a small fire burn might save the house from collapsing later. Lucas: Metaphorically, yes. Practically, it means you prioritize systemic fixes over individual heroics. It shifts the metric of success from 'who saved the day' to 'how many days did we not need saving?' That is a much healthier way to run a team. Luna: What about the emotional toll on the employee? They feel guilty saying no because they want to help. Lucas: That guilt is manufactured by a culture that confuses availability with value. You have to reframe it. Saying no to a low-leverage task is saying yes to your strategic objectives. It is not selfish; it is stewardship of your primary role. If you neglect your main goals to fix side projects, you are failing your actual job description. Luna: It requires a conversation with the manager that can feel confrontational. How do you frame that without sounding like you are checking out? Lucas: You frame it around capacity and impact. You do not say, 'I don’t want to do this.' You say, 'To ensure I deliver on Q4 targets, I need to deprioritize these recurring ad-hoc requests. Can we agree on a triage protocol for these issues going forward?' Luna: So you put the ball back in their court to decide what matters less. That is a smart move. Lucas: It is. And if the manager pushes back and insists you keep doing everything, then you have your answer about their priorities. You are not the problem; the system is. Recognizing that clarity is valuable in itself, even if it makes leaving easier. Luna: This is such a subtle dynamic. Most people think they are being rewarded when they are actually being set up for burnout. Lucas: They are. And it is exhausting to watch. We see it in tech, finance, healthcare. The person who knows where all the bodies are buried ends up carrying the shovel everywhere they go. Luna: It reminds me of that concept of 'emotional labor' but applied to operational chaos. It is not just feeling stressed; it is managing the uncertainty for everyone else. Lucas: Spot on. It is cognitive overhead. Every time you take on a crisis, you have to hold the context, the relationships, and the solution in your head. That drains the mental energy you need for creative or strategic thinking. You become reactive instead of proactive. Luna: So the antidote is really about forcing structure onto chaos. Even if the chaos doesn't disappear, you manage the intake. Lucas: Yes. You create filters. You establish protocols. You make the invisible work visible. And if the manager refuses to engage with those structures, then you know the relationship is fundamentally misaligned. Luna: It is a tough pill to swallow because we want to believe that hard work is always noticed and rewarded fairly. Sometimes it is just noticed and exploited. Lucas: It is. But recognizing the pattern gives you agency. You can choose to change the dynamic, or you can choose to exit. Both are better than staying stuck in the loop of endless firefighting. Luna: If you've found this perspective useful for navigating your own workplace dynamics, remember that listener support keeps this show independent and ad-free. Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Lucas: Thanks for that. Back to Sarah. After she implemented the triage protocol and documented her workflows, her manager finally had to hire two junior analysts to handle the routine crisis intake. Sarah’s workload dropped by twenty percent, and she finally had time to lead the strategic initiative she had been promising for a year. Luna: So the system caught up to her. It took effort, but it worked. Lucas: It did. And the lesson is not to avoid being excellent. It is to ensure your excellence is scalable. Don't be the human patch for a broken system. Be the architect who fixes it, or the leader who builds the team that maintains it. Luna: Which means knowing when to stop being the hero and start being the manager. Lucas: Exactly. The most dangerous trap is thinking that your value lies in how much you can endure. Your value lies in how much you can enable others to succeed. Luna: A powerful shift in mindset. Next time you get that urgent request, ask yourself: am I solving this, or am I just delaying the inevitable? Lucas: Or consider this: if you stopped fixing everything tomorrow, would the world end, or would the organization finally admit it needs more resources? The answer tells you where you stand.