Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Handle a Boss Who Undermines Your Authority
Transcript
- Lucas: You know that moment in a meeting when you present a plan, your team nods along, and then your boss pipes up with, 'Are you sure that's the right approach?' — in front of everyone. Suddenly you're not the authority figure anymore, you're the person being second-guessed. Luna: Oh, that's a gut punch. It's not just embarrassing — it erodes your team's trust in you. And it happens more often than we talk about. Lucas: Right. So today I want to drill into a specific scenario: a mid-level marketing director I'll call Jen. She worked at a mid-sized consumer packaged goods company — think yogurt, granola bars, that aisle. Her boss, the VP of marketing, had a habit of questioning her recommendations in cross-functional meetings. Luna: Was it a one-time thing or a pattern? Lucas: By the time Jen reached out to me, it had been going on for about four months. She'd present a media-buying strategy backed by data, and her boss would say, 'Hmm, I'm not sure that's the most efficient use of budget.' Or she'd propose a product launch timeline, and he'd ask, 'Did you stress-test the supply chain assumptions?' — again, in a room of fifteen people. Luna: That's textbook undermining. It makes her look unprepared, even when she's not. And it gives the team permission to ignore her authority because they see the boss doesn't fully back her. Lucas: Exactly. So the first question is: why do bosses do this? In Jen's case, I think there were two drivers. One, her boss was a former consultant who loved playing the devil's advocate — it was his default mode. Two, he genuinely believed he was 'staying involved' and 'adding value.' He didn't see the collateral damage. Luna: That's actually helpful framing — because it's not always malice. Sometimes it's a clueless leader who doesn't realize how their behavior lands. Lucas: Right. And the strategy changes depending on intent. But either way, you need to protect your authority. So here's the framework we worked through with Jen. Step one: have a private conversation where you name the pattern — but not in an accusatory way. Luna: How did she phrase it? Lucas: She said something like, 'I really value your input, and I've noticed that when you challenge my recommendations in team meetings, it sometimes creates confusion about who's driving the decision. Could we agree that you'll share any concerns with me one-on-one before the meeting, so we can align on the message?' Luna: That's smart. It frames it as a coordination issue, not a personal attack. And it gives him a clear action: pre-meet. Lucas: Exactly. Step two: when he does it anyway — and he will, at least at first — you don't get defensive. You use a clarifying question that redirects the spotlight. So in the moment, Jen would say, 'That's a great question. I actually ran a sensitivity analysis on that. The assumptions were X and Y. Want me to walk through the numbers?' Luna: That's good because it shows you're prepared and it keeps you in the driver's seat. You're not reacting to his challenge — you're owning the response. Lucas: Right. And it subtly reminds the room that you did your homework. The third step is escalation — but only if the pattern persists after a few weeks. Jen's boss continued the behavior even after she asked for pre-meets, so she scheduled a follow-up conversation and made it more explicit. Luna: What did she say? Lucas: She said, 'I've noticed that in the last two steering committee meetings, you raised concerns about my budget allocation in front of the CFO. When that happens, it undermines my credibility with the finance team. I need us to be a united front. If you have concerns, let's resolve them before we walk in the room.' Luna: That's firmer. And it names the specific consequence: the CFO now doubts her. That's hard to argue with. Lucas: Her boss actually apologized. He said he hadn't realized the impact. And he agreed to a ten-minute pre-brief before any major meeting. It wasn't perfect — he still slipped up occasionally — but the frequency dropped by about 80 percent. Luna: That's a win. And I think the key is that she didn't let it fester. A lot of people in her position would just suffer silently, hoping it stops, or they'd confront the boss publicly, which almost never ends well. Lucas: Yeah, public confrontation is a landmine. If you push back in the meeting, you look defensive. If you don't push back, you look weak. The only winning move is to handle it privately and preemptively. Luna: What about cases where the boss is deliberately trying to undermine you — like they see you as a threat? Lucas: That's a different animal. If it's intentional, the pre-meeting alignment might not work because the boss wants you to fail. In that scenario, you need to document every instance — date, meeting, exact words — and build a case. Then you go to HR or a skip-level, but only after you've tried the direct approach. Luna: And you have to be careful. HR's job is to protect the company, not you. So you need to frame it as a risk to the business: 'When my boss undermines my authority in front of the team, it slows decision-making and could cost us the quarter.' Lucas: Exactly. Jen's case didn't go that far — her boss was more clueless than cruel. But the framework works for both. Step one: align privately on process. Step two: redirect publicly with competence. Step three: escalate formally with evidence. Luna: I also think there's a preventive move here. When you start a new role or a new project, you can proactively set expectations with your boss about how you'll handle disagreements. Say something like, 'If you have a concern about my recommendations, I'd love to hear it before we present to the team so we can be on the same page.' Lucas: That's a great habit. It's essentially a pre-nup for the working relationship. And it makes the boss's future undermining a breach of an agreement, not just an awkward moment. Luna: So what happened with Jen in the end? Lucas: She stayed in the role for another year and ended up getting promoted. Her boss eventually wrote her a recommendation letter. The irony is that he thought he was being a helpful mentor the whole time — he just needed someone to show him the blind spot. Luna: That's a good reminder that many difficult bosses aren't monsters. They're just oblivious. And a lot of workplace suffering comes from not having the language to name what's happening. Lucas: Absolutely. And speaking of showing appreciation for the work we do here — we keep this show ad-free, and that's only possible because a small group of listeners chips in through buy me a coffee dot com slash fexingo. If this topic resonated with you, or if any of our episodes have helped you navigate a tough work situation, that support is what keeps us going. Luna: Yeah, it's genuinely just a way to say 'this matters' without any of the ad-clutter. And we really appreciate everyone who does. Lucas: So back to the framework — the key takeaway is that you have more agency than you think. You can't control your boss's behavior, but you can control how you respond. And a well-timed, well-framed conversation can change the dynamic more than you'd expect. Luna: I'd add one more thing: if you try the framework and it doesn't work, that's information. It tells you the situation might not be salvageable, and it's time to start looking for a new manager — not necessarily a new company, but a new boss. Lucas: That's a crucial distinction. People quit bosses, not companies. And sometimes the best career move is to find a leader who builds you up instead of chipping away at your authority. Luna: Well said. For now, that's the episode. Next time, we'll talk about what to do when your boss takes credit for your ideas — a classic but we've got a fresh angle. Lucas: Looking forward to it. Thanks for listening.