Giving & Receiving Feedback

Why Feedback Is the Most Underused Communication Skill

Most workplaces have a feedback problem, and it usually runs in the wrong direction. People assume the hard part is delivery: how to phrase the criticism, how to soften the blow, when to schedule the chat. So the training money goes to managers learning to give better feedback. But the person doing the talking is rarely the bottleneck. The bottleneck is the person on the receiving end, who can dismiss, deflect, or quietly resent even a well-built comment within seconds.

That is the central argument Stone and Heen make in Thanks for the Feedback. They spent roughly a decade studying why feedback is so hard to absorb, and concluded the business world has it backwards. Polish the giver all you want. A defensive receiver still learns nothing. Their fix is to treat receiving as a skill in its own right, one you can practice, rather than a trait you either have or lack.

Feedback also gets called the wrong thing. A vague compliment, a rant about character, an annual review that dumps nine months of grievances at once, all of it gets filed under "feedback." None of it does the one job feedback exists for: giving a person something concrete to act on. Good feedback is specific, timed close to the event, and clear about what to keep doing or change. The frameworks below exist to make that easier, not to turn an ordinary conversation into a ceremony.

None of this is exotic. The same instincts that carry a hard conversation at home carry it at work: describe what you saw, say what it did, stay curious about the other side. Feedback sits on the same shelf as difficult conversations and conflict resolution, and people who handle one well tend to handle the others well too. What follows is a set of structures our guides return to often, with an honest note on where each one helps and where it gets in the way.

The SBI Feedback Model: Situation, Behavior, Impact

SBI is the model most worth learning first, because it fixes the single most common failure in feedback: the leap from one event to a character verdict. Someone misses a deadline, and the comment that lands is "you're unreliable." That is not feedback. It is a label, and labels invite a fight.

The structure splits the message into three parts. Situation sets the scene, naming the specific time and place so there is no ambiguity about which moment you mean. Behavior describes what the person actually did, in plain, observable terms, the way a camera would record it. Impact explains the effect that behavior had, on you, on the work, on the team. The point is to stay on the ground the whole way through. You are reporting an observation, not handing down a judgment.

Compare two versions of the same note. The vague one: "Your presentation needed work." The SBI one: "In this morning's client call (situation), you read the slides aloud word for word (behavior), and I noticed the buyers stopped asking questions and started checking their phones (impact)." The second gives the person something to do differently next time. The first gives them a wound and no map.

SBI works for praise too, which is where people forget it. "Great job" is pleasant and forgettable. "When you caught the billing error before the invoice went out (situation and behavior), you saved us a refund request and an awkward email to the client (impact)" tells the person exactly which instinct to repeat. Positive feedback that names the behavior is far more useful than positive feedback that just radiates warmth.

The limit of SBI is that it describes; it does not solve. It is built to deliver a clear observation cleanly. What happens next, the part where the two of you figure out what to change, sits outside the acronym. That is by design. Stating the impact and then pausing leaves room for the other person to respond, rather than rushing to a fix before they have even agreed there is a problem. Treat SBI as the opening move, not the whole conversation.

Comparing Feedback Frameworks

No single framework wins every situation. SBI shines for a quick, behavior-specific note. DESC, from the Bowers' Asserting Yourself, adds the step SBI deliberately leaves out: it specifies what you want to happen next. The feedback sandwich, praise wrapped around criticism, is the most popular and the least defensible, for reasons worth being blunt about. And feedforward skips backward-looking critique entirely in favor of ideas for the future.

The table below lays the four side by side. Read it as a menu, not a ranking. The right choice depends on the stakes, your relationship with the person, and whether the goal is to flag one behavior or to renegotiate an ongoing pattern.

One practical rule cuts through the choice. If the behavior happened once and you mainly want the person to see its effect, reach for SBI. If it keeps happening and you need an actual change, use DESC so the request is explicit. Save feedforward for moments where the goal is growth rather than correction, and treat the sandwich with suspicion. We get into why next.

Feedforward: The Future-Focused Alternative

Feedforward flips the camera around. Instead of dissecting what went wrong last week, it asks a simple question: what two or three things could you try next time? The conversation points ahead, toward what is still changeable, rather than back at a record nobody can edit.

