Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Disagree With Your Boss Without Getting Fired
Transcript
- Lucas: Luna, I want to start with a question we got from a listener named Priya. She works in marketing at a Fortune 500 retailer, and she writes: 'My boss just announced a new campaign direction that I know is going to flop. Every data point I have says the customer segment they're targeting isn't ready. How do I tell them they're wrong without getting labeled as difficult?' Luna: Oh, that's a tough one. Because the instinct is either to say nothing and watch it fail, or to blurt out 'that's a terrible idea' in the meeting. Both have bad outcomes. Lucas: Exactly. And the research backs that up. There's a study from Harvard Business Review that looked at 1,500 employees across industries. People who regularly challenged their boss's ideas were rated as more competent on performance reviews — but only if they did it in a specific way. The ones who just said 'I disagree' were seen as insubordinate. Luna: So the framing is everything. What's the right way? Lucas: There's a technique I call the 'pre-buttal.' It's three steps, and you do them in order. Step one: acknowledge the boss's reasoning before you challenge it. Say something like, 'I see why you're targeting that segment — the margins are higher and they've been under-marketed.' That signals you're on the same team. Luna: So you're validating their logic. That lowers defensiveness before you even get to the 'but.' Lucas: Right. Step two is what I call 'data sandwich.' You present your counter-evidence framed as a question. Not 'the data shows you're wrong,' but 'I ran the numbers on retention rates for that segment, and I'm curious if you think the engagement metrics could offset the lower conversion we saw last quarter?' Luna: That's smart — it invites them to problem-solve with you instead of defending their position. Lucas: And step three: offer an alternative, not just a critique. The worst thing you can do is shoot down an idea without giving something in its place. So after you've acknowledged their logic and gently surfaced the contrary data, you say, 'What if we ran a three-week A/B test on a smaller sample first? That way we de-risk the full launch and still move fast.' Luna: That also makes you look proactive. You're not the person who says 'don't do that' — you're the person who says 'here's how to do it better.' Lucas: Exactly. And there's a linguistic trap a lot of people fall into: starting with 'I might be wrong, but...' or 'This is probably a dumb question, but...' Research from Stanford shows that those qualifiers actually reduce your perceived credibility. Listeners hear the uncertainty first and anchor on it. Luna: So you're better off just stating your case confidently after doing step one. Lucas: Right. Now, what if you've already disagreed in a way that felt clumsy? Priya mentioned she's already sent a cautious email that her boss didn't respond well to. There's a recovery play. Luna: What's the move there? Apologize? Lucas: Not exactly. You don't apologize for having a different opinion — you apologize for the delivery. So you go to them and say, 'I realize my email yesterday came across as more negative than I intended. I actually want this campaign to succeed, and I think there's a way to test it that reduces risk. Can I walk you through what I'm seeing?' Luna: That reframes it as collaboration. You're still holding your ground, but you're doing it in a way that respects their authority. Lucas: And that's the core skill here: disagreeing without challenging their status. Because most bosses, especially if they're insecure or under pressure, read disagreement as a threat to their position. Your job is to make it clear that you're trying to protect the outcome, not undermine them. Luna: I think a lot of people also freeze because they don't know the right time to bring it up. Do you do it in the meeting, or pull them aside afterward? Lucas: Great question. If the decision hasn't been finalized yet — like it's a draft or a proposal — you can raise it in the meeting using the pre-buttal. But if the boss has already announced it as a done deal, pull them aside privately. Public pushback on a finalized decision feels insubordinate even if you're polite. Luna: That's a really good nuance. And it's something a lot of early-career people miss. Lucas: Yeah. I had a friend who worked at a consulting firm — first year out of business school. She was in a client meeting and the partner said they should pursue a certain strategy. She knew it was wrong. She raised her hand and said 'I think the data suggests otherwise.' The partner got visibly upset. She never made that mistake again. Luna: What should she have done instead? Lucas: She should have waited until after the meeting, caught the partner in the hallway, and said, 'I noticed something in the data that might change our approach — do you have five minutes to look at it together?' That preserves the partner's authority in front of the client while still surfacing the issue. Luna: It's almost like you're giving them the chance to be the hero who catches the mistake. Lucas: Exactly. And good leaders appreciate that. Now, there's one more layer to this. Sometimes the boss is wrong and they know it, but they're wedded to the idea for political reasons — maybe a senior exec pushed it, or it's their pet project. In that case, your data probably won't change their mind, no matter how you frame it. Luna: So what do you do then? Just go along with it? Lucas: You can still advocate — but you adjust your goal. Instead of trying to kill the idea, you try to limit the downside. Say, 'If we're going ahead with this, can I suggest we cap the initial spend at $50,000 and review after four weeks?' That way you're still being helpful and you're protecting the company from a total disaster. Luna: That's a pragmatic middle ground. You've spoken your truth, but you're not fighting a losing battle. Lucas: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, it really helps. Even a small contribution keeps us from having to run ads, and it means we can keep digging into questions like Priya's. Lucas: Alright, back to the tactics. One last piece: if you're the boss, how do you encourage your team to disagree with you? Because Priya's boss probably thinks they're open to feedback, but their reaction says otherwise. Luna: That's a good flip. What would you recommend to managers? Lucas: You have to explicitly invite pushback and then reward it when it happens. Say things like, 'I want you to tell me if this is a bad idea — I won't be offended.' And when someone does disagree well, thank them publicly. That signals to the whole team that it's safe. Luna: And if you're the one who disagreed and it went well, follow up with a thank-you note. That reinforces the behavior. Lucas: Great add. So for Priya: use the pre-buttal, pick your timing, and if all else fails, limit the downside. You've got this.