Situations

Feedback People Actually Hear

Why most feedback gets nodded at and then ignored, and three documented approaches, from Scott, Edmondson, and Rogers, for feedback that actually changes behavior.

By Gareth Hoyle·5 October 2026·8 min read

The feedback gets delivered. The person nods, says thank you, maybe even agrees out loud that it's fair. Three weeks later, nothing has changed. The feedback wasn't wrong. It just wasn't heard in any way that reached the part of the person that would actually change behavior.

Why does the generic feedback advice fail?

"Use the feedback sandwich," positive, critical, positive, is probably the most widely taught feedback technique and one of the most reliably ineffective. The recipient learns to wait for the critical middle layer and discount the praise around it as padding, which means the positive feedback loses credibility at the same time the critical feedback gets buried in a softening structure that dilutes its specificity.

Generic AI prompting tends to reproduce exactly this pattern. Ask an assistant to "help me give feedback to my employee about their missed deadlines," and without more context it will often default to a diplomatically softened structure that prioritizes not upsetting the recipient over being specific enough to actually change what they do differently next time. It sounds kind. It rarely changes behavior.

The deeper problem with both the sandwich technique and generic AI softening is that they optimize for the moment of delivery rather than for what happens after the conversation ends. A piece of feedback can feel comfortable to deliver and comfortable to receive and still fail completely at its actual job, which is changing what the person does next time the situation comes up.

What does the documented research say to do instead?

Kim Scott: care personally and challenge directly, at the same time

Scott's Radical Candor (2017) argues that feedback fails along two separate axes: whether the giver demonstrates genuine personal care, and whether the feedback is specific and direct enough to act on. Feedback that's caring but vague doesn't change behavior. Feedback that's direct but delivered without demonstrated care reads as an attack and triggers defensiveness instead of reflection.

Applied: Before delivering critical feedback, make the care explicit and specific, not a generic "I care about you" but a concrete reference to why this particular person's growth matters to you or the team. Then deliver the critique itself with specific, observable detail, not "be more reliable" but "the last three deadlines slipped without a heads-up, and that's what I need to see change."

The two axes have to show up together, not in sequence. Leading with vague warmth and then pivoting hard into blunt criticism reads as exactly the sandwich pattern that trains people to discount the positive half. Scott's framework works because the care and the directness are woven into the same specific sentences, not separated into different parts of the conversation.

This is the part most feedback training drops: it's easier to teach "be direct" and "be kind" as separate skills to practice in sequence than to teach the harder, more specific move of writing a single sentence that carries both at once. The payoff is that a sentence doing both jobs together reads as one coherent message instead of two conflicting ones stitched together.

Amy Edmondson: the safety has to exist before the specific conversation

Edmondson's The Fearless Organization (2019) documents psychological safety, the shared belief that it's safe to take interpersonal risks in a given group, as the precondition for feedback actually landing rather than triggering a defensive shutdown. Feedback delivered into a low-safety relationship gets heard as a threat regardless of how carefully it's phrased in the moment.

Applied: Before a specific hard conversation, consider the broader pattern: has this person seen you respond well to their own disagreement or mistakes in the past? If the answer is no, the immediate feedback technique matters less than the longer-term work of demonstrating that imperfection and disagreement are survivable in this relationship. A single well-phrased conversation can't substitute for that groundwork.

This is why the same words, delivered by two different managers, land completely differently: the words aren't actually where most of the information is. The recipient is reading the relationship's history for evidence of whether this is safe territory, and a technically well-structured feedback conversation on top of a low-safety relationship often does less good than a clumsier conversation inside a relationship with real trust already built.

Carl Rogers: separate the person's worth from the specific behavior

Rogers' unconditional positive regard and person-centered method, documented across his published therapeutic work, holds that people change most readily when they feel accepted as a whole person independent of the specific behavior being discussed. Feedback that implicitly threatens the relationship or the person's basic worth triggers defense of the self rather than consideration of the behavior.

Applied: Frame critical feedback explicitly as being about a specific action, not an identity: "this particular report had gaps" rather than "you're not detail-oriented." The distinction sounds subtle but changes what the recipient defends, a specific fixable action versus a global claim about who they fundamentally are.

Rogers' broader insight is that a person can only genuinely consider changing a behavior once they stop having to defend their basic worth in the conversation. The moment feedback starts to feel like a verdict on character rather than a note on one action, the recipient's energy shifts from considering the content to protecting the self, and the actual behavioral message gets lost in that shift regardless of how accurate it was.

How do the three compare side by side?

