How to give feedback that lands
Feedback lands when it targets behavior, names which type it is, and arrives often enough to matter. The playbook — and why the feedback sandwich fails.
Feedback lands when it targets a specific behavior, not the person behind it. Stone & Heen (2014) found that most feedback misfires because givers and receivers are answering different questions at the same time — one evaluating, the other seeking appreciation. Name which game you are playing before you start.
Name the type of feedback before you give it
Stone & Heen’s central argument in Thanks for the Feedback (2014) is that feedback fails most often not because it was delivered badly, but because the giver and receiver were trying to have different conversations. The giver arrives with coaching in mind; the receiver is waiting to hear whether they are valued. Nobody named the type, so both leave frustrated.
The three types are appreciation (I see what you did and it matters), coaching (here is how to grow), and evaluation (here is where you stand). Each requires a fundamentally different posture from the listener. Appreciation needs to be received; coaching needs to be considered; evaluation needs to be accepted or contested. When you blend them — burying a performance evaluation inside what sounds like a coaching conversation — the receiver does not know how to process what they are hearing.
The fix is simple and almost no one does it: say the type out loud. “I want to share some coaching feedback about how this project went” or “I need to give you an evaluation, which is different from what I usually bring.” Two sentences of naming saves the entire conversation from derailing. If you are still building the vocabulary for difficult conversations, our piece on how to raise a problem without starting a fight covers the same principle from the raising side.
Behavior, not character — every time
Sullivan (Simply Said) and Goleman both make the same point with different language: feedback aimed at character is unfalsifiable and therefore useless. “You are careless” cannot be acted on. “The report had three factual errors that were caught in the review meeting” can be. The first produces shame and defensiveness; the second produces a specific, correctable problem.
Chandler (Feedback and Other Dirty Words) adds a useful frame: notice without judging. The observer role is to describe what happened, as specifically as possible, without layering on an interpretation of what it means about the person. “The client asked a question and the call went silent for 45 seconds” is observation. “You clearly weren’t prepared” is interpretation. Start with observation. Let the interpretation emerge from the conversation, not from your opening line.
This is also why always and never are dangerous words. Hancher (Firm Feedback) flags them as distortion terms: they invite the recipient to find the one counterexample that proves you wrong, and then the conversation is about the exception rather than the pattern. “This is the third time in a month” is specific. “You never meet deadlines” is a fight invitation.
Why frequent small feedback beats the annual download
Here is the explicit stance: saving feedback for a quarterly or annual review is a failure mode, not a system. By the time months of observations have been batched up, several things have gone wrong. The recipient cannot remember the specific events well enough to discuss them. The giver’s account has been shaped by recency bias and accumulated frustration. The stakes feel enormous because the conversation is enormous. And the behaviors being discussed have been running uncorrected long enough to become habits.
Chandler’s case for frequent, bite-sized feedback rests on absorption: a one-sentence observation delivered the same day is metabolized completely differently than a twelve-point review delivered six months later. Small, timely feedback is information; large, delayed feedback is an event, and events trigger fight-or-flight rather than reflection.
The practical implication is that giving feedback well is less about mastering a single high-stakes conversation and more about building a low-stakes habit. A thirty-second observation after a meeting — “that reframe you used was sharp, the client visibly relaxed” — costs almost nothing and does more than an hour-long performance review. The same applies to the how to receive feedback side: people get better at receiving when feedback stops being rare and terrifying.
Huston (Let’s Talk) frames the prerequisite clearly: this habit only builds if there is trust in the relationship. Before you can give regular, honest observations, the other person needs to know your intentions are good. State them. “I raise things quickly because I think it helps both of us” is not a preamble to dismiss — it is the sentence that makes everything after it receivable.
Match the mode to the situation
Hancher’s three modes — directive, collaborative, and supportive — solve a real problem: not every feedback situation is the same, and treating them identically produces friction. Using the wrong mode is one of the most common reasons a technically well-delivered message still lands badly.
Directive is appropriate when the standard is clear, the gap is clear, and the path is clear. There is not much to discuss. A deadline was missed; the procedure was not followed; the output did not meet the specification. Directive feedback does not need to be cold or harsh — it just needs to be unambiguous. Wrapping it in collaborative language to soften it creates confusion about whether there is actually a problem.
Collaborative is appropriate when you have partial information and so does the other person. You noticed something; you do not fully understand why it happened; the best solution requires their knowledge as well as yours. This is a genuine problem-solving conversation, and it should feel like one. Wong’s past–present–future structure fits here particularly well: name what happened (past), describe the impact you observed (present), invite them to help design the fix (future).
Supportive is appropriate when the person already knows what to do and needs a space to process, not a new instruction. They missed something they understand; they are in a difficult patch; they need acknowledgment before they can move. Giving directive feedback in a supportive moment — jumping straight to ‘here is what you need to do differently’ — shuts down the conversation. Listen first. The directive or coaching can follow once the person feels heard. For those moments when the conversation is genuinely high-stakes, the full playbook for how to have a difficult conversation covers the preparation and structure in more depth.
References
-
Reference Thanks for the Feedback
Stone, D., & Heen, S. (2014). Viking.
-
Reference Simply Said
Sullivan, J. (2016). Wiley.
-
Reference Let's Talk
Huston, T. (2021). Portfolio.
-
Reference Feedback and Other Dirty Words
Chandler, M. T. (2019). Berrett-Koehler.
-
Reference Firm Feedback
Hancher, M. (2022).
-
Reference Eight Essential People Skills
Wong, P. T. P. (2021).
-
Reference Handbook of Strategic 360 Feedback
Church, A. H., et al. (2019). Oxford University Press.
FAQ
What is the most important rule for giving feedback?
Target the **behavior**, not the person. Sullivan (*Simply Said*) and Goleman both emphasize that feedback aimed at character — 'you are disorganized' — triggers defensiveness and changes nothing. Feedback aimed at a specific action — 'the agenda arrived 20 minutes into the call' — is observable, debatable, and actionable. The rule is not about softening the message; it is about making it specific enough to be useful. A person cannot change 'being disorganized,' but they can change when the agenda goes out.
What is the difference between appreciation, coaching, and evaluation?
**Stone & Heen (2014)** identify three distinct feedback types that people constantly confuse. **Appreciation** is motivational — 'I see what you did and it matters.' **Coaching** is developmental — 'here is how to grow.' **Evaluation** is comparative — 'here is where you stand against a standard.' Each requires a different mindset from the receiver. The failure mode is mixing them: wrapping a performance evaluation in coaching language, or hoping appreciation will substitute for a hard evaluation. Name the type before you start so the other person knows how to listen.
Does the feedback sandwich actually work?
No. Hancher (*Firm Feedback*) and Hutchens (*Get It*) both criticize the positive–negative–positive structure for diluting the message. When people know the sandwich, they wait through the opening praise for the real point, and the closing compliment reads as damage control. The concern gets lost in the bread. If you have something important to say, say it directly, with context and care — not buried between two unrelated positives. Direct does not mean harsh; it means the recipient knows what you actually mean.
How often should I give feedback?
Far more often than most people do. **Chandler (*Feedback and Other Dirty Words*)** argues that frequent, bite-sized feedback — a quick observation after a meeting, a one-sentence note the same day — is dramatically more effective than the annual or quarterly download. Small doses are easier to absorb, easier to act on, and less threatening. By the time feedback has been saved up for months, it has aged badly: the recipient cannot recall the context, and the giver's account has been distorted by memory. Build the habit of noticing and saying something small, regularly.
How do I give feedback without triggering defensiveness?
State your good intentions explicitly, before the content. **Huston (*Let's Talk*)** and **Church et al. (*Handbook of Strategic 360 Feedback*)** both stress that **psychological safety** is the prerequisite — if the receiver does not trust your motives, no framing will save you. Open with why you are saying this: 'I want to raise something because I think it will make the project go better for both of us.' Then anchor the feedback to a specific observable behavior rather than a trait. The combination of stated intent plus specific behavior cuts the defensive reaction significantly, because there is less to argue with.
What are the three feedback modes and when do I use each?
Hancher (*Firm Feedback*) describes **directive**, **collaborative**, and **supportive** modes. Use **directive** when there is a clear standard and the person is falling short of it — no ambiguity about what needs to change. Use **collaborative** when both parties have relevant information and the best path forward is genuinely uncertain — this is a problem-solving conversation, not a verdict. Use **supportive** when the person already knows what to do but needs confidence or processing space. Picking the wrong mode is a common failure: using collaborative when directive is needed creates confusion; using directive when supportive is needed feels like an attack.
What is the past–present–future feedback structure?
**Wong (*Eight Essential People Skills*)** outlines a three-stage structure: surface the **past** event without judgment, diagnose the **present** impact or pattern, then plan the **future** next step together. Example: 'In the last three calls, the agenda came out after we started' (past). 'That makes it hard to prepare questions in advance, which slows us down' (present). 'Can we agree it goes out the evening before?' (future). The structure stops feedback from being a verdict and turns it into a problem with a solution. It also forces the giver to have a concrete ask ready, which is the most common thing missing.
How do I give feedback to someone more senior than me?
The same principles apply — specific behavior, named intent, chosen mode — but the sequencing matters more. Start by **asking permission**: 'I noticed something last week; would it be useful to share it?' This respects the power dynamic without abandoning the feedback. Use the collaborative mode almost always with seniors: you are raising an observation and inviting their read, not issuing a verdict. Huston (*Let's Talk*) notes that upward feedback is most credible when it is framed around shared goals rather than personal preferences: 'I think this is affecting the team's ability to X' rather than 'I find it difficult when you Y.'
Should I give feedback in public or private?
Private, almost always. Public feedback — even positive — puts the recipient on a stage they did not choose, which triggers self-consciousness rather than absorption. Critical public feedback is almost never absorbed; it is survived. The exception is **appreciation**: a genuine public recognition of someone's contribution can be welcome if it is specific and does not embarrass. Even then, if you are uncertain, ask the person first. The safest default: say the hard things in private, reserve public moments for genuine celebration, and check before you make anyone the center of attention they didn't request.
How do I follow up after giving feedback?
Check in, briefly, within a week. Ask how it landed, not whether they agreed with it. Something like 'I wanted to check in — has what I raised been useful, or was there something in how I said it that got in the way?' This signals that you care about the relationship, not just the content, and it gives the recipient a chance to process and respond rather than react. **Chandler (*Feedback and Other Dirty Words*)** frames good feedback as a loop, not a delivery: the giver is also responsible for noticing whether the message was received in the spirit it was intended.