We need to talk: Conversations every manager should master when tackling difficult situations
Difficult conversations bring risk: the risk of being misunderstood, of upsetting someone, of saying too much or too little. So instead, we delay. We drop hints. We tell ourselves ‘now isn’t the right time.’ And the moment passes.
Here's the brutal truth: 60% of new managers fail within their first two years, largely because nobody taught them how to have these conversations. And when managers suck at their jobs, people leave – 80% of employees have quit because of a bad boss.
Note: A bad boss isn’t just one who is a bully who yells or intimidates employees. There are several other attributes that bad managers often exhibit, including poor leadership stemming from lack of skills, support or emotional intelligence rather than active nastiness.
As a manager, it’s essential you learn to have these conversations, because: You control 70% of whether your team actually gives a damn. You have more influence over their success than any strategy deck or pizza party ever could. Companies that teach managers how to navigate tough conversations see enhanced ROI in the first year. Replacing someone can cost 50% or more, of their salary plus recovery time from a mistake…Ouch!
Example 1: Correcting missed deadlines or broken commitments
Scenario: Someone didn’t deliver. A task was late, a ball was dropped, and now the rest of the team is feeling it.
Why it’s difficult: You don’t want to micromanage. You worry about sounding accusatory. You like this person and don’t want to damage trust. It can also trigger defensiveness or blame-shifting.
How to Approach It: Lead with impact, not blame. Use “what happened?” energy instead of “how could you...” Keep it specific, brief, and framed around team outcomes. Don’t get personal and not accusatory.
Opening the Conversation: “Rohan, I wanted to follow up on [project/task]. We didn’t get the estimates on time, and that created a rush for the rest of the team. Can you walk me through what happened from your side?”
If Rohan pushes back giving various reasons: “I hear you, and I know unexpected stuff comes up. But when we drop deadlines without flagging it, it leaves others exposed. I’m less worried about the delay, more about how we flag and recover from it. Let’s build a habit of raising the flag earlier next time.”
Likely Result: You reinforce a culture of accountability without playing the blame game. Over time, this builds a team that flags risks early instead of covering their tracks late.
Example 2: Responding to a Mistake That Cost the Company Money or Trust
Scenario: A team member made a real mistake, something that had visible consequences: lost revenue, a blown client deadline, a broken promise.
Why it’s Difficult: You’re balancing accountability and empathy They probably already feel awful. You still have to clean up the mess. You don’t want to scare them into hiding future mistakes.
How to Approach It: Start with acknowledgment, then move into root cause and forward motion. Avoid shame spirals and focus on learning loops. Separate the person from the problem.
Opening the Conversation: “Hey, I know the [X mistake] situation sucked — for you, for the team, and for the client. I’m not here to pile on. I do want to understand what happened, how we got here, and what we can do to make sure we don’t repeat it.
If They Push Back: “I get that you didn’t intend for it to happen. I’m not questioning your work ethic, just trying to make sure we learn from this instead of dancing around it. What feels fair and constructive as a next step?
Likely Result: You preserve trust while still making clear that mistakes have consequences. You also build a culture where problems get solved, and not swept under the rug.
Example 3: Mediating Conflict Between Teammates
Scenario: Two people on your team are butting heads. Maybe it’s open tension, maybe it’s quiet weirdness - either way, it’s messing with the vibe and slowing things down.
Why it’s Difficult: You weren’t there for every exchange. You risk making it worse if you choose sides (or seem like you are).
They might be super different communicators.
You probably have a million other things to do.
How to Approach It: Use the triangle model: hear each side separately, then bring them together with clear guardrails. Focus on behavior, not personality. Your goal isn’t to make them friends — just functional collaborators
Opening The Conversation (in a one-to-one situation): “I’ve been picking up on some friction between you and [Name], and I wanted to check in. I’m not here to take sides - I just want to understand what’s been tough, and what you’d need to work better together.
Opening The Conversation ( both parties together): “Thanks for being open to this. The goal here isn’t to rehash every detail, but to figure out how we move forward productively. Let’s focus on what’s getting in the way of collaboration and what clear agreements we can set for working together.
If They Push Back: “I totally get that you may see things differently. My job isn’t to be a judge, but to make sure this team is functional. We don’t need total agreement, but we do need a baseline of respect and responsiveness.
Likely Result: You turn tension into clarity and show your team that conflict doesn’t have to fester. Even a semi-resolution can free up a lot of energy.
Source: The hustle
|
|
|
|
