If someone goes defensive every time you give them feedback, the most useful assumption is not that they cannot take it. It is that the feedback is arriving in a form they cannot use. Defensiveness is a response to how something was delivered at least as often as it is a response to what was said — and delivery is the half you control.
Why does the same feedback land differently with different people?
Because people process information differently, and under pressure those differences get sharper, not softer. Someone who wants the conclusion first experiences a long, careful build-up as evasion, and starts bracing before you reach the point. Someone who needs the reasoning first experiences a blunt opening as an attack, because the judgement arrived before any of the context that would let them evaluate it.
Both of them are now defensive. Neither of them has heard the actual feedback yet. And in both cases you delivered it the way you would want to receive it, which is the default almost everyone runs.
This is the practical use of DISC: it gives you a read on how the person in front of you processes information, so you can adapt the delivery deliberately instead of discovering the mismatch mid-conversation.
How should you adapt the delivery?
Same message, four different openings:
| Style | What defensiveness looks like | How to deliver it |
|---|---|---|
| D — Dominance | Cuts you off, challenges the premise, wants to argue the point | Lead with the conclusion. Be direct and brief. Skip the preamble — it reads as softening bad news |
| I — Influence | Talks over it, reframes it, turns it into a story | Keep it warm but land one specific point. Confirm the agreed action in writing afterwards |
| S — Steadiness | Goes quiet, agrees too readily, absorbs it without objecting | Slow down. Give notice that the conversation is coming. Ask directly for their view and wait for it |
| C — Conscientiousness | Disputes the detail, asks for evidence, litigates the example | Bring specifics. Give them time to process before expecting a response. Do not rush the conclusion |
The S row is the one leaders misread most often. Quiet agreement is frequently taken as feedback landing well. It is often the opposite — the person absorbing it, saying nothing, and changing nothing, because the conversation gave them no room to disagree.
What still applies regardless of style
- Be specific about behaviour, not character. "You interrupted three people in that meeting" is workable. "You're not a team player" is a verdict, and people defend against verdicts.
- Say it close to when it happened. Feedback saved up for a review arrives with compound interest and feels like an ambush.
- Separate the observation from the interpretation. Say what you saw, then say what you concluded, and let them correct the second one. Most defensiveness is an argument with an interpretation that was never stated as one.
- Ask before you conclude. There is often information you do not have. Asking is not softening — it stops you being wrong in public.
- Agree the change out loud. End with what will be different and when you will look at it again. Without that, the conversation was a critique, not feedback.
What if they are defensive no matter how you deliver it?
Then you have moved from a communication problem to a performance conversation, and it should be run as one — clearly, on the record, with a stated expectation and a date. That is a different conversation and it deserves to be named as such rather than repeated as feedback that never takes.
Worth checking first, honestly: whether the feedback has ever actually been delivered plainly, or whether it has been hinted at several times and counted as delivered. Those feel the same from the inside and are completely different from the receiving end.
Adapting how you deliver hard messages is one of the most common things leaders work on in coaching. See Executive & Performance Coaching or book a free consultation.
- communication
- DISC
- feedback