Giving & Receiving Feedback

Why Feedback Is the Most Underused Communication Skill

Here is the fact that should unsettle anyone who manages people: feedback does not reliably work. When Avraham Kluger and Angelo DeNisi pooled 607 effect sizes for their 1996 meta-analysis in Psychological Bulletin, the headline was an average improvement — feedback helped, on the whole. But buried in the same paper was the finding that's stuck with me for years. In more than a third of the studies they reviewed, feedback made performance worse. Not flat — worse. The thing we hand out to fix problems was, a third of the time, creating them.

I have spent years editing communication content for communicationability, and the question readers raise most often is not "what should I say." It's "why did it backfire last time." Kluger and DeNisi give part of the answer. When feedback pulls a person's attention toward their sense of self rather than the task in front of them, it stops teaching and starts threatening. That distinction — task versus self — sits underneath every framework here.

It also explains why I'm skeptical of the advice that you just need to give more feedback. More of something that fails a third of the time is not a plan. The fix is structure and tone. Kim Scott, the former Apple and Google executive who wrote Radical Candor in 2017, framed the tone half: you have to care personally and challenge directly at the same time. Drop either axis and the feedback either wounds or evaporates. The structure half is what the Center for Creative Leadership, Marshall Goldsmith, and a handful of researchers worked out, and the mechanics they landed on hold up everywhere: good feedback is specific, lands close to the event, targets what someone did rather than who they are, and rides on a relationship the person trusts.

The SBI Feedback Model: Situation, Behavior, Impact

Start with the framework I reach for first. SBI comes out of the Center for Creative Leadership and stands for Situation, Behavior, Impact. The whole trick is that it forces you to report what happened instead of grading the person — the difference between feedback that gets heard and feedback that gets argued with.

Situation. Pin the feedback to one moment. "In Tuesday's project review, right after the budget slide" beats "lately." Vagueness invites the oldest dodge in the book — "When? I don't do that" — and a timestamp closes that door before the person can open it.

Behavior. Describe what a camera would have caught. "You checked your phone four times while the client was talking" is behavior; "you were disrespectful" is a verdict. People can't argue with the camera, but they'll fight your verdict all day — and the fight is where the conversation dies.

Impact. Say what the behavior did. "The client lost their thread twice, and afterward pulled me aside to ask whether the team was actually committed." Impact is the part people care about — it connects their action to a consequence they'd rather avoid. Skip it and the feedback floats free.

Here's what most people miss: SBI works just as well for praise, and using it for praise might matter more. "During the board presentation, you had a clean answer for every question, which got us the green light for phase two" lands; "great job" does not. Run the framework only when something goes wrong and you've trained your team to dread it. For more on how leaders use feedback well, see our leadership communication guide.

The mistake I see most is the jump straight from Situation to Impact with the Behavior step left blank. "In yesterday's meeting you were unprofessional" is not SBI; it's a judgment wearing a framework's clothes. Make yourself name the observable thing — interrupted, talked over, arrived late — and the conversation changes character on the spot.

Comparing Feedback Frameworks

No single framework fits every conversation. Here is how the main ones stack up.

Feedforward: The Future-Focused Alternative

Marshall Goldsmith, the executive coach who coined the term, makes a simple case: you can't change the past, so why spend the whole conversation litigating it? Feedforward drops the grade and offers a suggestion for next time. Not "your presentation had no data," but "next time, open with two numbers that make the stakes obvious." Same point, different reception.

The reason it works lines up with what Kluger and DeNisi found. A suggestion about the future doesn't put your sense of self on trial, so the threat response stays quiet and the person can listen. Buckingham and Goodall made a related argument in their 2019 Harvard Business Review piece "The Feedback Fallacy," questioning how much corrective feedback teaches at all.

