Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / Why Smart Managers Sabotage Their Own Success
Transcript
- Lucas: There is a specific kind of exhaustion that comes from working for someone who is genuinely brilliant at their old job but has no idea how to be a manager in their new one. It is not malice. It is not even insecurity, necessarily. It is simply the gravitational pull of competence. Luna: Right. The person who was the top salesperson gets promoted to VP and then spends three hours editing your emails because they think their copy is better. Which it might be, but it is also completely wrong for the role. Lucas: Exactly. And this brings us to the core problem we are tackling today: the delegation deficit. We have covered bosses who change rules, or take credit, or never give context. But there is a more subtle, pervasive issue where the boss is technically helpful but structurally destructive. They are solving the wrong problems because they are addicted to being the hero. Luna: So we are talking about the boss who steps in when things go slightly off-track instead of letting you navigate the fix. The micro-interventions. Lucas: Precisely. These are the small corrections that add up to massive inefficiency. Let me set the scene with a case study I looked at recently. A senior product lead at a mid-sized tech firm. Her name was Elena. Elena was exceptional at coding. She could debug legacy systems faster than anyone on the team. When she got promoted, she didn't stop coding. She started taking over the hardest tickets. Luna: And her junior developers just watched? Or did they try to push back? Lucas: They tried. But Elena framed it as mentoring. She would say, 'Watch how I structure this function,' while actually rewriting the code they had already written. Within six months, two of her best engineers left. Not because Elena was mean, but because they felt useless. They couldn't learn anything because she wasn't letting them make mistakes. Luna: That is a classic example of the individual contributor trap. You promote the best player to coach, but they keep playing instead of coaching. Lucas: And here is where it gets tricky for us as employees. Because Elena thinks she is helping. She sees a deadline approaching, sees a risk, and jumps in to save the day. To her, she is protecting the team. To the team, she is stripping away ownership. Luna: It creates this weird dependency. If you know your boss will fix it, why bother learning how to fix it yourself? You just wait for them to step in. Lucas: That dependency is the real cost. And it shows up in performance reviews later. The boss says, 'This employee lacks initiative.' But the reality is, the boss never gave them the space to show initiative. It is a self-fulfilling prophecy of incompetence born from excessive competence. Luna: So how do we identify this pattern before it ruins our projects? Is there a signal we can look for early on? Lucas: Yes. Look at the ratio of meetings to output. In a healthy team, the manager’s job is mostly coordination, unblocking, and strategy. If your boss is spending forty percent of their week doing actual execution work, something is broken. That is the first red flag. Luna: I like that metric. Forty percent seems high, but for a technical manager, it feels plausible if they are still attached to the codebase. Lucas: It is very plausible. Especially in tech. There is a cultural bias that says 'real work' is hands-on. So managers feel guilty when they are just talking to people. They revert to what feels productive, which is doing the task. Luna: But that guilt is misplaced. Their productivity is now measured by their team's output, not their own. If the team fails because they were waiting for the boss to code, the boss failed. Lucas: Spot on. And this leads to the second signal: the rework rate. If you notice your boss constantly redoing your work without explaining why, or if they change your final deliverable right before it goes out, ask yourself if it is quality control or comfort seeking. Luna: Comfort seeking. I think that is the key phrase. They are comfortable in the weeds. The strategic view feels vague and scary to them. Lucas: It is terrifying for many high performers. The weeds are concrete. Strategy is ambiguous. So they retreat to the weeds. But we need to manage this dynamic. We cannot just tell our bosses to stop. They will not listen. Luna: Agreed. Confrontation usually makes them dig in. They feel attacked. So what is the alternative? How do we gently steer them back? Lucas: You use the 'pre-mortem' technique. Before you start a project, explicitly define who owns which decisions. Write it down. Say, 'I will handle the design, you review the timeline.' Then, when they try to jump in, you refer back to the agreement. 'Hey, remember we agreed I would handle the design phase so you could focus on stakeholder alignment?' Luna: That is clever. It removes the personal element. It is not you rejecting their help; it is you honoring the plan. It makes it harder for them to override without looking like they are breaking the rules. Lucas: Exactly. And you have to be willing to fail. This is the hardest part. If your boss steps in because they think you are struggling, you have to prove you can struggle successfully. You have to let them see you hit a wall, solve it, and move on. Without that proof, they will never let go. Luna: That requires a lot of patience. And a thick skin. Because they might criticize your method even if the result is good. Lucas: They will. And you have to ignore the nitpicking if the outcome is solid. Focus on the end state. If the project launches on time and under budget, you have won. The boss’s ego bruise is the price of admission. Luna: So, summary for our listeners: Watch the time allocation, track the rework, set explicit boundaries early, and allow yourself to make small mistakes to build trust. Lucas: Perfect summary. It is about shifting the power dynamic from 'hero worship' to 'accountability'. Once your boss trusts your accountability, they can finally relax into their actual role. Luna: And if they can’t? If they just refuse to adapt after six months of this? Then we have to talk about whether this is a fixable management style or a fundamental mismatch. Lucas: That is the next episode. But for now, remember that competence is not always a virtue in leadership. Sometimes, it is the cage. Luna: Well said. Now, speaking of cages, have you seen the latest stats on remote work retention? Lucas: Actually, before we dive into that, I want to pause for a moment. Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making this many of these. No ads, just us talking. Luna: Yeah, it really helps keep the lights on and allows us to research these cases properly. If you value the deep dives, consider joining in. Lucas: Anyway, back to those remote work stats. The numbers are shifting again. Luna: Right. So, returning to the topic of delegation deficits. Is there a tool or framework you recommend for documenting those decision rights we mentioned? Lucas: The RACI matrix is the standard. Responsible, Accountable, Consulted, Informed. It sounds bureaucratic, but it forces clarity. Most conflicts arise because everyone thinks they are 'Responsible' when only one person should be. Luna: I have used RACI before, but usually as a formality. Have you found it effective in practice when a boss is trying to micromanage? Lucas: It works if you enforce it. When the boss tries to take the 'Responsible' slot, you politely ask, 'Who is going to be held accountable if this goes wrong?' That question usually makes them step back. Accountability is heavy. They often prefer the lightness of consulting without the weight of responsibility. Luna: Ouch. That is a sharp insight. Shifting accountability is the ultimate deterrent to unwanted intervention. Lucas: It is. And it puts the ball in their court. If they want to do the work, they have to accept the blame for any errors. Most bosses realize that is not worth the hassle. Luna: So we are essentially gamifying their laziness. Or rather, their desire to avoid risk. Lucas: Exactly. We are using their self-interest to align with your professional growth. It is not about winning an argument. It is about designing a system where delegation is the path of least resistance for them. Luna: That is a much more sustainable approach than hoping they have an epiphany. Systems beat willpower every time. Lucas: Always. So, to wrap up this angle: Identify the competence trap, document the roles, and enforce accountability. It changes the dynamic from chaos to clarity. Luna: Clear and actionable. I think our listeners will find that particularly useful for navigating those tricky mid-level management layers. Lucas: Hopefully. It is a difficult balance, but worth the effort. Next week, we will look at how to handle the boss who is competent but unpredictable. Luna: Looking forward to it. For now, go update your RACI charts and watch your boss squirm. Lucas: Or at least watch them appreciate the lack of surprises. See you then.