Why You Keep Putting It Off
You’ve drafted the email three times and deleted it. You’ve told yourself you’ll bring it up after the next project wraps. You’ve convinced yourself it’s not that bad, or that the person will figure it out on their own.
You’re not alone. Most managers — new and experienced alike — have a performance conversation they’ve been sitting on for too long. Not because they don’t care, but because they care too much about getting it wrong. They’re afraid of damaging the relationship, triggering a defensive reaction, or saying something that makes things worse instead of better.
The problem is that delay has a cost. The employee doesn’t improve because they don’t know there’s a problem. The rest of the team notices and wonders why you’re not doing anything. And every week that passes makes the conversation harder to start, because now you also have to explain why you waited.
This article will walk you through exactly how to have the performance conversation you’ve been avoiding — from preparation to follow-through.
Get Clear on What You’re Actually Dealing With
Before you say a single word to the employee, you need to be precise about what the issue is. Vague discomfort is not a performance problem. “Something feels off” is not feedback.
Ask yourself these questions:
- What specific behavior or output is the problem? Name it in concrete terms. “Deadlines are being missed” is specific. “Attitude issues” is not.
- How often is it happening? Once might be a bad week. A pattern is a performance issue.
- What is the impact? On the team, on the work, on customers, on you. Impact is what makes the conversation necessary.
- Do they know this is a problem? Have you ever told them directly? If not, this first conversation is about clarity, not consequences.
Write it down. If you can’t put it in writing in clear, factual language, you’re not ready to have the conversation yet. Keep working until you can.
Separate the Story from the Facts
One of the most common mistakes managers make is walking into a performance conversation with a narrative already built — “she doesn’t care,” “he’s checked out,” “they’re not cut out for this role.” These interpretations feel true, but they aren’t facts, and if they come out in the conversation, they will put the employee immediately on the defensive.
Stick to observable, documented facts:
- Fact: “The last three reports were submitted after the deadline.”
- Story: “You don’t take your responsibilities seriously.”
- Fact: “In the last two team meetings, you didn’t contribute when I asked for input.”
- Story: “You’ve disengaged from the team.”
Lead with facts. Save your interpretation for a question, not a statement: “I’ve noticed X. Help me understand what’s been going on.” This keeps the conversation open rather than triggering a defense.
Plan the Conversation — But Don’t Script It
You should know your opening line before you sit down. That’s not the same as writing a script and reading from it. Scripts make you sound rehearsed and kill the natural back-and-forth that makes these conversations productive.
Plan for three things:
1. Your opening
Get to the point quickly. Don’t open with small talk and then blindside them. Don’t bury the issue in a wall of positive feedback (the classic “feedback sandwich” usually just confuses people about what the actual message is). Be direct and human:
“I want to talk about something I’ve been observing, and I want to make sure we’re on the same page about it.”
Then state the specific behavior and its impact in one or two sentences.
2. A genuine question
After you’ve stated the issue, stop talking and ask something real. Not a rhetorical question — an actual invitation for them to respond. “What’s your take on this?” or “Is there something going on that I’m not aware of?” gives them a chance to provide context you might not have.
Sometimes there’s a good reason. A family situation, a workload problem, unclear expectations, a tool that’s broken. You won’t know unless you ask. And if it turns out the problem is partly yours to fix, you need to know that too.
3. A clear ask for what changes
The conversation needs to end with a shared understanding of what needs to be different, and by when. This is where a lot of managers get vague because they’re conflict-averse. Resist the urge. Be specific:
“Going forward, I need reports submitted by the Thursday deadline, without exception. If something is going to prevent that, I need to hear from you before the deadline, not after.”
Vague asks produce vague results. Specific asks give the person something to actually do differently.
Choose the Right Setting
Have this conversation in private, in person when possible, and at a time when neither of you is rushing to something else. Don’t have it right before a big meeting, at the end of a Friday, or in a shared workspace where people can overhear.
If you’re managing remotely, a video call is better than a phone call — you need to be able to see each other. Block at least 30 minutes, even if you expect it to be shorter. Running out of time before resolution is worse than having no conversation at all.
Don’t announce the meeting in a way that sends the employee into a spiral of anxiety. You don’t need to tell them in advance that it’s a performance conversation. “I’d like to connect one-on-one this week — do you have time Thursday?” is enough.
During the Conversation: What to Do When It Gets Hard
Even when you’ve prepared well, these conversations can go sideways. Here’s how to handle the most common difficult moments.
They get defensive
Don’t match their energy. Stay calm and don’t back away from the core message. Acknowledge their reaction: “I understand this is hard to hear.” Then return to the facts: “What I know is that X has happened, and that’s what I need to address.”
They cry
Pause. Let them collect themselves. Don’t apologize for having the conversation — apologizing signals that you did something wrong by raising it. You can say: “Take a moment. I’m not going anywhere.” Then continue once they’re ready.
They have a reasonable explanation you hadn’t considered
This is good news. Adjust accordingly. If they tell you the deadline is impossible because of a dependency that was outside their control, acknowledge it: “That’s useful context. Let’s talk about how to fix that going forward.” You can still address the behavior while also acknowledging the system problem.
They push back and say the problem isn’t real
Stay grounded in your documentation. “I hear that you see it differently. Here’s what I’ve observed: [specific examples]. That’s what I need to work through with you.” Don’t debate whether the problem exists. State clearly that it does and move toward solutions.
Follow Up in Writing
After the conversation, send a brief follow-up by email or message — not a formal write-up, just a clear summary. This does two things: it removes any ambiguity about what was agreed to, and it creates a record if you need to escalate later.
Keep it factual and forward-looking:
“Thanks for talking with me today. As we discussed, the key thing I’m asking for going forward is [specific change]. Let’s check in again in two weeks to see how it’s going. My door is open if anything comes up in the meantime.”
This isn’t about building a paper trail to fire someone. It’s about making expectations clear and showing that you’re taking the conversation seriously enough to document it.
Don’t Confuse Having the Conversation with Solving the Problem
One conversation rarely fixes a performance issue. The conversation opens the door. What happens next is where things either improve or escalate.
Schedule a follow-up. Check in proactively. Notice and acknowledge when things improve — a lot of managers give feedback when things go wrong but forget to close the loop when things go right. If you told someone their reports needed to be on time and they’ve been on time for three weeks, say something: “I’ve noticed the reports have been in on time. I appreciate you making that change.”
If things don’t improve after a direct conversation and a reasonable amount of time, that’s when you move to more formal steps — documented expectations, a performance improvement plan, involvement from HR. But you have to have the direct conversation first. You cannot skip to consequences without first giving someone a clear chance to correct.
The Conversation Is Part of Your Job
This is the part no one tells you clearly enough when you become a manager: having hard conversations is not an optional add-on to your role. It is one of the core responsibilities of managing people. When you avoid it, you’re not being kind — you’re prioritizing your own comfort over the employee’s chance to improve and the team’s right to a functional environment.
The managers people respect most are not the ones who never say anything difficult. They’re the ones who say difficult things clearly, calmly, and early — before the problem gets entrenched.
The conversation you’ve been avoiding is probably not as bad as you’ve made it in your head. Most people, when approached with respect and specificity, respond better than managers expect. And even when they don’t, you’ll be in a better position than if you’d said nothing.
Stop waiting for the right moment. Prepare, pick a time, and have it. That’s what your team needs from you.
Frequently Asked Questions
Why do managers avoid having difficult performance conversations with employees?
Managers typically avoid performance conversations because they fear damaging relationships, triggering defensive reactions, or making situations worse. They often care too much about getting it wrong rather than not caring at all. This avoidance stems from wanting to protect both the employee and the working relationship, but ironically creates bigger problems over time.
How do I know if something is actually a performance issue or just my perception?
A real performance issue involves specific, measurable behaviors or outputs that you can document in clear, factual language. Ask yourself: What exactly is the problem, how often does it happen, and what’s the measurable impact on the team or work? If you can’t write it down in concrete terms without using vague phrases like ‘attitude issues,’ you’re not ready for the conversation yet.
What’s the difference between facts and assumptions when addressing employee performance?
Facts are observable, measurable behaviors like ‘missed three project deadlines this month,’ while assumptions are interpretations like ‘she doesn’t care’ or ‘he’s checked out.’ Managers often create narratives about why performance issues exist, but leading with these interpretations in conversations immediately puts employees on the defensive. Stick to documented facts and let the employee explain the context.
How long should I wait before having a performance conversation with an underperforming employee?
You shouldn’t wait once you’ve identified a clear pattern of performance issues with measurable impact. While a single incident might be a bad week, repeated problems need immediate attention. Delaying makes the conversation harder because you’ll also need to explain why you waited, and the employee misses opportunities to improve.
What should I prepare before having a difficult conversation with an employee about their performance?
Write down specific behaviors or outputs that are problematic, document how often they occur, and clearly identify the impact on the team or work. Determine whether the employee knows this is a problem – if you’ve never told them directly, this should be a clarity conversation, not a consequences discussion. Separate observable facts from your interpretations about their motivations or attitude.