Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Avoids Conflict
Transcript
- Lucas: So there's a type of difficult boss we haven't covered yet, and it might be the most insidious one because it never raises its voice. Luna: The passive-aggressive type? Lucas: Close, but I'm thinking of the conflict-avoidant boss. The one who would rather let a project spiral than call out a problem. And the cost isn't just a few awkward meetings — it's real money and talent. I was reading about a mid-sized tech company where the CTO avoided confronting a senior engineer's recurring missed deadlines. The engineer eventually left, and the post-exit interview revealed he'd been disengaged for months because no one ever told him he was underperforming. The CTO thought he was being kind. He was actually being negligent. Luna: That's brutal. And probably more common than we think. So what's the move when your boss is that person? You can't exactly force them to have a hard conversation. Lucas: Right, and that's where the research from organizational psychologist Liane Davey comes in. She's written a lot about 'productive conflict' — the idea that healthy teams fight about the work, not each other. The first step is to stop framing the issue as 'my boss hates conflict' and start framing it as 'our team lacks a structure for surfacing disagreements.' Luna: Okay, that reframe is helpful. But how do you actually create that structure from below? Lucas: One tactic Davey calls 'extreme questioning.' Instead of asking your boss, 'Don't you think we should address this?' you ask, 'What would it take for us to have a direct conversation about the timeline?' That shifts it from a personal challenge to a problem-solving exercise. You're not forcing your boss to be brave; you're inviting them into a process. Luna: I like that. It's less confrontational, but it still makes the elephant visible. So you're kind of leading your boss to the hard conversation by making it feel safe. Lucas: Exactly. And sometimes you have to make it even more concrete. Say you're in a project meeting and the deadline is clearly slipping. A conflict-avoidant boss will dance around it — 'let's revisit next week' or 'maybe we can adjust some priorities.' You can step in with, 'I want to flag that we're three weeks behind on the deliverable. Can we spend ten minutes now to name the blockers and decide how to handle them?' You're not accusing anyone; you're just introducing the topic with a clear label. Luna: And then the boss has to either engage or visibly deflect. Either way, you've put the issue on the table. Lucas: Right. But here's a wrinkle — sometimes the conflict avoidance is so deep that your boss will still find a way to deflect. That's when you need a fallback: the written trigger. Send an email after the meeting that says, 'Just to recap, we agreed to revisit the timeline in two weeks. I'll prepare a status update.' That creates a paper trail and a future commitment, which is harder to ignore. Luna: That's smart. It's not passive-aggressive; it's just professional. And it protects you if things go south. Lucas: Absolutely. But we should also talk about the personal toll. Working for a conflict-avoidant boss can be exhausting because you're constantly second-guessing yourself. You start to wonder, 'Is it me? Am I the problem?' It's a form of gaslighting, even if unintentional. Luna: Yeah, I've had that. You walk on eggshells without even realizing it. How do you protect your own sanity in that environment? Lucas: One thing that helps is to get external validation. Talk to a trusted colleague or mentor outside your team. Not to gossip, but to reality-check your perception. If two other people say, 'Yeah, the boss never addresses issues directly,' you know it's not you. That's crucial for your confidence. Luna: Good point. And I'd add that you should document your own contributions and decisions, so you have a record of your performance that isn't dependent on your boss's feedback. Lucas: That's a key point. Because when your boss avoids giving feedback, you end up with no data on your performance. You're flying blind. So you have to create your own feedback loops — ask clients or cross-functional partners for input, track your own metrics. It's not ideal, but it's better than nothing. Luna: And that data can be a lifeline if you ever need to escalate to HR or a higher-up. If you can show that you've tried to address issues directly and nothing changed, you're in a much stronger position. Lucas: Exactly. But let's back up a step. Before you escalate, you should give directness a real shot. And here's a counterintuitive tip: sometimes you have to be the one to model the behavior you want from your boss. If you're direct with them — respectfully, of course — they might mirror that back. It's not guaranteed, but it's worth trying. Luna: So you're saying we should be the boss we wish our boss would be. Lucas: Ha, something like that. And speaking of directness — I want to be direct about something real for a second. You know how this show is ad-free? That's not an accident. It's because a small group of listeners chip in monthly through buy me a coffee dot com slash fexingo. That literally funds the production and keeps us independent. Luna: Yeah, it's pretty amazing. We've had some people ask, 'How is this free?' and the answer is, it's not — it's supported by people who find value in it. Lucas: Right. So if you've gotten one useful tip from this episode, and you're in a position to support the show, that's the way to do it. No pressure, just a fact. And we're back to the issue at hand — because there's another layer to this conflict-avoidance thing that we haven't touched yet. Luna: What's that? Lucas: The cost to the team's decision-making. When your boss avoids conflict, you end up with decisions that are made by committee, or worse, not made at all. I read a study that found teams with conflict-avoidant leaders were significantly more likely to have projects stall. And it's not just about deadlines — it's about innovation. If nobody feels safe to disagree, you get groupthink. Luna: Groupthink is scary. That's how companies make terrible choices that everyone saw coming. Lucas: Exactly. So a practical move is to introduce 'devil's advocate' moments into your meetings. You can say, 'Before we lock this in, who wants to play devil's advocate for two minutes?' That gives your boss a safe way to voice concerns without feeling like they're initiating conflict. And it nudges the team toward healthier debate. Luna: That's a clever workaround. You're creating a structure for disagreement that doesn't feel personal. Lucas: And it works. I've seen teams adopt that and suddenly people who were silent for months start contributing. The boss doesn't have to be the one to break the silence; you've given everyone permission. Luna: So what if you've tried all this and the boss still won't engage? At what point do you say, 'This isn't working'? Lucas: Good question. If you've made several attempts — say, over a quarter — and there's no shift in behavior, then you have a choice. You can escalate to someone above your boss, but you need to be smart about it. Frame it as a business concern, not a personality clash. 'I'm worried about the project timeline because we haven't resolved the blocker. I've raised it directly, but I need help unblocking it.' That's a legitimate reason to go over someone's head. Luna: And if that doesn't work either? Lucas: Then you might need to think about your own future. If the conflict avoidance is so systemic that it's hurting your ability to do your job, that's a sign the organization isn't a good fit for your working style. And that's okay. Knowing when to leave is a form of managing up, too — to yourself. Luna: That's a fair point. Sometimes the best boundary is a new job. Lucas: But let's end on a more positive note. There's a great example of a team that turned this around. A product manager at a large bank noticed her boss would never push back on her ideas, even when they were half-baked. Instead of getting frustrated, she started bringing two options to every meeting — a safe one and a more ambitious one. She'd say, 'I'm torn between these. What's your gut feeling?' That gave her boss an easy way to disagree without feeling confrontational. Within a few months, her boss was initiating those conversations on their own. Luna: That's a great success story. It shows that with patience and the right framing, you can actually help a conflict-avoidant boss build that muscle. Lucas: It's not always possible, but it's worth trying. Because at the end of the day, avoiding conflict doesn't avoid the problem — it just delays it and makes it bigger. When you're the one who steps in with a little structure and empathy, you might just save the project, the team, and even your boss's career. Luna: And maybe your own sanity. Thanks for the great breakdown, Lucas. Lucas: Anytime, Luna. And to our listeners — if you've got a boss who never wants to fight, we'd love to hear how you've handled it. You can reach us through the show notes or on social. Until next time.