Giving feedback is easy. Giving feedback that actually lands — that the other person can hear, process, and use — is a skill. Most feedback fails not because it’s wrong, but because it’s delivered in a way that triggers defence rather than reflection.

Why feedback fails

When someone receives feedback, their brain faces a choice: treat it as information (useful, process it) or treat it as a threat (dangerous, defend against it). Most poorly delivered feedback triggers the threat response.

It’s too vague. “You need to be more professional” gives nothing to work with. What specific behaviour? In which context? The vaguer the feedback, the more the person fills in the blanks with their worst fears.

It’s about identity, not behaviour. “You’re disorganised” attacks who they are. “The last three reports were submitted after the deadline” describes what happened. The second gives them something to change; the first makes them feel helpless.

It’s public. Feedback delivered in front of others adds shame to the equation. Shame shuts down learning. Always give critical feedback privately.

It comes with judgement. There’s a difference between “I noticed X and here’s the impact” and “I can’t believe you did X.” The first is neutral observation. The second is evaluation — and evaluation feels like a verdict.

Descriptive vs. evaluative

This is the core distinction that separates feedback people can hear from feedback they reject:

Evaluative feedback passes judgement: “That presentation was terrible.” “You’re not a team player.” “Your work is sloppy.”

Descriptive feedback observes specifics: “The slides had several data errors.” “In the last three meetings, you presented your ideas without asking for input from others.” “The report had formatting inconsistencies on pages 4 and 7.”

Descriptive feedback works because:

  • It’s harder to argue with facts than opinions.
  • It gives specific targets for improvement.
  • It doesn’t attack identity, so defences stay down.
  • It respects the other person’s ability to draw their own conclusions.

The feedback framework

1. Ask permission (when appropriate). “Can I share some observations about the project?” This signals respect and gives the other person a moment to prepare mentally. In formal settings (performance reviews, manager-to-report), this isn’t always necessary — but it still helps.

2. Describe the behaviour. What you observed, specifically. Facts only, no interpretation. “In yesterday’s client call, you interrupted the client three times during their explanation.”

3. Share the impact. What happened as a result. “The client seemed frustrated and cut the call short. I’m concerned we may lose the account.” Impact makes the feedback relevant — it answers “why does this matter?”

4. Invite their perspective. “How do you see it?” They might have context you don’t. They might already be aware. They might disagree — and that’s a conversation worth having.

5. Collaborate on next steps. “What could we try differently next time?” This turns feedback from judgement into problem-solving. You’re on the same side.

Context matters

Timing. Don’t give feedback when either of you is emotional, rushed, or distracted. The best feedback is given soon after the event (while it’s fresh) but not in the heat of the moment.

Ratio. If the only time you give someone feedback is when something’s wrong, they’ll associate you with criticism. Make a habit of noting what works, too — not as a manipulative “sandwich” technique, but as genuine recognition.

Relationship. Feedback from someone you trust lands differently from feedback from someone you don’t. If the relationship is new or strained, invest in trust before expecting critical feedback to be well-received.

Culture. Different workplace and family cultures have different norms around directness. What reads as honest in one context reads as harsh in another. Adjust your delivery without diluting your message.


The goal of feedback isn’t to be right. It’s to be useful. If you’re right but the other person can’t hear you, nothing changes. If you deliver the same information in a way they can process, everything can change. The art isn’t in what you notice — it’s in how you share it.