How to Give Feedback Without Triggering Defensiveness
“Can I give you some feedback?”
Six words, and you can watch the shoulders rise. Whatever comes next now has to clear a wall that wasn’t there ten seconds ago. So most leaders adapt in one of two ways: they soften the message until it says nothing, or they sharpen it until it leaves a mark. One protects the relationship and wastes the moment; the other spends the relationship to win the moment.
There’s a third option, and it isn’t about being nicer or tougher. It’s about changing what the feedback points at.
Why feedback lands like a threat
Being evaluated by someone who matters to your livelihood registers, to the brain, as a safety question before it registers as information. The listener’s first unspoken question isn’t “is this useful?”, it’s “am I okay?” Until that question is answered, very little gets through.
Vague feedback keeps the safety question open. “Your communication needs work” could mean anything from one rambling email to “we’re documenting a case against you.” The listener’s brain fills that gap, and under pressure, brains fill gaps with the worst available version, then defend against it. The defensiveness you’re seeing is usually your own vagueness, reflected back.
Four feedback habits that backfire
The sandwich. Praise, criticism, praise. People decode it within two uses, after that, every compliment makes them brace, and your genuine praise stops being believable.
The drive-by. “Hey, quick thing, that deck was a mess. Anyway, good weekend?” No context, no time to respond, maximum residue.
Always and never. “You always run long.” One word turns an example into an indictment, and invites the listener to find the single counterexample instead of hearing the point.
The mind-read. “You clearly don’t care about this project.” Assigning motive forces people to defend who they are, the conversation is now about their character, not Tuesday’s deck.
Notice what these have in common: they all aim feedback at the person. Identity gets defended. Events get examined. That’s the whole trick.
The four-line pattern
Not a script, scripts sound like scripts. A pattern you can refill every time:
Context. “In Tuesday’s client call…”, one line that puts you both in the same scene.
Observation. “…when the pricing question came up, you answered before Maya finished her recommendation…”, the camera test: if a camera couldn’t have recorded it, it doesn’t belong in this line.
Impact. “…the client heard two different answers, and Maya went quiet for the rest of the call.”, consequences, stated plainly, no adjectives required.
Question. “What was happening from your side?”, and then silence. This line does the heavy lifting: it treats them as the expert on their own behavior and turns a verdict into a working session.
Four lines. The person hears exactly what happened, exactly what it caused, and gets the next word. There’s nothing to defend against, because nothing attacked.
When the pushback comes anyway
Sometimes it still comes, “the client was stalling, someone had to answer.” Don’t re-argue the observation. Get curious one more time: “Tell me more about that.” You’ll either learn context that changes your read, or they’ll talk their way to the impact themselves. Either way, two rounds of listening beat one round of insisting, and you only earn the right to return to the impact after they feel heard on the facts. (Listening well is its own skill: Beyond Active Listening.)
Make it normal, not an event
Feedback that arrives once a quarter feels like a verdict no matter how well it’s built. The four-line pattern is small enough to use weekly, in one-on-ones, after meetings, in the hallway. Frequency is what changes the meaning of “can I give you some feedback?” from a threat to a habit. Teams that hear specific, observable feedback often stop bracing, because the safety question is already answered.
And when the feedback conversation is a bigger one, performance, conflict, a pattern that has to change, start here: Why Difficult Conversations Go Sideways.
This week
Take the one piece of feedback you’ve been sitting on. Run it through the four lines, context, observation, impact, question. Check the observation against the camera test. Then deliver it within 48 hours, and let the question do its work.
Change the pattern. Change the conversation.
Want this to be how your whole team communicates? Barbara builds the four-line pattern, and the listening that powers it, into teams through hands-on workshops. Explore Workshops, or start with a conversation: Let’s Talk.
FAQ
Why do employees get defensive when given feedback?
Because evaluation by someone with power over your work registers as a safety question first. Vague or judgment-led feedback keeps that question open, so the brain defends. Feedback aimed at observable events, not identity or motive, closes the safety question and gets examined instead of defended.
What is a simple framework for giving feedback to an employee?
Four lines: context (“In Tuesday’s call…”), an observation a camera could have recorded, the plain impact, and one curious question (“What was happening from your side?”). It works because it gives the listener facts to work with and the next word.
Should I use the feedback sandwich?
No. People decode it quickly, and then your praise stops being believable, they brace every time a compliment starts. Separate praise from corrective feedback entirely; give each its own moment and both get stronger.
How often should leaders give feedback?
Weekly beats quarterly. Small, specific, observable feedback delivered close to the event feels like coaching; saved-up feedback delivered at review time feels like a verdict. Frequency, not softness, is what makes feedback feel safe.
