There’s a conversation you’ve been avoiding. You know the one. Maybe it’s the team member who’s consistently underperforming. The two people who can’t stop sniping at each other. The project that’s failing and someone needs to hear it. The person who asked for a promotion you can’t give.
You keep telling yourself you’ll handle it next week. Or that it’ll resolve itself. Or that it’s not that bad yet.
It won’t resolve itself. And the longer you wait, the harder it gets.
I avoided my first difficult conversation for six weeks. By the time I finally had it, a small performance issue had become a team-wide morale problem. I learned the hard way: the cost of avoiding a difficult conversation is always higher than the cost of having one.
This guide is about having those conversations well — not perfectly, but well enough that things actually improve. Whether you call it a crucial conversations framework or just “that talk I’ve been dreading,” the principles are the same.
Why We Avoid Them (And Why That’s Normal)
Let’s be honest about what’s really going on. You’re not avoiding the conversation because you’re lazy. You’re avoiding it because:
- You’re afraid of conflict. Most people are. We’re wired to avoid confrontation.
- You don’t want to hurt someone. You’re a decent human being. Telling someone they’re falling short feels cruel — especially if you were recently their colleague.
- You’re not sure you’re right. What if you’re overreacting? What if there’s context you’re missing?
- You don’t know how. Nobody taught you this. You’ve never done it before.
- You want to be liked. Especially as a new manager, you’re still building relationships. A hard conversation feels like a threat to that.
All of these feelings are valid. None of them are reasons to avoid the conversation.
Here’s the reframe: a difficult conversation is an act of respect. You’re treating someone like an adult. You’re giving them information they need to succeed. You’re investing in the relationship, not damaging it.
The managers people respect most aren’t the ones who avoid hard truths. They’re the ones who deliver them with honesty and care.
The Preparation Framework
The conversation itself is 20 minutes. Preparing for tough talks with employees is what makes or breaks it. As Harvard’s research on difficult workplace conversations shows, the outcome is largely decided before anyone opens their mouth.
Step 1: Get Clear on the Facts
Before anything else, separate what happened from how you feel about it.
Facts (observable, specific):
- “The last three deliverables were submitted after the deadline.”
- “In the team meeting on Tuesday, you interrupted Sarah twice.”
- “The client reported two bugs that weren’t caught in testing.”
Not facts (interpretations, feelings, labels):
- “You don’t care about deadlines.”
- “You’re disrespectful to Sarah.”
- “You’re being sloppy.”
Write down the facts. If you can’t point to specific, observable behaviors — you’re not ready for the conversation yet.
Step 2: Identify Your Desired Outcome
What do you actually want from this conversation? Be specific:
- “I want late deliverables to stop.”
- “I want the team conflict resolved so we can collaborate effectively.”
- “I want this person to understand the impact of their behavior and commit to a change.”
What you’re not trying to do:
- Win an argument
- Make someone feel bad
- Prove you’re right
- Vent your frustration
If your primary motivation is any of the above, wait until you’ve cooled down.
Step 3: Consider Their Perspective
Before you walk in, spend five minutes thinking:
- What might they say? What’s their side of this?
- Is there context I might be missing?
- How might they be feeling right now?
- What do they need from me to hear this?
This isn’t about making excuses for the behavior. It’s about entering the conversation with curiosity instead of judgment — what the Harvard Negotiation Project calls moving from certainty to curiosity. That changes everything — your tone, your body language, your willingness to listen.
Step 4: Choose the Right Time and Place
- Private. Always. No exceptions. Never in front of others.
- In person (or video call) when possible. Never by email or Slack for anything sensitive.
- Enough time. Don’t squeeze it into 10 minutes between meetings. Block 30 minutes minimum.
- Not on Friday afternoon. Give them time to process and come back to you with questions.
- Not when you’re angry. Cool down first. A conversation driven by frustration rarely goes well.
The Conversation: A Step-by-Step Structure
Opening: Name It (30 seconds)
Don’t bury the topic in small talk. The other person can feel something’s off, and the small talk just increases their anxiety.
Say something like:
“Thanks for meeting with me. I want to talk about something that’s important, and I want to be direct with you because I respect you.”
Or simply:
“I need to talk about [topic]. I’d rather be upfront than let it linger.”
This does three things: it signals that this is serious, it establishes respect, and it removes the guessing game.
State the Facts (1-2 minutes)
Deliver the specific, observable facts you prepared. No editorializing.
Example:
“In the last three sprints, your deliverables have come in 2-3 days past deadline. The most recent one — the API integration — was four days late, which pushed the client demo back.”
Not:
“You’ve been really unreliable lately, and it’s becoming a problem.”
See the difference? The first version is specific and factual. The second is a character judgment that will immediately trigger defensiveness.
Share the Impact (30 seconds)
Explain why this matters. Connect the behavior to real consequences.
“When deliverables are late, the rest of the team can’t start their work on time. It also puts our credibility with the client at risk — they’ve mentioned it in the last two check-ins.”
Impact isn’t about making someone feel guilty. It’s about addressing performance issues directly while helping them understand the why behind the conversation. People change behavior when they understand consequences, not when they’re told to.
Pause and Listen (5-10 minutes)
This is the hardest part. And the most important.
After you’ve stated the facts and impact, stop talking. Ask an open question:
“I’d like to hear your perspective. What’s going on?”
Then actually listen. Not the “waiting for my turn to talk” kind of listening. Real listening.
You might learn:
- They’re dealing with a personal crisis you didn’t know about
- They’re stuck on a technical problem and were too embarrassed to ask for help
- They have a different understanding of the priorities
- They didn’t realize the impact of their behavior
Whatever they say, resist the urge to immediately counter or solve. De-escalation techniques for managers come down to this: let them talk. Acknowledge what they share:
“I didn’t know that. Thank you for telling me.”
“I can see how that would make things difficult.”
“That makes sense. I appreciate you being honest.”
Find the Path Forward (5 minutes)
Now you co-create a solution. The key word is co-create — don’t just dictate what needs to happen.
“So knowing all this, what do you think we can do to get the deliverables back on track?”
Let them propose solutions first. People commit more to plans they helped create.
If their proposal is enough, great. If not, add to it:
“I like that idea. Can we also agree on [specific action]? That would give me confidence we’re on the same page.”
Make the agreement concrete:
- What will change?
- By when?
- How will we measure it?
- When will we check in on progress?
Close with Support (1 minute)
End the conversation with genuine care:
“I know this wasn’t an easy conversation. I brought it up because I believe in your potential and I want to see you succeed. How can I support you?”
This isn’t soft. It’s strategic. A person who leaves a hard conversation feeling supported will work to improve. A person who leaves feeling attacked — because you failed at managing emotional reactions at work — will disengage or start looking for another job.
Scripts for the 5 Most Common Difficult Conversations
1. Underperformance
“I want to talk about your recent work on [project]. In the last [timeframe], I’ve noticed [specific facts]. The impact is [consequences]. I know you’re capable of more — I’ve seen it in [positive example]. What’s getting in the way, and how can we get things back on track?“
2. Interpersonal Conflict Between Team Members
For a full playbook on mediating these situations, see our guide on how to handle conflict between team members.
“I’ve noticed some tension between you and [person]. In [specific situation], [what happened]. It’s affecting the team — people are uncomfortable and it’s slowing collaboration. I’d like to understand your perspective. What’s going on from your side?“
3. Delivering Bad News (No Promotion, No Raise, Project Canceled)
“I want to be straight with you. I know you were hoping for [promotion/raise/outcome]. The decision is [what it is], and here’s why: [honest reason]. I understand this is disappointing, and I want to talk about what we can do to get you there in the future.”
4. Behavioral Issue (Attitude, Communication Style)
“There’s something I need to share with you, and I’m telling you because I want you to succeed here. In [recent situation], when you [specific behavior], the impact was [what happened]. I don’t think that was your intention, but the effect on [person/team] was real. Can we talk about what happened?“
5. Someone Is in the Wrong Role
“I want to have an honest conversation about your role. I’ve noticed that [specific observations — struggles, lack of engagement, mismatch]. I care about you being in a position where you can thrive. How are you feeling about your current work? Is this where you want to be?”
The Mistakes That Make Difficult Conversations Worse
The Sandwich Method
You’ve probably heard this: start with a compliment, deliver the criticism, end with a compliment. Please don’t do this.
It’s manipulative and transparent. After the first time, people learn to dread your compliments because they know a “but” is coming. It also dilutes both the praise and the feedback.
Instead: Be direct. People can handle honesty. They can’t handle wondering what you really think.
The Email Ambush
Never deliver difficult feedback over email, Slack, or text. Tone is impossible to read. The other person can’t ask questions. And you can’t see their reaction.
The rule: If it makes your stomach tight to write it, you should say it face-to-face.
The Vague Feedback
“You need to step up” or “I need you to be more professional” are not feedback. They’re conclusions without evidence. The person has no idea what to change.
Always include: What specifically happened, when, and what the impact was. Our guide on how to give feedback for the first time covers the SBI framework in detail.
The Monologue
If you talk for 10 minutes straight and then ask “Any questions?”, you haven’t had a conversation. You’ve delivered a lecture. And lectures don’t change behavior.
Aim for 50/50. You should be talking about half the time, listening the other half.
The “I Heard That You…”
Starting a conversation with secondhand information is a trust killer. If someone complained to you about a team member, don’t say “I heard that you…”. Either witness the behavior yourself or say “I’ve received feedback that…” and be prepared for them to ask from whom.
Waiting Too Long
Every week you wait, the conversation gets harder and the problem gets bigger. Small issues discussed early stay small. Small issues ignored for months become career-threatening.
The rule of thumb: If it’s bothering you for more than a week, it’s time to talk.
After the Conversation
The conversation is only the beginning. What you do next determines whether anything actually changes.
Follow Up in Writing
Within 24 hours, send a brief email or message:
“Thanks for the open conversation today. To make sure we’re aligned, here’s what we agreed on: [list of specific commitments]. Let’s check in on [date]. Let me know if I missed anything.”
This isn’t about creating a paper trail (though it helps). It’s about clarity and accountability — for both of you.
Check In When You Said You Would
If you agreed to follow up in two weeks, follow up in two weeks. Not three. Not “when things calm down.” Exactly when you said.
Missing a follow-up signals that the conversation wasn’t important. And if the conversation wasn’t important, why should they change?
Acknowledge Improvement
If you see progress, say so. Explicitly.
“I noticed the last two deliverables came in on time. That’s exactly the improvement I was hoping for. Thank you.”
People need to know that their effort is seen. Otherwise, why bother?
Know When to Escalate
Sometimes a difficult conversation doesn’t lead to change. You’ve been clear, you’ve listened, you’ve supported — and nothing improves.
That’s a different conversation. One about consequences: a performance improvement plan, a role change, or ultimately, letting someone go. Those are hard too. But you can have them with a clear conscience because you did the work first.
The Conversation You’re Avoiding Right Now
You know the one. You’ve been thinking about it while reading this article.
Here’s your next step: schedule it. Not “sometime this week.” Put it on the calendar. Tomorrow or the day after. 30 minutes. Private room.
Then prepare using the framework above. Write down the facts, the impact, and your desired outcome. Think about their perspective. And walk in with the belief that this conversation is an act of respect — for them and for your team.
It won’t be perfect. That’s fine. It just needs to be honest.
The first difficult conversation is the hardest one you’ll ever have. Every one after that gets a little easier. And your team will be better for it.