Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Cost of Avoiding a Difficult Conversation
Transcript
- Lucas: There's a moment every manager recognises: you know you need to have a hard conversation with someone on your team, and you find a reason to put it off. Maybe you tell yourself they'll improve on their own. Maybe you're worried about damaging the relationship. I've been guilty of this myself. Luna: Oh, I think everyone has. That knot in your stomach before a one-on-one when you know the topic is performance, but you start with 'How was your weekend?' and hope the issue goes away. Lucas: Exactly. And it rarely goes away. In fact, the cost of avoiding that conversation is almost always higher than the cost of having it. I want to walk through a specific case from my reporting — a marketing director at a mid-size SaaS company who waited seven months to address a senior designer's declining quality and missed deadlines. Luna: Seven months? That's a long time. What happened in the end? Lucas: By the time the director finally had the conversation, three other team members had quit. One of them explicitly said in their exit interview that they'd been covering for the designer's mistakes, felt resentful, and saw that management wasn't going to act. The other two left for reasons that were partly about the same dynamic. Luna: So the cost wasn't just the designer's underperformance — it was the collateral damage to the rest of the team. Lucas: Right. The director told me that if she'd calculated the replacement cost of those three team members — recruiting, onboarding, lost productivity — it was around $240,000. Plus the designer eventually left anyway after the conversation. So the total tab for avoiding a 30-minute discussion was probably over $300,000. Luna: That's a staggering number. And it doesn't include the cultural hit — the trust that's broken when people see underperformance being tolerated. Lucas: Exactly. The thing is, most managers don't avoid these conversations because they're lazy. They avoid them because they don't have a framework for how to do it well. They're afraid they'll either say the wrong thing or damage the relationship irreparably. Luna: I interviewed an HR leader recently who shared a really useful model for this. She called it the 'three braids' approach. Want me to walk through it? Lucas: Please. I love a good framework that's actually practical. Luna: So the three braids are: first, state the specific behavior you've observed. Not a character judgment, just facts. Second, explain the impact of that behavior — on the team, on the work, on you. Third, ask a question that invites the other person into the problem-solving. Lucas: I like that. Instead of 'You're not pulling your weight,' it becomes something like: 'I noticed the last two design submissions came in three days late. That delayed the product launch schedule by a week. Can you help me understand what's happening?' Luna: Exactly. That third part is key — it turns a monologue into a dialogue. The other person often has a reason you don't know about. Maybe they're struggling with a new tool, or they have a personal issue they haven't shared. Lucas: And even if the reason is just a lack of discipline, framing it as a problem to solve together preserves the relationship. The person doesn't feel attacked, so they're more likely to engage. Luna: Right. And the research backs this up. Studies on feedback show that people are more receptive when the feedback is specific, behavior-focused, and delivered with curiosity rather than judgment. Lucas: One thing I'd add: timing matters. If you wait too long, the problem becomes part of the routine. The person might not even realise it's a problem anymore because no one has said anything. Luna: That's a great point. The marketing director in your case — did she say what finally prompted her to have the conversation? Lucas: She said it was a missed deadline that cost the company a major client demo. That was the catalyst. But she also admitted that if she'd done it earlier, the designer might have been able to correct course, and the team might not have unraveled. Luna: So what's the lesson for managers listening? Is it 'have the conversation sooner rather than later'? Lucas: Partly. But more specifically, I think it's: develop a habit of regular, low-stakes feedback. So when a bigger issue comes up, it doesn't feel like a confrontation — it's just another one of those conversations you have. Luna: That's a smart way to frame it. Create a culture where feedback is normal. Then the difficult conversation is just a slightly more intense version of the same thing. Lucas: I'll give you a concrete practice. In your weekly one-on-ones, spend the first two minutes on what I call 'micro-feedback.' One thing they did well, one thing they could do differently. Every week. After a few months, the idea of feedback being scary just disappears. Luna: That's simple but powerful. I've used something similar, and it really does change the tone of the relationship. Lucas: So to bring it back to the cost of avoidance: the next time you feel that knot in your stomach before a conversation, run the numbers. What's the cost of waiting? What's the cost of that person staying the same for another month, another quarter? The answer is almost always higher than the cost of a 20-minute chat. Luna: And if you need a script, use the three braids: behavior, impact, invitation. It gives you a structure so you don't freeze. Lucas: Yeah. And remember, the goal isn't to win the conversation — it's to help the person and the team. If you go in with that intent, it changes everything. Luna: On that note, I think we've given listeners a lot to work with. Next week, I want to talk about how to handle someone who gets defensive no matter how you deliver feedback. Lucas: That's a great follow-up. We'll see you next Monday.