How to give constructive feedback

Most feedback fails not because the message is wrong, but because it's vague, late, or aimed at the person instead of the behavior. Here's how to give constructive feedback that someone can actually use.

Constructive feedback has one job: to help someone do better next time, without making them feel smaller for having done it this time. That's a narrow target, and it's easy to miss in both directions — too soft and the message never lands, too sharp and they spend the conversation defending themselves instead of listening. The good news is that a simple structure gets you most of the way there.

Use a simple model: situation, behavior, impact

The most reliable framework is SBI — Situation, Behavior, Impact. You describe where and when it happened, what you observed, and what effect it had. Then you stop and let them respond.

• Situation — anchor it in a specific moment. "In yesterday's client call…"
• Behavior — describe what you actually saw or heard, not your interpretation of it. "…you answered the pricing question before the client finished asking it."
• Impact — name the consequence. "…and the client went quiet for the rest of the call, so we didn't hear their real concern."

The power of SBI is that it keeps you reporting facts rather than assigning traits. "You interrupted the client" is observable. "You're impatient" is a verdict — and people argue with verdicts.

Give it soon, not someday

Feedback decays. A point made the same day, while the details are fresh for both of you, is worth ten points made three weeks later in a review. Late feedback also feels like an ambush — the person had no chance to course-correct, and now they're hearing about a pattern they didn't know existed.

You don't need a formal meeting. A quiet two-minute word after the call usually beats a scheduled sit-down. The one exception: never deliver corrective feedback in front of others. Praise in public if you like, but correct in private, always.

Be specific enough to act on

"Be more proactive" is not feedback — it's a mood. The test is simple: could the person do something differently tomorrow based on what you said? If not, you haven't been specific enough. Replace abstractions with the concrete behavior you want to see.

"Communicate better" tells someone nothing. "Send the status update on Friday afternoon instead of Monday morning, so the team can plan their week" tells them exactly what to do.

Separate the behavior from the person

People can change what they do far more easily than who they are. Frame everything as a behavior and a choice, never as a fixed quality. "The report had three errors that the client caught" leaves room to improve. "You're careless" closes the door — and invites a fight.

Skip the "feedback sandwich," where you bury a criticism between two compliments. People see it coming, the praise reads as fake, and the actual message gets lost in the padding. Be warm in your delivery and direct in your content. Those aren't in tension.

A worked example: before and after

Say a report, Maya, has been turning up late to the team's morning stand-up and it's holding everyone up.

Before (vague, personal, no path forward):

"Maya, you've got to take this more seriously. People are noticing you're not really committed to the team."

This is a character judgment with no specifics. Maya can't tell what "seriously" means, "people are noticing" is anonymous pressure, and there's nothing to actually do.

After (SBI, specific, forward-looking):

"In the last three stand-ups you've joined five to ten minutes late, so we've ended up repeating the updates for you, and we're starting the day behind. I wanted to flag it early — is something making 9:00 hard right now? If the time doesn't work, let's move it."

Same concern, completely different conversation. It's anchored in fact, it names the real impact, it treats Maya as someone with reasons rather than a flaw, and it ends with a genuine question instead of a sentence. You may learn she has a school drop-off that makes 9:00 impossible — in which case the problem was the meeting time, not her commitment.

Follow up

Feedback without follow-up is just a complaint. Close the loop: a week or two later, acknowledge the change if it happened. "The updates have been on time all week — thank you, it's made a real difference" tells the person the effort was seen and worth it. If nothing changed, that's useful information too, and now you're having a clearer second conversation rather than re-opening the first.

The habit that makes all of this easier is simply writing things down as they happen — the specific moment, the behavior, the impact. When you've captured the detail in the moment, you're never reconstructing a fuzzy memory weeks later, and your feedback stays concrete instead of drifting into "lately I feel like…"