Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Avoids Hard Conversations
Transcript
- Lucas: So we get a lot of questions about the employee who says all the right things in a one-on-one, nods along, and then quietly never does the thing you asked. But there's a subtler version of that pattern that I think deserves its own episode. Luna: You mean the employee who just... avoids the conversation altogether? Lucas: Exactly. The one who schedules a conflict-resolution meeting and then 'forgets' to send the invite. Or who changes the subject when you bring up a missed deadline. Or who says 'let's talk about that later' and later never comes. That's the avoidance pattern. Luna: And it's more common than you'd think. There was that study from the Journal of Applied Psychology a while back that found nearly seventy percent of employees admit to avoiding at least one necessary workplace conversation. Lucas: Yeah, seventy percent. That's huge. And if you're a manager and you're seeing this in your team, you're not imagining it. The interesting thing is that avoidance rarely looks like bold defiance. It looks like busyness, or vagueness, or a sudden interest in process. Luna: Right. It's almost always a quiet behavior. So how do you actually get to the root of it without making the person feel cornered? Lucas: Well, first, I think it helps to understand why we avoid. Psychologists have a concept called the 'ostrich effect' — we literally bury our heads to avoid uncomfortable information. And in a work context, the discomfort often comes from a fear of conflict, a fear of looking incompetent, or sometimes a genuine belief that the conversation won't go anywhere anyway. Luna: So you're saying the avoidance might actually be a signal — like, the employee doesn't trust that the conversation is going to be productive? Lucas: Exactly. If they've had past experiences where bringing up a problem led to blame or no action, they've learned that silence is safer. That's a rational response, not just a personality flaw. So the manager's job is to make the conversation feel safer and more consequential at the same time. Luna: And that's the real skill. So what's the first step? You've got a one-on-one next week and you suspect your employee is avoiding a specific issue. What do you do? Lucas: The first step is to name the pattern, but in a neutral, almost curious way. You don't say 'you've been avoiding this.' You say something like 'I've noticed that when we talk about the quarterly forecast, you tend to steer us toward other topics. I'm curious what's behind that.' Luna: That's a really specific example. And it's not accusatory — it's observant. But what if the employee still deflects? Lucas: Then you shift from monologue to dialogue. You ask an open-ended question and then you stay quiet. Let them fill the space. The silence is uncomfortable, but it's productive. If they still deflect, you can offer a choice: 'We can talk about this now, or we can set aside twenty minutes later this week. Which works for you?' Luna: So you're giving them some control over the timing, which reduces the feeling of being ambushed. Lucas: Right. And you always want to end with a concrete follow-up. So even if the conversation doesn't fully happen in that moment, you've established that the topic is on the table and that it's going to be addressed. Luna: And that's where a lot of managers drop the ball, honestly. They bring it up once, get a vague 'let's talk later,' and then never circle back. The avoidance becomes the pattern because the manager accidentally endorses it. Lucas: Yeah, I've been guilty of that myself. And that's a good point to pause on. As managers, we often avoid these conversations because we're worried about hurting someone's feelings or making it worse. So we put it off, and the problem festers. Luna: And then by the time you actually have the conversation, it's a much bigger deal. You've built it up in your head, and the employee can feel the tension. That's a recipe for defensiveness. Lucas: Which is exactly why the neutral observation is so important. But I want to be careful here — there's a difference between naming a pattern and pathologizing the person. The language matters. Luna: Can you give an example of the difference? Lucas: Sure. Pathologizing would be 'you're defensive' or 'you avoid conflict.' Naming the pattern is 'I notice you tend to pause when I bring up the feedback from the last review.' One is a label, the other is a behavior you can address. Luna: That's a subtle but really important distinction. And it ties into something I read recently from the book 'Thanks for the Feedback' — that people are more likely to engage with feedback when it's about a specific moment, not a global character assessment. Lucas: Exactly. And that's the same principle here. So if you're going to have that conversation, you want to be prepared with a specific example and a specific impact. Like, 'When you didn't respond to the client's email for three days, the account manager had to follow up twice. That made us look disorganized.' Luna: That's a concrete consequence. And it's not about blame; it's about the effect on the team and the client. That's a much easier thing for someone to hear and act on. Lucas: And then you ask a question like 'What was going on there?' or 'How can we make sure that doesn't happen again?' You're moving from the past to the future, which gives them an exit from the shame spiral. Luna: You know, this reminds me of a situation I had with a direct report a couple years ago. She was brilliant, but she would never push back in meetings. She'd agree to everything, then complain to me in private. It took me a while to realize she was avoiding the conflict of disagreeing in front of the group. Lucas: And what did you do? Luna: I started preparing her before meetings. I'd say 'I know you have a different opinion on this — I'd like to hear it in the room. Could you share it when we get to that agenda item?' And I'd check in with her after. Lucas: That's a nice example of giving someone a runway. You're essentially saying 'I see you, I value your input, and I'm going to help you make it safe to share.' That's a powerful leadership move. Luna: And it worked. She started speaking up more, and eventually she didn't need the pre-briefing. But it took time and consistency. You can't just do it once and expect a transformation. Lucas: Right. And that's where a lot of managers get frustrated — they try a technique once, it doesn't work, and they conclude the employee is 'just like that.' But avoidance is a habit, and habits take time to break. Luna: So what's the biggest mistake you see managers make when they try to address avoidance? Lucas: I think it's making the conversation a one-time event. You address it once, you feel good, and then you never mention it again. But the employee needs reinforcement. They need to see that the safe space is consistent. Luna: And I'd add that managers need to check their own avoidance too. Because sometimes we're the ones avoiding the hard conversation with the underperformer, or with the peer who's overstepping. And if we're modeling avoidance, our team sees it. Lucas: That's a crucial point. And there's actually research that shows leaders who avoid difficult conversations create teams that are less likely to speak up. It's a contagion effect. Luna: So, you know, this kind of episode is exactly why we keep this show ad-free. We want to have these conversations without interruption, and we want to keep it accessible to anyone who manages people. Lucas: Yeah, and if that matters to you, you can support the show at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. It keeps the lights on and keeps us from ever having to sell out to a mattress company. Luna: Ha, exactly. And we're glad you're here. Now, back to that employee who's avoiding the performance review conversation. Lucas: Right. So another thing to watch for is the 'let me check my calendar' move. When you try to set a follow-up, they suddenly seem booked. If that happens more than once, you need to gently point it out: 'I've noticed it's been hard to find time. Is there something about this topic that feels uncomfortable?' Luna: And then what if they still say 'no, it's fine, let's find a time'? Lucas: Then you hold them to it. You say 'Great, I'll send you two options for next week. Let's make it happen.' And then you do. It's about setting a clear expectation that this conversation is not optional. Luna: Sometimes the avoidance is even more subtle, like the employee who agrees with your feedback in the moment but then doesn't change behavior. That's a form of avoidance too — they're avoiding the real work of change. Lucas: That's a really good point. And that's where you need to follow up with a clear action plan. You say 'So what specifically will you do differently? And when can I expect to see it?' Then you set a check-in date. That accountability is what turns feedback into change. Luna: And what about the employee who avoids by over-committing? They say yes to everything and then miss deadlines. That's like avoidance in disguise. Lucas: Totally. They're avoiding the discomfort of saying no or of admitting that they can't handle the workload. So you need to make it safe for them to say 'no.' You can say 'I know you want to be helpful, but I'd rather you be realistic. What's your actual capacity here?' Luna: And that requires trust. They have to believe that saying no won't damage their reputation with you. Lucas: Exactly. And building that trust is a long game. Every time they say no and you respond with 'thanks for being honest,' you're reinforcing the behavior. And then one day, you'll have a team where difficult conversations are just... conversations. Luna: I think that's the goal, right? To get to a place where you don't have to use these tactics because the culture makes it safe to speak up. Lucas: Yeah. But until then, the tactics help. And I think the core principle is this: avoid the avoidance. If you sense it, name it early, and deal with it directly. The longer you wait, the harder it gets. Luna: And on that note, a question for our listeners — have you ever had an employee who avoided a difficult conversation? How did you handle it? We'd love to hear your stories. Lucas: You can share them with us on social media, and we might read a few on a future episode. But for now, we hope this gives you a bit of a roadmap for tackling avoidance on your team. Thanks for being here with us.