Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Resists Change
Transcript
- Lucas: You've been working on a proposal for weeks. You've got the data, you've aligned with cross-functional partners, and you walk into your boss's office feeling confident. And then, within thirty seconds, you hear 'We tried that before' or 'It's too risky right now.' Sound familiar? Luna: That's the classic 'no' that kills more good ideas than any bad idea ever could. And it's not necessarily about the idea itself — it's about the boss's comfort zone. Lucas: Right. And that's the premise of today's show: how to manage a boss who resists change — not because they're malicious, but because they perceive risk differently than you do. We're going to talk about the psychology behind it, and one specific tactic that works. Luna: Let's start with the psychology. Why do some managers instinctively say no? Lucas: A big part of it is what behavioral economists call loss aversion. For a boss, the downside of a failed initiative often feels larger than the upside of a success. They have more to lose — reputation, budget, team morale. So their default is to preserve the status quo. Luna: So you're asking them to take a risk that they personally bear the cost of. No wonder they resist. Lucas: Exactly. The trick is to lower the perceived risk. That's where the small-bet tactic comes in. Instead of asking for a full launch, ask for a trial — a limited experiment with a clear stopping point. Luna: Give me a concrete example. If I'm a product manager who wants to introduce a new feature, what does that look like? Lucas: There's a case I've seen work: a product manager at a mid-sized software company wanted to add a chatbot to their customer support flow. Her VP was skeptical — worried about development costs and customer backlash. So she reframed it: instead of a full integration, she proposed a two-week A/B test with 5 percent of users. The cost was minimal, and she promised to kill it if satisfaction dipped. Luna: And the VP said yes? Lucas: He did. Because the ask was reversible. The VP could always say 'see, I told you' if it failed, without blowing the budget. But the test showed a 12 percent increase in satisfaction. And the chatbot eventually rolled out to all users. Luna: That's powerful. It reduces the commitment for the boss. They're not signing up for a year-long project — they're okaying a tiny pilot. Lucas: And it gives them an off-ramp if things go wrong. That's key. Bosses who resist change are often afraid of being wrong in front of senior leadership. A small bet lets them save face. Luna: So what other tactics do you recommend? Besides the small bet. Lucas: Pre-briefing. Before you formally pitch, have a casual conversation: 'I'm thinking about this idea, wanted to get your gut feel.' That way you can address concerns before the public meeting. It's harder for them to reject something they've already heard about. Luna: I do that, but sometimes I feel like it just gives them more time to find objections. Lucas: True, but if they find objections, you can prepare counter-arguments. And you're showing that you respect their opinion. That builds trust over time. Luna: Another thing I've noticed: mirroring their language. If your boss always talks about 'efficiency gains' or 'cost savings,' frame your idea in those terms. Lucas: Absolutely. Map your proposal to their stated priorities. If they're worried about team bandwidth, show how your idea frees up time in the long run. Luna: But what about bosses who are not just cautious but actively hostile to new ideas? Where nothing works. Lucas: That's a different animal. If the resistance is consistent across all ideas from all people, it's not about you — it's a toxic pattern. In that case, you might need to go over their head or find a champion elsewhere in the org. Luna: Or eventually, look for a different boss. Lucas: Right. But for the more common scenario — a boss who is risk-averse but not unreasonable — the small bet and pre-briefing are your strongest tools. Luna: Speaking of tools, I sometimes struggle with timing. When should I bring up an idea? Lucas: Avoid the moment right after a stressful meeting or at the end of the day when they're overwhelmed. Pick a calm, one-on-one slot. And always tie it to a current pain point. Luna: And the thing is, these tactics work because they respect the boss's constraints. If this kind of practical advice is valuable to you, a couple of dollars a month is genuinely what keeps these episodes coming — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: Yeah, we try to keep this ad-free and focused on real situations, and listener support makes that possible. Luna: Another thing that helps is building a track record. If you've delivered on small bets before, your boss will trust bigger ones. Lucas: That's a great point. Credit is like a bank account. Every time you execute, you deposit trust. So start with a low-risk win. Luna: So if you're facing a change-resistant boss, the takeaway is: shrink the ask, speak their language, and build trust over time. Lucas: Exactly. And don't take the first 'no' as final. Sometimes it's just a reflex. Come back with a smaller version. Luna: I love that. One final thought: how do you deal with a boss who says 'We tried that before'? Especially when you know the context was different. Lucas: Acknowledge their experience: 'You're right, we tried something similar in 2021. Let me share what's changed and why this version might work now.' Then present your data. Luna: Nice. So it's not about dismissing their memory — it's about updating it. Lucas: Exactly. And with that, we hope you try a small bet next time. Thanks for listening — we'll be back with another episode soon.