ApproachFromWhen it fitsWatch out for
Care personally, challenge directlyKim Scott, Radical CandorYou need a specific behavior to change soon and the relationship can bear directnessDropping the care half turns this into plain criticism; dropping the directness turns it into empty warmth
Build safety before the conversationAmy Edmondson, The Fearless OrganizationFeedback keeps triggering defensiveness regardless of how it's phrasedTakes longer than any single conversation technique; it's groundwork, not a script
Separate behavior from identityCarl Rogers, person-centered methodThe feedback risks feeling like a judgment of character rather than a specific actionCan read as overly therapeutic if the specific behavioral ask gets lost in the framing

What can you run before the next conversation?

1. The care-and-directness check
"Here's feedback I need to give: [describe the situation]. Help me write it so the care is specific and genuine, not generic warmth, and the critique is specific and actionable, not vague. Show me where I'm currently being vague on either side."

Why it works: most feedback drafts fail on one axis or the other without the writer noticing, and an explicit check against both catches the gap before the conversation happens.

2. The identity-versus-behavior rewrite
"Here's feedback I was planning to give: [paste it]. Rewrite it so every statement is about a specific, observable action rather than a trait or character judgment about the person."

Why it works: identity-level language is often unconscious, "you're careless" instead of "this specific thing was missed", and a rewrite pass catches it reliably.

3. The safety read
"Here's my working relationship with this person: [describe the history, including past hard conversations]. Based on this, how much groundwork-building should I do before delivering direct critical feedback, versus how ready is this relationship for directness now?"

Why it works: forcing an explicit read on relationship safety before choosing a feedback approach prevents defaulting to the same delivery style regardless of context.

What's the honest limit of this approach?

These frameworks improve how feedback is built and delivered. None of them can guarantee the recipient changes, people sometimes hear perfectly delivered feedback and still don't act on it, for reasons entirely outside the conversation itself, workload, disagreement with the premise, or circumstances you don't know about. The frameworks raise the odds of being heard. They don't guarantee the outcome. A well-delivered piece of feedback into a relationship with months of unaddressed low safety is still working against that history, and no single conversation technique closes a gap that was built over a much longer time.

Kim Scott and Amy Edmondson both sit in the People & Culture category, the fuller bench for management and team dynamics work. Carl Rogers' full person-centered framework lives in the Psychotherapist category. For structuring a specific hard feedback conversation you've been postponing, Difficult Feedback is a $49 tool built for exactly that.

All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.

FAQ

Frequently asked questions

Is this guide about giving feedback or receiving it?

Giving it, specifically the problem of feedback that's delivered, acknowledged, and then doesn't change anything. Receiving feedback well is a related but separate skill, and the frameworks here are built around the giver's side of the exchange.

What's the single biggest reason feedback gets ignored?

The person receiving it doesn't believe it's meant to help them, as opposed to protect the giver, cover a process requirement, or vent frustration. Kim Scott's framework names this directly: feedback without demonstrated personal care reads as an attack or a formality, neither of which motivates real change.

Does this apply to feedback from a peer, not just a manager?

Yes, arguably more so, since peers usually have less implicit authority to make feedback land and have to rely more heavily on trust and clear specificity to be heard at all. All three frameworks here are about the mechanism of being heard, not about positional authority.

What if the person just gets defensive no matter how it's delivered?

Defensiveness is often a signal that psychological safety is missing in the relationship or the broader team context, not necessarily that the feedback itself was poorly phrased. Amy Edmondson's framework addresses this directly: the groundwork for hearable feedback is laid well before the specific conversation happens.

Can AI tell me exactly what to say in a specific feedback conversation?

It can help you structure what you want to say and check it against these frameworks, specific, caring, delivered in a way that invites rather than forecloses response. It has no knowledge of this particular relationship's history or this person's specific triggers, so the final judgment about delivery still has to be yours.

Is Carl Rogers' approach too soft for a performance problem that needs to change fast?

Unconditional positive regard doesn't mean avoiding the hard message, it means separating the person's worth from the specific behavior being addressed. A direct, specific critique delivered without that separation often triggers defensiveness that actually slows the behavior change down, which matters most exactly when speed is the goal.

How is this different from Radical Candor training most companies already do?

This guide draws the same Kim Scott framework many companies already reference, but adds Edmondson's safety precondition and Rogers' person-centered delivery mechanism, which most Radical Candor training compresses into a single slide. The combination is the point: care and candor alone aren't sufficient without the safety and delivery mechanics underneath them.

Written by Gareth Hoyle. Last updated 5 October 2026. Part of the authority.md guides library.

Keep reading

More guides.