How to Give Feedback That People Actually Hear
Most feedback conversations fail before they start. The feedback is given defensively — with excessive preamble, vague examples, and a final reassurance that negates what was just said. The person receiving it either argues back, nods and changes nothing, or takes it more personally than intended and loses confidence. The failure is not usually in the intention to give feedback but in the skill of giving it in a way that produces a useful response rather than a defensive or demoralised one.
The most reliable framework for effective feedback is one that describes behaviour rather than character. "In Tuesday's client meeting, you cut across Marcus twice while he was presenting" describes an observable behaviour. "You're not a good listener" describes a character trait. The former invites a specific response — the person can think about whether they were aware of it, why it happened, and what they will do differently. The latter invites defence of a self-image, which produces argument rather than change.
Specificity is the single most important quality of feedback that lands. The feedback recipient needs to be able to play the moment back in their mind — to see what you saw, hear what you heard, and understand why it mattered. Feedback that cannot be traced to a specific event ("you could improve your communication") provides nothing to work with. Feedback that refers to a specific, recent, well-described example provides both evidence and context for change.
Timing matters. Feedback given close to the event — within the same day where possible — is more accurate, more useful, and more likely to be received constructively than feedback given weeks later when neither party's memory is clear. The common practice of "saving up" feedback for the annual review produces the worst possible conditions for the conversation: the examples are stale, the recipient has no opportunity to improve in real time, and the review becomes a retrospective judgment rather than a forward-looking development conversation.
The feedback conversation should end with clarity about what is expected going forward, not just what went wrong in the past. "I'd like you to check in with the presenter before cutting across anyone's point in future" is a forward-looking instruction that gives the person something to do. Without a clear expectation going forward, feedback is criticism without direction — and criticism without direction tends to produce anxiety rather than improvement.
Positive feedback deserves the same specificity as developmental feedback. "Good work" is pleasant but provides no information. "The way you handled the escalation call with the client — staying calm, summarising their concerns back to them before responding, and committing to a specific timeline — is exactly the standard we're trying to reach" tells the person specifically what they did well and why it mattered. That specificity makes positive feedback genuinely developmental, not just motivational.
Managers who are skilled at giving feedback create teams where development feels continuous rather than episodic. The conversations become normal — something that happens because the manager is paying attention and cares about the person's growth, not an event that is feared because it signals a problem. Building that normality takes time and consistency. The single biggest accelerant is for managers to receive good feedback themselves — which is both a model of how it should be done and a motivator for doing it for others.