Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Coach an Employee Who Avoids Hard Conversations
Transcript
- Lucas: You have a direct report who's great at their job — meets deadlines, produces solid work, gets along with everyone. But the moment a tough conversation comes up, they freeze. Or they deflect. Or they just say 'I'll handle it' and then nothing happens. Luna: And you know that if you don't address it, it's going to create bigger problems down the road — stalled projects, resentment from teammates, maybe even a blown-up client relationship. Lucas: Exactly. So how do you coach someone who avoids hard conversations? That's today's question. I'm Lucas. Luna: And I'm Luna. And before we dive into the playbook — if you're listening and you've ever had to manage someone through this, or you're that person yourself, we've been there. This show stays ad-free because listeners like you support it at buy me a coffee dot com slash fexingo. No pressure. Just a heads-up that we appreciate you being here. Lucas: Really. It means we can keep doing deep dives on specific management problems without selling you anything. Okay. So let's start with a real case. I was talking to a product manager at a mid-size SaaS company — let's call her Priya. Luna: What was the situation? Lucas: Priya had a senior engineer, very talented, but he would avoid any conversation that involved pushing back on a stakeholder or saying no to a feature request. He'd say 'I'll follow up' and then just never do it. The team started getting blocked because decisions weren't being made. Luna: So the avoidance was actually creating more work for everyone. Classic downstream effect. Lucas: Right. And Priya's instinct was to just take over those conversations herself. But that's not sustainable. She needed to coach him to do it himself. Luna: So where do you even start? Do you just tell them 'you need to be more direct'? Lucas: That rarely works. They already know they avoid conflict. Telling them doesn't help. So first, you have to understand why. There are two broad categories: conflict-avoidant and conflict-averse. Avoidant means they've learned that conflict is dangerous — maybe a past boss yelled at them, or they have a family history of explosive arguments. Averse means they simply find it uncomfortable, but they can be coached through it. Luna: So the first step is diagnosis. How do you tell the difference? Lucas: You ask. Privately, in a one-on-one, you say something like: 'I've noticed you tend to hold back when there's a disagreement. I want to understand what's going on for you.' Not accusatory. Just curious. In Priya's case, the engineer said he was afraid of damaging relationships. That's a fear-based response — but not a trauma response. So he was averse, not avoidant. Luna: That's a good distinction. Because if it's trauma-based, you might need to involve HR or a coach. But if it's just discomfort, you can work with it. Lucas: Exactly. So step two is what I call the 'pre-mortem check-in.' Before a potentially difficult conversation, you and the employee script out the worst-case scenario. What's the worst that can happen? Usually, it's 'the other person gets angry' or 'they say no.' And then you ask: 'And then what?' Often they realize the consequences aren't catastrophic. Luna: So you're basically doing exposure therapy for conversations. Lucas: Exactly. Low-stakes practice. You can even role-play the conversation with them. Priya did this with her engineer before a meeting with a demanding stakeholder. They rehearsed his opening line: 'I understand you want this feature, but given our current capacity, we can't commit to it this quarter. Here's what we can do.' Luna: And did he use it? Lucas: He did. And the stakeholder didn't get angry. He just said 'okay, let's prioritize for next quarter.' The engineer came back to Priya and said 'that was fine.' And that small win built momentum. Luna: So step three is to give them repeated low-stakes opportunities. Not throwing them into a boardroom negotiation, but starting with small disagreements. Lucas: Right. Over the next four weeks, Priya gave him one 'hard conversation assignment' per week. First it was pushing back on a minor timeline. Then it was declining a low-priority request. Then it was giving constructive feedback to a junior dev. Each time they debriefed afterwards — what worked, what didn't. Luna: That debrief is key. Because they need to see that the world didn't end. And that they actually got a better outcome by speaking up. Lucas: Yes. And here's an important nuance: avoidance is not a neutral behavior. It's a choice that has consequences. So as a manager, you need to name that. In Priya's case, she said: 'When you avoid the conversation, the decision gets delayed, the team gets blocked, and someone else has to pick it up. That's a cost.' Not punishing, just factual. Luna: That reframes it from a personality trait to a behavior that can change. Lucas: Exactly. And within a month, that engineer was proactively scheduling difficult conversations. He wasn't perfect, but he was doing it. And the team's velocity improved because decisions were happening faster. Luna: So the three steps: diagnose whether it's aversion or avoidance, use the pre-mortem to reduce fear, then assign escalating practice conversations with a debrief. Lucas: That's the framework. But there's one more thing: sometimes the employee genuinely doesn't know what to say. They're not afraid — they just lack the script. In that case, you can give them sentence starters. 'Here's a template for saying no.' 'Here's how to start a feedback conversation.' That's coaching, not doing it for them. Luna: And what if after all that, they still avoid? When do you escalate? Lucas: If after six to eight weeks of consistent coaching you see zero progress — they still deflect, they still say 'I'll handle it' and don't — then it's a performance issue. You need to be direct: 'This is a core expectation of your role. If you can't meet it, we need to discuss whether this is the right position for you.' That's tough, but it's fair. Luna: And it protects the rest of the team from the ripple effects of one person's avoidance. Lucas: Right. Because the cost of avoidance isn't just the one conversation. It's the trust that erodes when people feel like decisions are never made. So coaching is worth the investment. But it's not infinite. Luna: Good advice. And I think a lot of managers don't realize that avoidance is a skill gap, not a character flaw. You can teach it. Lucas: Exactly. And if you've got a story about coaching someone through this, we'd love to hear it. You can find us on the Fexingo Business podcast network. I'm Lucas. Luna: And I'm Luna. See you next week.