That said, I don't buy feedforward as a total replacement, and neither did Goldsmith. When a behavior has caused real harm, a hopeful note about next time doesn't cut it — that's SBI territory. The communicators I trust most carry both: feedforward for coaching, SBI when a specific past action has to be addressed head-on. Folding feedforward into your regular one-on-ones, the way our workplace communication guide describes, turns improvement into a habit instead of an event.

How to Receive Feedback Without Defensiveness

Receiving feedback well is harder than giving it, and I'd argue it's the skill that separates people who keep growing from people who quietly plateau. Douglas Stone and Sheila Heen, both of the Harvard Negotiation Project, laid out the mechanics in their 2014 book Thanks for the Feedback. They name three triggers that make feedback hard to swallow. A truth trigger fires when you think the content is just wrong. A relationship trigger fires when you don't think this person has any business telling you. An identity trigger — the worst — fires when the feedback rattles your picture of who you are. Figure out which one went off, because each demands a different response and most of us treat all three the same.

Step 1 — Buy yourself five seconds. Breathe. Don't explain, don't justify, don't counter. You have one job: hear the sentence all the way to its period before your mouth opens.

Step 2 — Mine it for data. Even feedback delivered badly usually has something real inside it. Reach past the clumsy wrapping for the observation and the impact. If it's too vague to use, ask: "Can you give me a specific example?" You're not surrendering; you're gathering.

Step 3 — Say thank you, and mean the narrow version of it. Thanking someone is not agreeing with them. It's acknowledging that telling you the hard thing took nerve. "Thanks for telling me — I want to sit with it" buys you time to think instead of react.

Step 4 — Decide later, not now. You don't owe anyone an instant verdict. Walk away, weigh what fits and what doesn't, and choose what to act on. Not all feedback is right — but the reflex to swat it away guarantees you'll miss the piece that was. The active listening techniques in our dedicated guide earn their keep when the urge to stop listening and start defending peaks.

Who struggles most with this? Often the strongest performers — their competence has become part of their identity, so a note on their work reads as an attack on their character, a textbook identity trigger. The fix is boring and it works: breathe, ask one clarifying question, thank the giver, and practice until it runs on its own.

Giving Feedback Across Power Dynamics

Add a power gap and the difficulty jumps. Telling your boss something, hearing it from someone who reports to you, trading notes with a peer you're quietly competing with — these aren't the same skill, and treating them as one is why so many go sideways.

Going up the ladder, frame everything as a shared problem, never a personal failing. "I've noticed something I think is costing the team, and I wanted to flag it" is an opening most managers will take. Then lean hard on impact: "When priorities shift mid-sprint, we lose a day or two re-planning, and it's eating into our delivery dates" names a consequence without accusing the boss of being scattered. You're describing weather, not assigning blame.

Hearing it from below is where leaders quietly fail, because nothing forces them to listen. The power gap makes it effortless to nod, file it, and do nothing. The ones who get this right ask for upward feedback out loud, take it without flinching, and — the part that matters — visibly change something. A team that watches its feedback vanish starts telling the boss whatever keeps the peace.

Peer to peer goes smoothest when nobody has to invent the moment. Give a team a shared vocabulary — SBI works well — and bake feedback into things that already happen, like retrospectives, and the awkwardness of grading a colleague mostly evaporates. For teams spread across time zones, our remote communication guide covers the extra hazard of feedback over Slack and video, where tone goes missing and a neutral note reads as a cold one.

Building a Feedback Culture on Your Team

Your personal feedback skills only travel so far. They pay off inside a team that practices the stuff and wither inside one that doesn't. The foundation has a name. In 1999, Amy Edmondson published a study of 51 work teams in Administrative Science Quarterly and introduced "psychological safety" — the shared belief that you won't be punished for speaking up. She tied it directly to whether teams learned: no safety, no honest feedback, no learning.

