Why You Become Defensive When Receiving Feedback

Defensiveness is usually faster than thought

You hear, “The team did not know where the decision stood,” and your mind is already producing the messages you sent, the meeting they missed, and the reasons the situation was unusually difficult.

The explanation may be accurate. The problem is timing, and it is worth regulating before the conversation rather than during it. If it arrives before the feedback has been understood, the other person learns that giving you difficult information creates more work for them.

What the reaction may be protecting

Defensiveness is not always vanity. Feedback can threaten several things at once:

• Competence: “If this is true, perhaps I am not good at the job.”
• Fairness: “I am being judged without the context.”
• Status: “They no longer see me as credible.”
• Belonging: “This could change whether I am wanted here.”
• Intent: “They are describing an impact that does not match who I believe I am.”

Naming the threat privately says nothing about whether the feedback is correct, only about why hearing it cleanly is hard.

Find your sequence, not your type

A broad label such as “you are defensive” is not very useful. Look for what happens in order.

Perhaps you first become helpful and agree with everything. When that does not end the discomfort, you begin correcting the facts. Or you go silent in the meeting and return later with a long message that dismantles the example. Or you explain immediately, then become sharp when the explanation does not restore your standing.

The sequence matters because the second move is often the one other people remember. It also shows where you have a chance to intervene.

Do not turn this into a personality verdict. One event is one event. A pattern requires repeated examples under similar conditions.

What to do in the first minute

Use a response that keeps the channel open without performing agreement:

“I can feel myself wanting to explain the context. Before I do, can you give me one example of when you saw this?”

Then ask enough to understand:

• What did I do or say?
• What happened because of it?
• What would have helped instead?

You do not have to settle the truth of it in the room. Understand the example well enough to think about it properly later.

Restate before you respond

Try: “What I hear is that when I changed direction in the meeting without closing the earlier decision, the team did not know which version to follow. Is that the point?”

If they say yes, you now have something specific. You may still disagree about context or scale. Start there instead of answering an accusation they did not make.

Separate impact from identity

“This behaviour had this impact” is not the same as “this is who you are”. When the two collapse, people either reject the feedback or accept a damaging identity judgement.

Keep it behavioural. Could you try something different in the next comparable moment? If yes, the feedback is actionable. If the feedback remains a vague statement about your character, ask for an example and a desired alternative.

Decide after the meeting

Later, sort the feedback into three buckets:

• True and useful: act on it.
• Partly true or context-dependent: test it in another situation.
• Unsupported or inappropriate: decline the conclusion while retaining any useful observation.

You can take feedback well and still reject part of it. What you cannot do is let the first protective reaction stand as the final word.

A small practice for next time

Choose a cue and response: when I hear feedback and start collecting rebuttals, I will ask for one example and restate the point before explaining.

That is a behaviour another person can experience. “Be less defensive” is only an aspiration — see how to make one change stick. If you are the one giving the feedback, how to give it without damaging the relationship is the other half.

Frequently asked questions

Continue reading