Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / Why Competent Managers Make Poor Leaders
Transcript
- Lucas: There is a specific kind of exhaustion that comes from working for a manager who is undeniably good at their job, just not the job they have now. I am talking about the brilliant individual contributor who gets promoted into management because they were the best coder, or the best salesperson, or the best analyst, but never actually learned how to lead people. Luna: Right, and the tragedy is usually that they think they are helping by doing the hard parts themselves, while everyone else watches them drown in details. Lucas: Exactly. And before we dive into the mechanics of why this happens and how to survive it, I want to mention something quick. 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 shows. It keeps us ad-free and allows us to dig into topics like this without corporate sponsorship pressure. Luna: Yeah, it makes a real difference. If we've helped you think through a career move or decision lately, consider supporting the show if you can. Lucas: So let's look at a case study that feels very current as we head into Q four of two thousand twenty-six. I was speaking with a former colleague named Sarah, a senior software engineer who was recently promoted to engineering manager. She is sharp, she knows the architecture better than anyone, but her team has missed three deadlines in a row because she keeps getting pulled into micro-fixes instead of unblocking her reports. Luna: That is classic expert mode. She is solving the problem in front of her instead of building the system to solve problems later. Lucas: Precisely. Sarah told me she spends forty percent of her day coding. On paper, that sounds productive. In reality, it creates a bottleneck. Her team waits for her approval on minor decisions because she has historically been the final word. So the interesting question is not why she is bad at her job, but why her old skills are actively hurting her new role. Luna: Because her identity is tied to being the smartest person in the room, and stepping back feels like losing value. Lucas: That is the core psychological trap. When you are an individual contributor, your value is measured by your output. Code written, deals closed, reports filed. As a manager, your value is measured by your team's output. But if you cannot decouple your ego from your hands-on work, you will always default to doing it yourself because it is faster and safer. Luna: And it feels safer because you control the quality, whereas delegating introduces risk and friction you have to manage. Lucas: Right. And for the listener dealing with a boss like Sarah, the first step is recognizing that this is not malice. It is misaligned incentives. Sarah thinks she is being a good leader by ensuring quality. You need to help her see that her involvement is actually creating the delay. Luna: How do you frame that conversation without sounding like you are criticizing their competence? Lucas: You frame it around capacity, not competence. You say something like, 'I know you can fix this bug in ten minutes, but if you spend an hour on it, the junior dev learns nothing and we lose visibility on the broader sprint.' You make it about the team's growth and the project's transparency. Luna: So you are giving them permission to stop doing the work by highlighting the downstream cost to the organization. Lucas: Exactly. It shifts the debate from 'am I good enough to delegate this?' to 'is my time allocated efficiently?' Most technical managers respond well to efficiency arguments because that is their native language. Luna: But what if they don't respond? What if they just insist on taking over because they distrust the team's ability? Lucas: Then you have to protect your own autonomy. This is where managing up gets tricky. You need to create structured checkpoints. Instead of asking for permission to proceed, you send a status update that says, 'Based on our last discussion, I am proceeding with option B. Let me know if you have concerns by end of day.' It forces them to act or stay silent. Luna: It puts the ball in their court without requiring constant meetings that waste everyone's time. Lucas: Yes. And it documents your initiative. If they intervene later, you have a paper trail showing you acted within agreed parameters. This protects you from the blame game when things go wrong, which is exactly what these bosses love to play. Luna: It also forces them to confront their own anxiety about losing control. If you keep moving forward, they either have to trust you or admit they are blocking progress. Lucas: Right. And there is another layer here that we often miss. The boss who is technically brilliant often struggles with strategic thinking. They see the trees so clearly they miss the forest. Sarah, for example, was obsessed with optimizing the database query speed, ignoring the fact that the user interface was broken. Luna: Because fixing the database is a known variable. Fixing the UI requires coordination with design, marketing, and customer support. That is messy and ambiguous. Lucas: Exactly. Ambiguity is the enemy of the expert mind. Experts want clear inputs and clear outputs. Managers deal with fuzzy requirements and shifting stakeholder opinions. If your boss is stuck in the weeds, they will push you deeper into the weeds too, because that is comfortable territory for them. Luna: So the subordinate ends up doing the emotional labor of keeping the project aligned while the boss focuses on technical perfectionism. Lucas: That is the invisible tax I mentioned earlier. You are not just doing your job; you are managing their focus. You have to be the one to pull them out of the detail and back to the business objective. You have to speak their language but steer the ship. Luna: Which means learning to translate business risks into technical terms they care about. Like saying 'this UI delay increases churn risk by five percent' instead of 'customers hate the design.' Lucas: Perfect. That connects the abstract business goal to the concrete metric they respect. Once you do that, you start to see a shift. They begin to appreciate the broader context because you are showing them how their technical decisions impact the bottom line. Luna: It turns them from a roadblock into a resource. Suddenly they are using their expertise to advocate for the team rather than hoarding it. Lucas: Yes. And this requires patience. It is not a one-time conversation. You have to reinforce this behavior every time you interact. When they offer to jump in, gently redirect. When they ask for a status update, provide the strategic summary first, then the technical details if asked. Luna: Teach them how to consume information efficiently. If you overload them with data, they will try to process it all. If you curate it, they will learn to trust your curation. Lucas: That is a crucial point. Curation is a skill. Many junior employees dump raw data on their bosses hoping for guidance. The smart employee synthesizes the data and presents options. This trains the boss to rely on your judgment, which gradually reduces their need to micromanage. Luna: It builds trust incrementally. Trust is just repeated proof that you can handle complexity without needing hand-holding. Lucas: Agreed. And if you find yourself in a situation where your boss simply cannot or will not change, you have to evaluate your long-term fit. Is this a temporary phase while they learn, or is this their permanent style? If it is the latter, you may need to look for a different manager who values delegation over execution. Luna: Because staying in a role where you are constantly fighting your boss's instincts burns you out faster than any workload ever could. Lucas: Absolutely. Your energy is finite. Spend it on growing your skills and building relationships, not on trying to rewire a competent but misguided leader. Sometimes the best management strategy is knowing when to adapt and when to move on. Luna: So the takeaway is not just how to survive, but how to decide if survival is worth the cost. Lucas: Right. Use the techniques we discussed to give it a fair shot. Document your wins, protect your boundaries, and try to educate your boss. But keep your eyes open for other opportunities. You deserve a leader who empowers you, not one who competes with you. Luna: And remember, even the best engineers have to learn to lead. It is a steep curve, but with the right support, it is possible to climb it together. Lucas: Thanks for listening. How would you handle a boss who refuses to delegate critical tasks?