When someone reacts defensively to feedback, slow down, ask what they understood, and check the specific event before repeating your conclusion. Acknowledge any missing context or mistake in your delivery. Then work toward a concrete action, support and follow-up.
You do not need them to agree with your interpretation of their personality. You need to understand what happened and decide what happens next. Calling them “defensive” in the middle of the exchange can create a second argument about the label.
Check your opening before choosing a comeback
If you said “Your attitude has been terrible lately,” the other person has a reasonable question: which behavior do you mean? If you surprised them publicly with a sensitive issue, the setting may be part of the problem.
The Center for Creative Leadership’s SBI approach describes the situation, observable behavior and impact. Its extension adds inquiry about intention. Asking is important: you cannot infer a person’s intention reliably from your impression of the impact.
Before pressing on, check:
- Can I name the event and what I actually observed?
- Was the expectation communicated?
- Am I reporting an impact, or predicting one?
- Have I given them a genuine chance to correct the facts?
For help with the opening itself, use giving feedback without sounding harsh. The examples below focus on what comes after it.
“That’s not what happened”
Treat this as a claim to investigate, not automatic resistance.
Manager: “The analysis arrived Friday rather than Tuesday. We had to compress the review.”
Employee: “That’s not fair. You changed the input file on Wednesday.”
Manager: “You’re right that I changed it. I hadn’t accounted for the rework. What did that add, and when did you realize Tuesday was no longer possible?”
Employee: “I thought the new file meant the deadline had moved too.”
Manager: “We left that unclear. Next time I’ll confirm the date when I change the brief. Can you flag any date assumptions at that point? Let’s reset this week’s plan now.”
This fictional exchange ends with responsibility on both sides. The manager corrects the premise rather than making the employee admit fault to finish the conversation.
If records differ, identify what you will check and when you will return. “I’ll check the timestamp and brief, then we can pick this up tomorrow” is more useful than debating uncertain memories indefinitely.
“So you think I’m bad at my job?”
Separate the issue from the broader judgment without making a reassurance you do not mean.
I’m talking about the three totals in this draft, not making a judgment about everything you do. I spent 25 minutes reconciling them before we could send it. How did you check the figures this time?Then listen. If the real issue is that the employee lacks access to the source, “be more careful” will not solve it. If they had the right inputs and skipped a check, discuss that check and the next handoff.
Avoid “Don’t take it personally.” It tells them how to feel without clarifying the concern. You can be respectful while still naming a legitimate standard.
“Everyone else does it”
There may be a wider problem worth addressing. Keep that possibility open while discussing this instance.
If the standard is inconsistent across the team, I need to address that. For this handoff, we agreed the source check would happen before sending. What got in the way? I’ll also review how we’re applying the standard more broadly.Do not promise team-wide follow-up and then ignore it. If the person identifies unequal treatment, investigate rather than using “we’re talking about you” to close the subject.
Silence, upset or a request for time
You do not know what silence means. Ask rather than narrating it for them:
“Would a minute help, or would you prefer to pick this up tomorrow morning? I want to leave room for your view.”
If you pause, make the next meeting specific. Send the factual example in advance if that helps them prepare. Urgent operational decisions may still need handling now; distinguish those from the longer feedback conversation.
If the exchange turns into personal attacks, you can set a limit: “I’m willing to discuss the feedback. I’m going to pause while we’re speaking to each other this way. Let’s return at 10 tomorrow.” Adapt the timing and support to the situation.
End with an agreement, not forced agreement about feelings
Write down the action, owner, support and check-in. If there is unresolved disagreement, record it accurately rather than claiming everyone agreed.
“For the next draft, you’ll reconcile the totals with the source sheet. I’ll make sure you have access today. We’ll review the process Friday. You still disagree with my account of Tuesday; I’ll check the version history before we finalize that point.”
CCL’s feedback guidance emphasizes preparation, specificity and listening, while recognizing that you cannot control whether someone likes or agrees with feedback. A script is a starting point, not a guarantee of a calm response.
For repeated performance concerns, another clever line may not be the next step. Clarify expectations, examine support and follow your organization’s process. See setting clear expectations. If you are the person receiving feedback, the relevant guide is responding to criticism.
For related practice in TalkCraft, find Give Hard Feedback Clearly → The Deflector. You choose between written replies and read the explanation for that fictional situation.
