How to Give Negative Feedback to Someone Who Reports to You

Your direct report made a mistake. Or they're underperforming. Or they did something that needs to be addressed, and it's your job to address it.

You know you need to have the conversation. You've been putting it off because it's uncomfortable, or because you're worried about their reaction, or because you're not sure exactly what to say.

The longer you wait, the worse it gets. The problem doesn't fix itself. Your resentment grows. Their performance doesn't improve because they don't know there's a problem. Eventually, you're either having the conversation in anger, or you're avoiding it until it becomes a firing situation.

Neither of those is good management.

Why This Conversation Feels Impossible

Most people avoid giving negative feedback because they're afraid of the emotional reaction. The employee might get defensive, or upset, or angry. They might cry. They might shut down.

All of that is possible. It's also not a reason to avoid the conversation.

The other fear is that you'll damage the relationship or destroy their morale. But here's what actually damages the relationship: letting someone continue doing something wrong without telling them, then holding it against them later.

If someone is failing and doesn't know it, that's on you, not them.

The Wrong Way to Give Negative Feedback

The most common mistake is the compliment sandwich. You say something nice, then deliver the criticism, then end with another compliment.

It doesn't work. The person leaves the conversation remembering the compliments and confused about whether there's actually a problem. Or they see right through it and feel patronized.

The other mistake is making it casual. "Hey, just a quick thing..." No. If the feedback matters enough to give, it matters enough to treat seriously. Schedule a real meeting. Don't ambush someone at their desk or in the hallway.

And don't deliver negative feedback in writing unless you absolutely have to. Email or Slack removes all context and tone. What you meant as straightforward reads as harsh. What you meant as serious reads as furious.

If you can have the conversation in person or over video, do that.

How to Structure the Conversation

Start with the specific issue. Not a general observation about their performance. Not a vague sense that something is off. The actual, concrete thing that needs to change.

"The report you submitted yesterday had three significant errors. I need to talk about what happened and how we prevent this going forward."

Not: "I feel like your work quality has been slipping lately."

The first version is clear. The second version is an opinion they can argue with.

Then, shut up and listen. Give them a chance to explain. Maybe there's context you're missing. Maybe there's a resource they need that they don't have. Maybe they didn't understand the expectations.

You're not obligated to accept every explanation as an excuse, but you should hear it.

Separating Intent From Impact

Here's where most managers get stuck. The employee didn't mean to do a bad job. They tried their best. They had good intentions.

None of that changes the impact.

You can acknowledge their intent while still addressing the impact. "I believe you worked hard on this. The result still didn't meet the standard we need, and we need to talk about why."

If you focus only on intent, you're letting them off the hook. If you dismiss intent entirely, you sound callous. You need both parts.

What to Do When They Get Defensive

They probably will get defensive. Most people do when receiving critical feedback.

They'll explain why it's not their fault. They'll point to extenuating circumstances. They'll mention all the things they did right. They'll compare themselves to other team members who they believe are doing worse.

Let them get it out. Don't interrupt. Don't argue with every point. Just listen.

When they're done, bring it back to the specific issue: "I understand there were challenges. Here's what I need to see change going forward."

If they keep arguing, you can say: "I'm not looking to debate whether this was a problem. It was. I'm trying to work with you on how we fix it."

That's not mean. It's clear. Clarity is kinder than letting someone think this is a negotiation when it's not.

Setting Clear Expectations for Improvement

The point of the feedback isn't to make them feel bad. It's to change behavior.

That means you need to tell them exactly what success looks like. Not "do better." Not "be more careful." Specific, measurable expectations.

"Going forward, I need you to double-check calculations before submitting reports. If you're unsure about something, ask me before the deadline, not after."

Or: "I need you to respond to client emails within 24 hours, even if the response is just acknowledging receipt and telling them when they'll get a full answer."

Whatever the issue is, they should leave the conversation knowing exactly what they need to do differently.

Documenting the Conversation

If this is part of a pattern, or if it's a serious issue, you need to document the conversation.

That doesn't mean you hand them a formal written warning in the moment. It means you send a follow-up email summarizing what you discussed and what the expectations are going forward.

"Thanks for meeting with me today. As we discussed, [specific issue]. Going forward, I need to see [specific change]. Let's check in on [date] to see how things are going."

This isn't about creating a paper trail to fire them later. It's about making sure you're both on the same page about what was said. Memories are unreliable. Writing it down removes ambiguity.

When the Feedback Is About Behavior, Not Work Product

Giving feedback about someone's work output is relatively straightforward. Giving feedback about how they interact with others is harder.

"Your reports are good, but you're condescending in meetings and it's creating problems with the team."

This conversation requires examples. You can't just say they're condescending and expect them to know what you mean. You need to point to specific things they said or did.

"In yesterday's meeting, when Sarah suggested the alternate approach, you said 'that's not how we do things here' in a tone that shut down the conversation. That's the kind of thing I'm talking about."

They might not realize they did it. They might think you're being overly sensitive. They might argue that you're misinterpreting their tone.

You're still the manager, and you still get to set the standard for how your team interacts. "Whether you intended it that way or not, it's affecting team dynamics. I need you to be more aware of how you come across."

Following Up

Don't give feedback and then never mention it again. Schedule a follow-up conversation to check on progress.

If things improved, acknowledge it. "I've noticed the reports have been much cleaner. Thank you for making that adjustment."

If things didn't improve, you have a different conversation: "We talked about [issue] two weeks ago. I'm still seeing the same problem. What's getting in the way of making this change?"

At some point, if the feedback isn't being implemented, you're moving from coaching to performance management. That's a different process. But you can't get there if you never gave clear feedback in the first place.

The Conversation That Goes Well

Most of the time, if you deliver feedback clearly and respectfully, the person will receive it fine. They might not love hearing it, but they'll understand it, and they'll work to improve.

The relationship won't be damaged. It might actually get stronger, because you've shown them you'll be direct instead of letting resentment build.

And if the relationship does get damaged because you gave them reasonable feedback in a respectful way, that tells you something important about whether this person can succeed in the role.

Clear Path helps you prepare for difficult feedback conversations with your direct reports. You'll get guidance on what to say, how to handle defensive reactions, and how to set expectations that actually lead to change.