How to Receive Feedback Without Getting Defensive

Most feedback advice is written for the person giving it: use SBI, be specific, be kind. Almost nothing is written for the person on the other end, even though receiving feedback well is the harder skill.

Here is what actually happens in your body when someone says "Can I give you some feedback?": your heart rate goes up, your attention narrows, and you start preparing a defense before they finish the sentence. That is not a character flaw. It is a normal threat response, and it happens to competent, secure, high-performing people just as often as anyone else.

The good news: you can learn to receive feedback well without pretending it does not sting. This guide gives you the framework, the scripts, and a way to practice before the next hard conversation lands in your lap.

Research on receiving feedback (most notably Douglas Stone and Sheila Heen's Thanks for the Feedback) identifies three separate triggers that can fire the moment feedback arrives — often at the same time, which is why it feels overwhelming.

Naming which trigger fired — even silently, in your head — is often enough to stop it from hijacking the conversation. "I notice I'm having an identity reaction right now" is a very different internal sentence than "this person is wrong about me."

A backend engineer (call him Kaan) got this message from his tech lead: "Your last three PRs took way longer to review than they should have — too much scope in one branch." Kaan's first internal reaction was: She thinks I'm slow. She's building a case against me.

He almost replied defensively. Instead, he waited an hour, then asked: "Can you walk me through one of the PRs? I want to understand what specifically made review harder." It turned out the tech lead had zero concerns about his speed — she just wanted smaller, reviewable diffs so bugs surfaced earlier.

Nothing about Kaan's competence was ever in question. His identity trigger had invented a story that was not in the feedback at all. One clarifying question replaced a week of quiet resentment with a two-minute alignment.

The first thing you say sets the entire tone of the conversation. Avoid these two extremes:

The middle path — curious, not defensive, not instantly agreeable: "Thanks for bringing this up. Can you give me a specific example so I understand exactly what you mean?" This buys you time, signals openness, and gets you the concrete detail you need to actually evaluate the feedback.

Once you have a concrete example, separate three things that are easy to blur together in the moment:

You can accept the impact was real ("I understand this caused a problem for you") without immediately accepting the interpretation ("I'm not sure 'careless' is the right word, but I hear that it caused real delay — let's fix that part"). That distinction alone prevents most feedback conversations from turning into arguments about character.

Sometimes feedback really is wrong, missing context, or delivered badly. You do not have to accept feedback just because someone gave it. But there is a difference between rejecting it in the moment (defensive, closes the door) and evaluating it honestly after you've actually understood it (confident, keeps the door open).

A useful script: "I want to make sure I understood — can you walk me through what led to this? I have some context I don't think I've shared yet." This gets your context on the table without dismissing theirs, and it often reveals that both sides were missing information.

For the next 7 days, every time you get feedback — big or small — do three things: name the trigger (truth, relationship, or identity) silently to yourself, ask one clarifying question before responding, and write down one thing you'll actually change.

By day 7, you'll likely notice the sting fades faster, the clarifying questions feel more natural, and — often the biggest surprise — people start giving you more specific, more useful feedback, because they've learned you'll actually do something with it.