Giving Feedback That Lands

You've been sitting on it for two weeks. Someone on your team keeps doing the thing, and every time it happens you tell yourself you'll say something, and every time you don't. The conversation plays out in your head and it always goes badly. They get hurt, or defensive, or they nod and change nothing. So you wait. And the longer you wait, the bigger and stranger the whole thing gets.

If that's familiar, you're in good company. Giving feedback is one of the most avoided tasks in any workplace, and it has almost nothing to do with whether you're right. You can be completely correct about what needs to change and still have the conversation blow up in your hands. The problem is rarely the content. It's the delivery, and the state the other person is in when they hear it.

Why honest feedback so often backfires

Here's something worth knowing before you open your mouth. To the brain, criticism from someone who matters to you registers a lot like a physical threat.

Researchers at the NeuroLeadership Institute describe it this way: we're highly sensitive to information that feels like a hit to our status or our standing in a group, and when that threat fires, it can shut down the very thinking you're hoping to engage. The person across from you stops being able to take in your carefully chosen words. They're not being difficult. Their alarm system is louder than your voice.

This is the trap. The more pointed and surprising your feedback, the more likely it is to trip that alarm, and the less likely it is to actually land. You can win the argument and lose the behavior change. Most of the skill in giving good feedback is really about keeping the other person's threat response quiet enough that they can hear you at all.

Name the behavior, not the person

The single most useful shift is to talk about what someone *did*, not who they *are*.

"You're disorganized" is a verdict on a person's character. There's nothing to do with it except argue. "The deck went out at 11pm the night before the client call, so I didn't have time to review it" is a description of a specific thing that happened. One invites a fight. The other invites a fix.

The Center for Creative Leadership built a simple, sturdy structure around this idea, and it's worth borrowing. They call it SBI, for Situation, Behavior, Impact:

• Situation. Anchor it to a specific moment. "In yesterday's standup" beats "lately" or "you always." Vagueness is what makes feedback feel like a character attack, because the other person can't point to the actual event and so they assume you mean all of them, all the time.
• Behavior. Describe what you observed, as plainly as a camera would have caught it. Facts, not interpretations. "You cut Priya off twice while she was presenting," not "you were rude."
• Impact. Say what happened as a result, especially the part the person couldn't see. "Priya didn't finish her point, and we moved on without the one number we actually needed."

That last piece matters more than people expect. Most of the time, the person had no idea their behavior caused the problem you're describing. They weren't being careless on purpose. They simply couldn't see the wake their actions left behind. When you show them the impact instead of pronouncing a judgment, you give them new information rather than a sentence to defend against.

Ask before you tell

There's a move that sounds almost too small to matter, and it changes the whole temperature of the conversation. Before you deliver your verdict, ask the person for their own read.

"How do you think the client call went?" "What's your sense of how the launch landed?" Often they already know. People are usually more aware of their own missteps than we assume, and when they name a problem themselves, there's no threat to defend against, because no one is attacking them. They're examining it with you.

This is one of the steps the NeuroLeadership researchers recommend for exactly that reason. Asking first hands the other person a measure of control in a moment where they'd otherwise feel powerless, and control is one of the things the brain is scanning for when it decides whether to treat a conversation as safe or dangerous. You're not being soft by asking. You're lowering the alarm so the real conversation can happen.

Point forward, not just back

Feedback that only relitigates the past gives someone nothing to do with their hands. They can feel bad about yesterday, but they can't change it.

So spend most of your energy on what comes next. After you've named the behavior and its impact, turn toward the future together. "Next time, what would help you catch this earlier?" "Here's what I'd love to see on the next draft." The aim is for the person to walk away with a clear, doable picture of a better version, not just a clear picture of how they fell short. People who feel they have a real path to do better tend to do better. People who feel only judged tend to dig in or shut down.

The conditions that make any of this work

None of these techniques save you if the underlying relationship is cold. Feedback lands in proportion to the trust it's delivered on.

The Harvard researcher Amy Edmondson spent decades studying what she named psychological safety: the shared sense in a team that you can speak up, admit a mistake, or hear a hard truth without being humiliated or punished for it. It's easy to mistake this for niceness, and it isn't that. As HBR's Amy Gallo puts it, psychological safety is precisely what makes candor possible. The teams that handle feedback best aren't the ones that avoid friction. They're the ones where people trust that the friction is in service of the work, not a weapon aimed at them.

A few things build that trust, in the small moments long before any hard conversation:

• Give feedback regularly, in low stakes, so it isn't a rare and terrifying event. A culture where small adjustments happen all the time never has to stage the dreaded Big Talk.
• Be at least as specific with praise as with criticism. "Good job" teaches nothing. "The way you slowed the meeting down to make sure everyone understood the change was exactly what we needed" tells someone precisely what to do again.
• Ask how people want to receive feedback, and remember the answer. Some want it on the spot. Some need a day. Honoring that is a quiet way of saying you're on their side.
• Own your own part out loud. "I should have flagged this two weeks ago, that's on me" makes you safe to be honest with, and it models the exact behavior you're hoping to see.

When the conversation is bigger than a technique

Some conversations are about more than a missed deadline. If someone's performance has fallen off a cliff, if they seem to be struggling in a way that looks like more than a bad week, or if the issue touches conduct that affects other people's safety, that's no longer a coaching chat to handle alone. Loop in your manager or your HR partner, and do it sooner than feels comfortable.

And watch for the moment when what you're seeing isn't a skills gap at all. Sometimes a performance problem is the visible edge of something heavier going on in a person's life. You're not their therapist, and you shouldn't try to be. But you can be a human being. You can say you've noticed things seem hard lately, that you're in their corner, and that there's no shame in reaching for real support. Then point them toward it, an employee assistance program, a doctor, a counselor, and let the professionals do the part that isn't yours to carry.

The goal of feedback was never to make someone feel small. It was to help them do work they can be proud of, with you, on a team where the truth is survivable. Get the delivery right and that's what the hard conversation actually becomes: not a punishment, but a door someone can walk through.

Sources

• Center for Creative Leadership, Use the Situation-Behavior-Impact (SBI) Feedback Model
• NeuroLeadership Institute, Use This 3-Step Approach to Give Better Negative Feedback
• Harvard Business Review, What Is Psychological Safety? (Amy Gallo)
• Harvard Business School, Creating Psychological Safety in the Workplace (Amy Edmondson)