There's a neuroscience layer underneath, too. David Rock's SCARF model, published in the 2008 NeuroLeadership Journal, argues that the brain treats a social threat — a hit to your status, a loss of certainty — with the same circuitry it uses for physical danger. That's the mechanism behind the Kluger-DeNisi backfire: feedback that threatens status doesn't just sting, it shoves the brain into defense and shuts learning off at the source.

So model it. Ask for feedback out loud, take it without getting prickly, and say what you're working on fixing. That visible vulnerability tells everyone watching that feedback is safe to give. Then hand the team a shared framework, so "can I give you some SBI feedback?" already tells the other person the shape of what's coming.

One caution from watching these rollouts up close. Radical Candor gets misused constantly, and Kim Scott has said as much — people latch onto "challenge directly" and skip "care personally," so it becomes a license to be blunt. Scott even named the failure: obnoxious aggression. If you run a feedback program, spend the bulk of the time on the caring half — the candor half is the part people find easy and overdo.

Build feedback into the machinery instead of leaving it to whoever feels brave that day — onto the one-on-one agenda, into a quarterly peer exercise, into retrospectives. The more ordinary it becomes, the less it reads as an alarming event. And when someone delivers something hard with care, say so out loud; you get more of whatever you're seen to reward. For the broader skills underneath all of this, see our enhancing communication skills guide and our workshop resources.

Common Feedback Mistakes and How to Avoid Them

The traps here are predictable, which is the good news. The worst one is hoarding. You let small things slide, they pile up, and they come out as a performance review or a frustrated outburst that's really about six weeks of unsaid feedback. By then the moment is cold — the person can barely remember the meeting, and the chance to fix anything in real time is gone. Close to the event, feedback is a nudge; six weeks late, it's an ambush.

Then there's the character mistake. "You're disorganized" is a verdict on the person, and it trips the identity trigger Stone and Heen warned about. "The project plan was missing three milestones and two deliverables had the wrong dates" points at the work. One is fixable by Friday; the other feels like a diagnosis, and nobody fixes a diagnosis.

Vagueness fails differently. "You need to communicate better" hands the person nothing to do. Compare: "Your updates in the last two standups each ran five minutes long and squeezed everyone after you. Try capping yourself at three points." The first is a shrug, the second a plan. None of this argues against hard feedback — Zenger Folkman surveyed 8,542 people and 92% said negative feedback, delivered well, improves their performance. People can take the truth; they just can't take a fog.

Last one: don't correct people in public. Public criticism humiliates instead of teaching, and it tells the room that feedback is a thing to fear. The reverse holds for praise, which lands harder with an audience. So praise in public, redirect in private. For more on these dynamics, see our guides on conflict resolution communication and powerful communication skills.

Feedback Scripts for Difficult Situations

Frameworks get you most of the way, but a few situations are hard enough that it helps to have the words ready. Here are openers I've seen hold up — scaffolding, not lines to read off a card.

When it's a pattern, not a one-off: "There's something I keep seeing that I'd like to talk through. Three times in the last couple weeks — [the specific moments] — and I'm raising it because it's starting to affect [the specific impact]. How does it look from where you sit?" That closing question turns a lecture into a conversation.

When they get defensive: "I can tell this is landing hard, and that's genuinely not what I'm going for. I'm bringing it up because I want you to do well here. Can we put the past part down and talk about what we do next?" Naming the defensiveness gently lowers the temperature faster than pretending you don't see it.

When you're prying feedback out of a manager who won't give it: "I'm trying to get better at [the specific skill]. If you had to name one thing I could do differently in [the specific setting], what would move the needle most?" Asking for one thing, not "any feedback," makes it easy to answer. A wide-open request gets a polite nothing.

When you're handing a peer feedback and have no authority to: "Something from our last project's been on my mind, and I think it could make the next one sharper. Open to hearing it?" Asking first hands them control of the moment, and people defend far less when they said yes.

Notice what these share. They're specific, they point at a shared goal rather than a grievance, they invite the other side in, and they aim forward. Borrow the bones, change the words to sound like you. And remember that delivery is half the message — which is why the nonverbal communication side is worth its own study.

