How to Give Feedback to a Direct Report Who Gets Defensive

The Trap Most New Managers Fall Into

You've given the feedback once. The person got visibly defensive — arms crossed, short answers, maybe a "well, actually" explaining why it wasn't really their fault. So the next time something similar happens, you soften the message. And the time after that, you soften it further, until what comes out of your mouth barely resembles the actual problem. Six months later you're surprised the behavior never changed, but you never actually told them clearly what needed to change.

Defensiveness from a direct report is uncomfortable, but caving to it doesn't protect the relationship — it just delays a harder conversation and lets a fixable problem calcify into a performance issue.

Separate the Observation From the Judgment

A lot of defensiveness gets triggered not by the feedback itself but by language that sounds like a verdict on someone's character rather than a description of a specific action. "You don't take ownership of your projects" is a judgment. "In the last two sprints, three tickets slipped past their deadline without a heads-up to me or the team" is an observation. The second version is much harder to argue with, because it's just what happened — and it gives the person something specific to respond to instead of something to defend themselves against.

Name the Defensiveness Without Escalating

If you can feel the conversation tipping into defense mode in real time, it's usually more effective to name it plainly than to plow through it. Something like: "I notice this might be landing as criticism of you as a person — that's not the intent. I want to solve the deadline problem, not relitigate the last two weeks." This resets the frame without accusing them of being defensive, which would just add another layer to defend.

Give Them Somewhere to Go

Feedback that only describes the problem and stops there tends to keep people stuck in the defensive posture, because there's nowhere else for the conversation to go except backward. Always pair the observation with a forward-looking question: "What would help you flag a slipping deadline earlier next time?" This moves the conversation from what went wrong to what happens next, which is usually where the defensiveness starts to drop.

Don't Let One Hard Conversation Be Your Only Data Point

A single difficult feedback conversation is easy for someone to write off as a bad day or a misunderstanding. A pattern is much harder to dismiss. This is where keeping specific, dated notes on behavior — not vague impressions — matters most: when you can say "this is the third time this quarter that a deadline slipped without a heads-up," you're no longer relying on the other person's memory of one uncomfortable meeting, and the conversation shifts from "he's being unfair" to "this is actually a pattern I need to address."

Follow Up Sooner Than Feels Necessary

The conversation isn't done when the meeting ends. A short check-in a week or two later — "how's the deadline tracking going since we talked?" — signals that the feedback was about solving a problem together, not scoring a point. It also gives you an early read on whether the behavior is actually shifting, instead of finding out at the next formal review that it wasn't.

Strivo helps with the pattern-tracking part specifically: logging a quick note right after a moment like this means that by the time you need to make the case — to the person, or to HR — you have specific, dated examples instead of a fuzzy sense that "this keeps happening."