How to give feedback to an employee who gets defensive
Name one thing you saw, say what it caused, then stop talking and ask for their side. When they push back, don't argue the facts: acknowledge the feeling in one sentence, restate the one thing, and ask what they need to change it. Most defensive talks go wrong because the manager says too much, too vaguely, too late.
This guide is for the manager who already tried once and got "That's not fair," crossed arms, tears or a long list of reasons. Below: why people get defensive, how to prepare in 15 minutes, the words to open with, exact replies to the six most common pushbacks, what to do after, and when it stops being a feedback problem.
Why do employees get defensive about feedback?
Defensiveness is a reaction to threat, and feedback can threaten three different things. Douglas Stone and Sheila Heen, who teach negotiation at Harvard Law School, sort these into three triggers in their book Thanks for the Feedback:
- Truth triggers. The feedback feels wrong or unfair. "I wasn't late, the bus was." The person argues the facts.
- Relationship triggers. The feedback is fine, but who it comes from isn't. "You were doing the same thing six months ago." This one hits new managers hardest, because the person giving feedback used to be a peer.
- Identity triggers. The feedback shakes how the person sees themselves. "I'm good at my job" meets "your reports are late," and it feels like an attack on who they are.
Knowing which trigger fired tells you what to say next. A truth trigger needs specifics. A relationship trigger needs you to own the change in roles. An identity trigger needs you to separate the one behavior from the whole person.
There are also reasons that sit with the manager, and they are worth checking first:
- The feedback is vague ("be more of a team player"), so the person fills the gap with the worst meaning.
- It arrives in a stack: three months of saved-up problems in one meeting.
- It comes in front of others, or by chat, where tone gets lost.
- It's the only kind of feedback they get from you. If every talk with you is a correction, every talk feels like a threat.
How to prepare (15 minutes, the day before)
The preparation is where most of the work happens. Write these five lines down before you book the meeting:
- The one behavior. Something a camera could record. "Sent the client update two days after the deadline" passes. "Doesn't care about deadlines" fails.
- When and where. The date and the setting. "Last Tuesday, the Henley update."
- The impact. What it caused for the team, the customer or you. "The client called me asking where it was, and I didn't have an answer."
- What good looks like. The exact change you want. "If an update will be late, tell me and the client the day before."
- The trigger you expect. If you know this person argues facts, bring the dates. If you used to be peers, plan your one line about it.
Lines 1 to 3 are the Situation-Behavior-Impact model from the Center for Creative Leadership. It works because it keeps you on what happened and off what you think it says about the person. Line 4 is what most managers leave out, and without it the employee leaves knowing they did wrong but not what right looks like.
Then cut it to one issue. If you have three, pick the one with the biggest impact and save the others. One issue gets fixed. Three issues get defended.
When and where to give it
| Choose | Avoid | Why |
|---|---|---|
| Private, in person or on video | Chat, email, in front of the team | They can see your face and you can see theirs. An audience makes saving face the goal. |
| Within a few days of the event | Weeks later, or saved for the review | Fresh memories mean fewer arguments about facts. |
| Early in their day or in your regular 1:1 | Friday at 5, right before a shift, right after a bad call | They need time to think afterward, and not a customer waiting. |
| After the heat of the moment | While either of you is still upset | A cooled-down talk is about the work, not the fight. |
If you already have a weekly one-on-one, use it. Feedback inside a regular meeting feels routine. A surprise "can we talk in my office" invite raises the threat level before you say a word. (If you don't have them yet, here's how to have an effective 1 on 1.)
The opening: what to say in the first minute
Keep the opening short. A long warm-up makes people brace, and the "compliment, criticism, compliment" sandwich teaches them that praise from you means bad news is coming. Say why you're there, then say the thing.
"I want to talk about the Henley update. It went out Thursday; the deadline was Tuesday. The client called me Wednesday asking for it and I didn't have an answer for them."
"I'd like to hear what happened on your end."
Then stop. Count to five in your head if you need to. The silence is where they start thinking instead of defending. Don't fill it with softeners ("it's not a big deal, but…") that make the message unclear.
For a former peer, add one line that names the change, once:
"This is part of my job now, and it feels a bit strange to me too. I'd rather tell you straight than have it come up some other way."
What to say when they push back: six common replies
The rule for every reply below: acknowledge in one sentence, don't debate, come back to the one behavior and the change. You are not trying to win the argument. You are trying to get one thing to change.
1. "That's not fair." / "That's not what happened."
A truth trigger. Don't defend your whole account. Ask for theirs and look for the part you both agree on.
"Tell me what I'm missing." (Listen.) "Okay, the data came late from finance. That's useful. The part I need to change is that I didn't know it would be late. Next time, can you flag it the day before?"
If they give you a fact you didn't have, say so. Being willing to be wrong on a detail makes the main point easier to hear.
2. "Everyone else does it too."
"If others are doing it, I'll talk to them. Right now I'm talking with you about yours."
Then actually check. If it really is the whole team, the problem may be your unclear standard, and the fix is a team-wide expectation, not one person's correction.
3. "You used to do the same thing."
The relationship trigger. Agree with what's true and keep going.
"You're right, I did. I see the cost of it more clearly from this seat. I'm asking because it affects the client, not because I'm better at it."
4. A long list of reasons
Workload, unclear instructions, a broken tool. Some reasons are real problems you need to fix. Separate them.
"Some of that is on me. Let's fix the reporting tool this week. And with the tool as it is, I still need a heads-up when a deadline will slip."
5. Silence, or "Fine. Whatever you say."
Quiet agreement often means they've checked out, not that they agree. Ask a question that needs a real answer.
"I don't want you to just agree with me. What would make that heads-up hard to do?"
6. Tears or anger
Pause the content, not the meeting. Offer water or a few minutes. Don't take the feedback back to make the feeling stop.
"I can see this is landing hard. Do you want a few minutes, or would you rather pick this up tomorrow morning? Either is fine. It's still something we need to sort out."
If someone raises their voice, lower yours and slow down. If it turns into shouting or threats, end the meeting calmly and talk to HR before the next one.
How to end the conversation
Every feedback talk should end with three things said out loud:
- The change, in their words. Ask: "So what will you do differently next time?" When they say it, they own it. When you say it, they hear it.
- What you'll do. Any fix you promised: the tool, the clearer brief, the earlier deadline from finance.
- When you'll check in. "Let's look at this again in our 1:1 on the 14th."
Then end on something true about the person's place on the team, not a fake compliment. "You're the person clients ask for. I want the deadlines to match that."
After the talk: the next two weeks
| When | What to do |
|---|---|
| Same day | Write three lines for yourself: the date, the behavior you raised, what they agreed to. Keep it factual. If your company has a system for notes, use it. |
| Next 1–3 days | Act normal. Say hello, include them in the usual things. People often expect to be frozen out after feedback; a normal day shows the talk was about one thing. |
| First time they get it right | Say so, specifically, within a day. "You flagged the Monroe delay on Monday. That let me warn the client. Thank you." Praise for the new behavior is what makes it stick. |
| Check-in date | Raise it briefly in the 1:1, even if it's going well. "How's the heads-up working?" |
When it happens again
One talk rarely changes a habit. Jacob Kaplan-Moss, an engineering leader who writes about management, suggests expecting to give the same feedback several times before it lands. That's normal. What changes is how direct you are each time.
- Second time: name that it's a repeat. "We talked about this on the 3rd. It happened again with the Price report. What got in the way?"
- Third time: name the stakes. "This is the third time. I need it to stop, and if it doesn't, it becomes a formal performance issue. I don't want that. What do you need from me so it doesn't get there?"
- After that: talk to your manager or HR about your company's process before the next conversation. Bring your notes. Our guide to difficult conversations with employees lists when it becomes HR's conversation.
The defensiveness itself can also become the issue. If someone can't hear any correction without a fight, give feedback on that, with the same model: "In our last three talks, when I raised a problem, the conversation turned to why I was wrong to raise it. That makes it hard for me to help you. Can we figure out a better way for me to bring things up?"
Mistakes that make defensiveness worse
- Labels instead of behavior. "You have an attitude problem" can only be denied. "You rolled your eyes when Sam presented" can be discussed.
- "Always" and "never." They will find the one exception and the talk becomes about that.
- Speaking for others. "People have been saying…" makes them hunt for who, not fix what. Speak to what you saw.
- Asking "why did you…" It sounds like an accusation. "What happened with…" invites the story.
- Backing down. Taking the feedback back to end the discomfort teaches them that pushing back works.
- Only correcting. If the only time you give feedback is when something is wrong, every talk feels like a threat. Specific praise on ordinary days makes the hard talks easier.
A one-page script you can use tomorrow
Open: "I want to talk about [situation]. [Behavior]. It meant [impact]."
Ask: "What happened on your end?" (Then be quiet.)
If they push back: "I hear you. [One sentence on what's fair in what they said.] The part I need to change is [behavior]."
Ask for the change: "What would you do differently next time?"
Close: "I'll [your part]. Let's check in on [date]."
If you want to know which part of this is hardest for you, the opening, the silence or holding the line, our free 2-minute leadership style quiz names your style and the conversations it tends to dodge. You can also read a full sample lesson on running your first 1:1, the meeting where most feedback should happen.
Questions managers ask
Should I use the feedback sandwich with a defensive employee?
Usually no. People learn the pattern fast, so the opening praise makes them brace and the closing praise sounds forced. Say the issue clearly, and give praise separately, when it's earned and specific.
Should I give feedback by email to avoid a scene?
Not for a first conversation. Email strips out tone, and the person rereads it alone and gets more upset. Talk first, then send a short written recap of what you agreed if your company expects records.
What if they say I'm targeting them?
Take it seriously and stay on facts. "I'd want to know if it felt that way. Here's what I raised and why. If you think I'm treating you differently from others, tell me how, and you can also raise it with HR." Then make sure your standards really are the same for everyone.
How do I give feedback to someone older or more experienced than me?
Lean on their experience for the solution, and keep the behavior and impact as clear as with anyone else. "You know this client better than anyone. The update was two days late and they called me. How would you handle a slip like that next time?"
When should I involve HR?
Before any formal warning, if the person makes a complaint about you or someone else, if the conversation includes threats or discrimination, or if the behavior is a conduct or safety issue rather than a performance one. This guide covers everyday feedback; your company's policy and HR decide formal steps.
How long until a defensive employee changes?
It varies. Watch for the next chance to do the new behavior, then praise it the first time it happens. If nothing has changed after two or three clear, documented conversations, it's a performance issue to handle with your company's process.
Your next step: take the free leadership style quiz to see the conversations you're most likely to put off, and browse all our guides for new managers.
Sources
- Douglas Stone and Sheila Heen, Thanks for the Feedback: The Science and Art of Receiving Feedback Well, Viking, 2014 (truth, relationship and identity triggers).
- Center for Creative Leadership, the Situation-Behavior-Impact (SBI) feedback model, summarized by Mind Tools: https://prime.mindtools.com/pages/article/situation-behavior-impact-feedback.htm
- Jacob Kaplan-Moss, on addressing defensiveness, jacobian.org, March 2021: https://jacobian.org/2021/mar/23/addressing-defensiveness/