The appeal is psychological. People defend the past because the past is theirs; criticism of it can feel like criticism of them. Suggestions about the future carry no such charge. There is nothing to defend, because the thing being discussed has not happened yet. That tends to lower the guard that even fair criticism raises, which makes feedforward a comfortable fit for peers who have no authority over each other and for situations where trust is still thin.

It pairs naturally with everyday workplace communication, where a quick "here's something to try in the next demo" travels far more easily than a formal sit-down. It also leans on the same future orientation that good leaders use when they coach rather than correct.

Be honest about the trade-off, though. Feedforward's strength is also its blind spot. By looking only forward, it can let real failures slide unexamined. If someone broke a commitment, mishandled a client, or repeated a mistake they were already warned about, "here's an idea for next time" is not enough. Some situations require naming what went wrong and why it mattered, plainly, before any talk of the future. Use feedforward to build skill and momentum. Do not use it to dodge accountability.

How to Receive Feedback Without Defensiveness

Here is the part most guides rush past. You can master every model for giving feedback and still learn nothing from the feedback aimed at you, because the hard skill is on the receiving side. Stone and Heen built an entire book around it, and their starting observation is that defensiveness is not a character flaw. It is the default human response to feeling judged, and almost everyone does it.

Their useful insight is that we reject feedback for predictable reasons. Sometimes the content seems wrong, so we argue the facts. Sometimes it is the messenger; the same advice from someone we trust would land, but from this person it grates. And sometimes the feedback rattles our sense of who we are, and the threat to identity drowns out the actual message. Knowing which of these is firing in a given moment is half the battle, because each one calls for a different recovery.

A few habits make the difference. Listen for the one grain of truth before reaching for the ninety-nine ways the person is wrong; almost all feedback contains something, even when most of it misses. Ask a clarifying question instead of mounting a defense, because "can you give me an example?" buys time and information at once. Separate the message from the delivery, so a clumsy or badly timed comment still gets a fair hearing. And give yourself permission to disagree later. Hearing feedback fully is not the same as accepting it; you can take it in, sit with it, and still decide it was off.

This is where receiving feedback overlaps with plain active listening. The skills are the same: stay quiet long enough to actually hear, reflect back what you heard, resist the urge to rebut before the other person has finished. A receiver who can do that turns even an awkward, poorly delivered comment into something useful, which is a quieter and more valuable skill than knowing how to deliver the comment in the first place.

Giving Feedback Across Power Dynamics

Feedback never travels through neutral air. It moves along lines of power, and the direction of travel changes everything about how it should be handled. The same words carry different weight coming down the hierarchy than going up it, and pretending otherwise is how well-meant feedback backfires.

Downward, from manager to report, the main risk is force. A boss's offhand remark lands harder than intended, because the listener hears it through the filter of "this person controls my paycheck." Tone and nonverbal signals amplify the effect, since a frown or a clipped delivery reads as far more severe from someone with authority. So precision matters more, not less. Stick to observable behavior, name the impact, and leave room for the other person to explain. A manager who labels rather than describes does real damage, because the report cannot easily push back.

Upward feedback, from report to manager, carries the opposite risk: it often does not get given at all. The cost of speaking up feels high, so people stay quiet and the manager keeps making the same mistake in the dark. When you do offer it, frame the feedback around shared goals and concrete impact rather than personal criticism, and pick your moment. "Here is something that would help me do this better" opens a door that "you're doing this wrong" slams.

Peer to peer is the easiest channel and the most wasted. There is no authority gap to manage, which is exactly why feedforward and casual SBI work so well between colleagues. The catch is that peers often withhold honest feedback to keep the relationship comfortable, so the most useful observations go unsaid. Across all three directions, the constant is the same: describe behavior, name impact, stay curious. The power dynamic decides how carefully you wrap it, not whether the underlying structure holds.

Building a Feedback Culture on Your Team

You cannot order a team to be candid. Feedback culture is not a policy you announce; it is a set of habits that either get practiced until they feel normal or stay theoretical forever. The teams that manage it tend to share a few traits, and none of them involve a poster on the wall.

