Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Avoids Conflict
Transcript
- Lucas: So we've spent a lot of episodes on the employee who talks too much, the employee who pushes back too hard, the one who says 'that's not my job.' Luna: Right — the loud, difficult archetypes. Lucas: Exactly. But there's another type that's just as damaging to a team, and it's much harder to spot because they seem like the perfect employee on the surface. Luna: You're talking about the conflict-avoidant team member — the one who never disagrees, never pushes back, just says 'sounds good' to everything. Lucas: That's exactly it. And let's ground this in a real example. I was talking to a product manager at a mid-sized SaaS company — let's call them Jenna. She manages a team of five engineers and one designer. One of her senior engineers, Michael, always says 'yes' in meetings. Never questions a timeline, never flags a technical risk. Luna: Which sounds great until things blow up. Lucas: Exactly. Michael would agree to deliver a feature in two weeks, knowing full well it would take four. He'd nod along to a design direction he knew would create technical debt. But he never said anything in the meeting. He'd just go back to his desk and quietly struggle — or worse, deliver something half-baked. Luna: And what did Jenna do about it? Lucas: That's where it gets interesting. And before I dive into that, I want to be transparent about something — and this ties directly to why we can spend time on stories like Jenna's. Luna: Go ahead. Lucas: A small number of listeners support this show every month through buy me a coffee dot com slash fexingo. No ads, no sponsors — just people who find value in these conversations and want to keep them coming. That's what funds episodes like this one. Luna: Yeah, and it allows us to dig into these specific cases without having to wrap everything in a commercial break. It makes a real difference. Lucas: So back to Jenna. She realised that Michael's agreement was actually a form of avoidance. He wasn't being agreeable — he was protecting himself from conflict. And that was damaging the team's decision quality. Luna: How did she figure that out? Was it from missed deadlines? Lucas: Partly. But the real clue came during a retrospective. When the team discussed a project that went over schedule, Michael finally admitted he'd known the timeline was unrealistic from day one. He just didn't want to 'rock the boat.' Jenna recognised the pattern. Luna: So what did she do? Did she start calling him out in meetings? Lucas: No — and that's key. Public pressure would only reinforce his avoidance. Instead, she used a technique she called 'The 10-Minute Devil's Advocate.' At the end of every one-on-one, she'd assign him a specific point from a recent decision and ask him to argue against it. Not as himself — as a role. Luna: So she gave him permission to disagree. That's smart. Lucas: Exactly. She'd say, 'For the next ten minutes, I want you to play devil's advocate on our decision to use this third-party API. Find every reason it could go wrong.' And because it was framed as a role, Michael could engage without feeling like he was being confrontational. Luna: Did it work? Lucas: It took about three weeks, but yes. He started surfacing real risks — things Jenna hadn't considered. And eventually, he began offering those critiques in team meetings without the role-play prompt. He just needed to build the muscle of productive disagreement. Luna: I love that. But I can already hear a listener thinking: 'What if my team is remote? Can I still do the devil's advocate thing over Zoom?' Lucas: Great question. And the answer is yes, but you have to be more deliberate. In a remote setting, silence is even harder to read. So you need to make the role-play explicit. Send a calendar invite that says 'Pre-mortem on Project X — your role: critic.' Put it in writing. Luna: So you're structuring the disagreement ahead of time. That removes the social friction. Lucas: Exactly. And here's another thing Jenna did that I think is crucial for anyone managing a conflict-avoider: she changed her own language in meetings. Instead of asking 'Does everyone agree?' — which invites a quick nod — she started asking 'What's the biggest risk you see here?' Specific, directed, and framed as a contribution. Luna: That shifts the burden from 'disagreeing' to 'helping.' It's a small linguistic tweak but a big psychological shift. Lucas: Right. And she also modelled the behaviour herself. In one sprint planning session, she openly said 'I think I was wrong about the priority on this feature. Let's revisit.' That gave Michael — and everyone else — permission to admit uncertainty. Luna: That's huge. Because a lot of managers think they have to project certainty all the time. But that actually shuts down dissent. Lucas: Exactly. And there's research to back this up. Amy Edmondson at Harvard has studied psychological safety for decades. One of her key findings is that teams with higher psychological safety don't have less conflict — they have more productive conflict. The conflict-avoider is actually a symptom of low safety. Luna: So if you have a Michael on your team, the fix isn't just coaching him — it's also examining the environment you've created. Lucas: That's right. Jenna realised that her own tendency to move fast and project confidence was inadvertently discouraging pushback. Michael wasn't the only one avoiding conflict — the whole team had a norm of 'don't question the plan.' She had to break that norm herself. Luna: What about the employee who's conflict-avoidant because of past experiences? Maybe they had a boss who punished disagreement. Lucas: That's a really important layer. If Michael had been burned before, no amount of role-play will fix it overnight. In that case, you need to build trust slowly and consistently. One technique is to explicitly thank someone when they do disagree. Say 'I really appreciate you flagging that — it makes our decision stronger.' That reinforces the behaviour. Luna: So the manager has to be hyper-aware of how they respond to the first few instances of pushback. If you get defensive even once, you undo weeks of work. Lucas: Absolutely. And that's why I think the single most powerful tool for a manager dealing with a conflict-avoider is a simple question in your next one-on-one. Ask: 'What's one thing you think I'm wrong about?' And then — and this is the hard part — sit in silence and wait for an answer. Luna: Don't fill the silence. Let them feel the weight of the question. Lucas: Right. Most people will give a safe answer at first. But if you stay quiet, they might dig deeper. And even if they don't, you've sent a signal: your honest disagreement is welcome here. Luna: I think that's a good place to leave it. One practical action, backed by a real story. Lucas: Yeah. If you've got a Michael on your team, try the devil's advocate exercise for two weeks and see what changes. And if you've been that Michael yourself — I think we all have at some point — maybe give yourself permission to speak up tomorrow. Luna: Thanks for listening, everyone. We'll be back next Monday with another episode of Manager Mondays. Lucas: Take care.