How to give feedback that people actually act on

The problem is not that people cannot take feedback. It is that most feedback is too vague to act on.

When someone says "you need to improve your communication," what exactly are they being asked to do? Communicate more? Communicate differently? In writing? In meetings? With which audience? The person receiving the feedback walks away with a vague unease and no idea where to start.

Effective feedback is not about tone. It is about structure. A simple framework called SBI, Situation, Behaviour, Impact, turns a vague impression into something the other person can actually use.

Why most feedback does not land

Before the framework, it is worth understanding what makes feedback miss.

Most feedback fails for one of three reasons. It is too general ("you need to step up"). It describes character rather than behaviour ("you're not a team player"). Or it is delivered so long after the situation that the recipient has no memory of the specific moment you are describing.

All three of these patterns make the feedback impossible to act on. You cannot change a character trait you cannot identify. You cannot fix a problem that has no specific example. You cannot replay a moment you do not remember.

The SBI model

SBI stands for Situation, Behaviour, Impact. It gives feedback a structure that makes it specific, observable, and forward-looking, the three things that make it useful.

• Situation.Anchor the feedback to a specific moment. "In yesterday's client call" or "in the team retrospective on Tuesday." Not "sometimes in meetings" or "often with clients." If you cannot name the situation, you are not ready to give the feedback.
• Behaviour.Describe what you observed, not what you concluded or inferred. "You interrupted the client twice before they finished their question" is observable. "You were dismissive" is an interpretation. Stick to what actually happened.
• Impact.Connect the behaviour to its consequence. "The client went quiet after that, and I noticed they seemed reluctant to contribute for the rest of the call." This is the reason the feedback matters, it makes the stakes clear without making it personal.

Five examples: vague to specific

The clearest way to understand SBI is through rewrites.

Vague:"You need to be more proactive."
Specific:"In last week's project standup, the delivery risk had been visible for three days, but it wasn't flagged until I asked. When that happens, we lose the time to course-correct early, which puts more pressure on the whole team."

Vague:"Great presentation."
Specific:"When you opened with the client's own problem rather than with our solution, it changed the energy in the room. They leaned in immediately. That framing made everything that followed easier to land."

Vague:"You need to improve your writing."
Specific:"In the proposal you sent last Friday, the executive summary was four paragraphs before it got to the recommendation. Senior stakeholders usually stop reading before they get there. Moving the recommendation to the first sentence would make it land better."

Vague:"You're not a team player."
Specific:"In the last two sprint planning sessions, you pushed back on the estimates from the other developers without asking what was driving them. A few of them have mentioned feeling like their input isn't valued. I'd like to talk about what's behind that."

Vague:"You need to manage your time better."
Specific:"The last three deliverables came in on the day of the deadline or after. When that happens, the people waiting on your output cannot do their work either. What is getting in the way of earlier delivery?"

What to do after you share SBI

After you have described the situation, behaviour, and impact, stop. Ask the other person what they think.

This matters for two reasons. First, their response will tell you whether the feedback landed and whether there is context you are missing. Maybe they interrupted the client because the client was about to commit to something that would have caused a problem later. You did not know that. Now you do.

Second, inviting a response turns the feedback into a conversation rather than a verdict. People are more likely to act on something they helped shape than something that was delivered to them.

Once you have both spoken, close with a specific next step. Not "do better," but "next time that comes up, what would you do differently?" or "what would be helpful from me?" The more specific the closing action, the more likely something actually changes.

When to give feedback

As soon as possible after the situation, ideally within 24 to 48 hours. The longer you wait, the harder it is for the other person to connect the feedback to the specific moment. Their memory of it has already started to blur.

The one exception: if you or the other person are in an emotionally charged state, wait until things settle. Feedback delivered in frustration rarely lands well, no matter how well-structured.

Frequently asked questions

What is constructive feedback?

Constructive feedback is feedback that is specific, actionable, and forward-looking. It describes what happened and its impact, and points toward what to do differently. It is not the same as positive feedback, constructive means it gives the recipient something concrete to act on.

How do you give negative feedback?

Use the SBI model: describe the specific situation, the observable behaviour, and the impact it had. Avoid interpreting motives. Then invite the employee to share their perspective before agreeing on what changes. Feedback framed as an observation rather than a verdict is far more likely to be heard.

How often should you give feedback?

As often as there is something worth saying. Most managers give too little feedback, not too much. Feedback given close to when the situation happened is more useful than feedback stored up for a scheduled performance review.

What are examples of good feedback at work?

Good feedback is specific, tied to a situation, and describes impact. "When you flagged the budget risk early in the conversation, it gave the client time to process it before we asked for a decision, they seemed much more comfortable by the end" is good feedback. "Great job in that meeting" is not.