The first is frequency. When feedback only shows up in the annual review, every instance of it feels loaded, because the stakes are high and the event is rare. When small comments flow regularly, in both directions, each one carries less charge and people stop bracing for them. A quick observation today beats a saved-up list in six months, every time. The annual review should hold no surprises.

The second is that leaders go first, and go first as receivers. A manager who asks for feedback, listens without defending, and visibly acts on it does more to build candor than any number of speeches about openness. People watch what happens to the first person who speaks up. If that person is the boss and nothing bad follows, the message lands. This is the practical core of psychological safety: the belief, earned through repeated experience, that an honest comment will not be punished.

Third, separate feedback from formal evaluation where you can. The two get tangled, and the tangle is corrosive: when every comment might affect a rating, a raise, or a promotion, people optimize for looking good rather than getting better. Coaching conversations that carry no scorekeeping let people be honest about what they are struggling with. Some of this is structural, and worth building into how the team communicates day to day, whether in the room or across a distributed team where casual feedback has to be made deliberate because it no longer happens by the coffee machine. A formal communication skills workshop can kick-start the habits, but only daily practice keeps them alive.

Common Feedback Mistakes and How to Avoid Them

Most bad feedback is not malicious. It is well-intentioned and badly built, and the same handful of errors show up again and again. Naming them is the fastest way to stop making them.

The biggest is vagueness. "Be more professional," "show more initiative," "communicate better," none of it tells the person what to actually do. Vague feedback feels like guidance and functions like fog. The fix is the discipline SBI enforces: name the specific behavior in the specific moment, or say nothing. If you cannot point to what you saw, the comment is not ready to deliver.

The second is hoarding. Feedback saved up for a quarterly review arrives stale and overwhelming, a pile of grievances the person can no longer fix because the moments are long gone. Timely beats comprehensive. A small note today, while the event is fresh, does more than a thorough one next season. The third is the global verdict, the slide from "you did X" to "you are X," which we have already flagged as the failure SBI exists to prevent. Behavior is changeable; character feels fixed, and telling someone what they are invites defense, not growth.

A fourth runs the other way: never delivering hard feedback at all, out of a wish to keep things pleasant. Withheld feedback feels kind and is not. It denies people the information they need to improve and lets small problems harden into reputations. And a fifth, the most common of all, gets its own section below.

Feedback Scripts for Difficult Situations

The fifth mistake is the feedback sandwich, and it deserves a closer look because so many people were taught it as best practice. The recipe is familiar: open with praise, slip in the criticism, close with more praise. The theory is that the cushion softens the blow. In practice it does three unhelpful things. It buries the real message, so the receiver walks away remembering the compliments and missing the point. It makes the opening praise feel like a setup, training people to flinch whenever you say something nice. And it muddies the signal so badly that, often enough, the criticism does not register at all.

A clearer script exists, and it is DESC, from Bower and Bower's Asserting Yourself. Describe the behavior in neutral terms. Express how it affects you or the work. Specify the change you would like to see. State the Consequences, ideally the positive ones that follow if things change. Worked through a recurring lateness problem, it sounds like this: "In the last three stand-ups you've joined ten or fifteen minutes late (describe). When that happens we have to repeat decisions, which slows everyone down (express). I'd like you to be on the call at the start time (specify). If you are, we keep the meeting short and you stop missing the parts that affect your work (consequences)." Direct, specific, and free of the sandwich's evasions.

Hard feedback is, at bottom, a kind of difficult conversation, and the principles carry straight over. Stone, Patton, and Heen's Difficult Conversations makes the case that these talks go wrong when both sides argue about who is right instead of comparing what each of them saw and felt. The way out is to slow down, ask what the other person's version of events is, and treat the conversation as joint problem-solving rather than a verdict to deliver. For the moments that carry real weight, our guide to difficult conversations goes deeper, and the same broader habits that strengthen any exchange are worth building everywhere your work, covered in our overview of communication skills and the toolkit for high-impact communication. Scripts help. But the goal is never to recite a formula. It is to make sure the person across from you walks away knowing exactly what happened and what to do next.

Frequently Asked Questions

CommunicationAbility is reader-supported and independent, accepts no sponsorship or paid placement, and this guide is general professional-development information, not a substitute for professional, counseling, or mental-health advice. Terms apply.

Last reviewed: July 15, 2026