Frequently Asked Questions

What is the SBI feedback model?

It's a three-part structure from the Center for Creative Leadership — Situation, Behavior, Impact — and the point of it is to keep you reporting facts instead of grading the person. You name the moment, you describe what they actually did, and you say what that did in turn. So: "On yesterday's client call, you cut in three times while they were explaining their worry, and they got visibly frustrated and ended the meeting early." Notice there's no "you were rude" anywhere in that. The power is in what it leaves out — the verdict.

How often should managers give feedback to employees?

More often than once a year, that much is clear. Gallup's 2022 data found that people who get daily feedback are 3.6 times more likelier to feel motivated to excel than people who only hear from their manager at the annual review. I wouldn't treat that as a quota, though. The realistic rhythm is small, in-the-moment notes when you actually see something, a regular one-on-one that covers both what's working and what's developing, and a quarterly conversation that connects the dots. The annual-review-only approach is the single most common way managers get this wrong.

How do you give negative feedback without damaging the relationship?

Aim at the work, never the character. "The report had several data errors" is repairable; "you're careless" is an insult with no exit. Do it privately, do it soon, and lean on a structure like SBI so you stay on the facts. One underrated move: ask a question before you deliver the verdict, because you might be missing context that changes the whole picture. Tie it to something you both want — "I want this launch to go well" — and finish with one concrete ask, not a limp "just do better."

What is feedforward and how is it different from feedback?

Feedforward is Marshall Goldsmith's term, and the whole idea is to skip the autopsy. Rather than grading what already happened, you offer a suggestion for next time — not "your slides had no data" but "next time, open with two numbers that make the stakes land." Because it doesn't ask the person to defend a past they can't change, the defensiveness never fires. That's its real advantage. I still think some things have to be named directly, but for ordinary coaching it's gentler and it tends to stick.

How do you receive feedback without becoming defensive?

Honestly, the trick is buying a few seconds before you say anything. Breathe, let the sentence finish, and resist the reflex to explain yourself. Then go looking for the actual data underneath the delivery, and if it's too vague, ask for a specific example. Say thank you even when you disagree — you're rewarding the courage it took, not endorsing the content. Decide later what's worth acting on. The move that helps most is separating what you did from who you are; a note on your work is not a ruling on your worth.

Why does the feedback sandwich not work?

Because people remember the opening and the close of a conversation, and the sandwich buries the message in the middle — the one spot guaranteed to get forgotten. Wharton's Adam Grant has made the case for dropping it. There's a second cost too: once your team spots the pattern, every compliment starts to feel like the setup for bad news, so you've quietly poisoned your praise. Better to keep the two apart — run the recognition conversation as its own thing and the development conversation as its own thing, and let each be taken at face value.

How do you create a feedback culture on a team?

It starts with you going first. Ask for feedback in front of people, take it without bristling, and name something you're working to fix — that's what signals it's safe. Amy Edmondson's 1999 research called this psychological safety and tied it straight to whether teams learn. From there, give everyone a shared framework, and fold feedback into things that already happen, like retrospectives, instead of staging it as a dreaded event. The part people skip is the last one: act on what you hear, visibly. A team that sees feedback change nothing stops bothering to give it.

What are the biggest mistakes people make when giving feedback?

Top of the list is waiting too long, until the moment's cold and the person can't picture what you're describing. Close behind is making it about character instead of behavior, which trips the identity alarm and ends the listening. Then there's vagueness — "communicate better" gives nobody anything to do — and correcting people in public, which humiliates more than it teaches. A few quieter ones round it out: only showing up when something breaks, never circling back to notice the fix, and walking in certain your read of events is the only one. That last bit of arrogance does the most damage.

The frameworks here are for professional and personal development. For formal performance reviews tied to pay or promotion, follow your organization's established process. Read terms.

Last reviewed: 2026-05-24