← Back to articles
📐 SBI model Situation–Behaviour–Impact
As soon as possible Feedback degrades with time
🔄 Both directions Up, down, and sideways
🎯 Behaviour, not person The golden rule

Why Most Feedback Fails

Most professional feedback fails to change anything. Not because people don't try, but because they don't know how to give it well — and neither do the people receiving it.

Common failure modes on the giving side:

  • Too vague. "You need to communicate better" tells someone nothing actionable. What specifically? In which situations? With what effect?
  • Too late. Annual performance reviews are the wrong format for developmental feedback. Delivered months after the event, it can't be acted on and creates defensiveness instead of learning.
  • Too personal. Feedback about character or personality ("you're disorganised") rather than specific behaviour triggers defensiveness and rarely changes anything.
  • Too sandwiched. The "feedback sandwich" — compliment, criticism, compliment — is so widely used that people have learned to filter out the bread and brace for the meat. It dilutes both the positive and the corrective message.

Common failure modes on the receiving side:

  • Defending or explaining rather than listening
  • Taking it personally rather than treating it as information
  • Nodding along without any real intent to change
  • Dismissing it entirely when it's uncomfortable

The SBI Model: A Framework That Works

The Situation–Behaviour–Impact model, developed by the Centre for Creative Leadership, is the most practical feedback framework for most professional contexts. It works because it's concrete, observable, and keeps the focus on behaviour rather than character.

  • Situation: When and where did this happen? "In this morning's client presentation..." "During last Tuesday's team meeting..."
  • Behaviour: What specifically did the person do or say? Observable, factual, not interpretive. "...you interrupted the client three times while they were explaining their concern..." "...you delivered the slide deck 20 minutes before the meeting started..."
  • Impact: What effect did that behaviour have — on you, on the team, on the client, on the project? "...which made the client visibly frustrated and may have damaged the relationship." "...which didn't give me enough time to review it and meant I wasn't prepared."

The power of this model is in the Impact step. Many people know what they did wrong but don't fully understand the consequence. When impact is stated clearly and non-judgmentally, it creates the intrinsic motivation to change.

SBI for positive feedback

The model works equally well for reinforcing good behaviour — and most organisations dramatically underuse positive feedback. "In today's presentation [S], the way you handled the difficult question from the finance director by pausing, acknowledging it, and then redirecting to the data [B] completely changed the room's energy and I could see the director visibly relax [I]." This is far more useful than "great job today."

Giving Feedback Well

Timing

Give feedback as close to the event as possible — not in the heat of the moment, but within 24–48 hours. The specific event is still fresh; you can both refer to it clearly. Waiting weeks or months creates a situation where the person can't remember the context and experiences the feedback as an ambush.

Setting

Difficult feedback should always be delivered in private — never in front of colleagues, never in a public forum. Positive feedback can be given publicly, and often should be — it signals what the organisation values and gives the person well-deserved recognition.

Intent

Before giving difficult feedback, check your intent. Are you giving this because it will help the person develop? Or are you venting, punishing, or establishing dominance? Feedback that comes from genuine care for the other person's development is received differently than feedback that comes from frustration.

One thing at a time

Don't give a list of five things to improve in one conversation. Pick the most important one. Multiple pieces of corrective feedback in one sitting overwhelm and demoralise. One clear message, well-delivered, is more effective than five points half-absorbed.

Receiving Feedback Well

How you receive feedback determines whether you benefit from it — and whether people continue to give it to you. Defensive or dismissive responses to feedback reliably result in people withholding it in future.

  • Listen to understand, not to respond. Resist the urge to explain, justify, or rebut while the other person is speaking. Let the full message land before you say anything.
  • Ask clarifying questions. "Can you give me a specific example?" or "What would you have liked to see instead?" turns vague feedback into actionable information.
  • Thank the person. Even if the feedback stings. Giving difficult feedback takes courage; acknowledging that encourages more of it.
  • Take time before responding to difficult feedback. "Thank you — I want to sit with this before I respond. Can we follow up tomorrow?" This is professional, not avoidant.
  • Separate the useful from the noise. Not all feedback deserves equal weight. Consider the source, the context, and the pattern. Feedback that arrives from multiple different people about the same thing deserves serious attention regardless of whether you agree in the moment.

Giving Feedback Upward

Giving feedback to your manager is genuinely difficult and underused. Most people find it too risky. In cultures where it's safe to do, it's enormously valuable — both for the manager's development and for the relationship.

  • Choose your moment. Ask if your manager is open to feedback before launching into it. "I have some thoughts on how our team meetings have been running — would you be open to hearing them?"
  • Focus on specifics, not patterns. "In last week's project review, when you cut me off before I'd finished explaining the blocker, I wasn't able to give you the full picture and we made a decision without some important context" is actionable. "You never let me finish" is not.
  • Frame it as an offering, not a complaint. "I want to raise this because I think it would help our working relationship" lands better than "This is something that bothers me."
  • Accept that it may not land immediately. Feedback to a manager sometimes takes time to be received well. Plant the seed and let it sit.

Building a Feedback Culture

If you're a manager, the frequency and quality of feedback on your team is one of the most important variables in team performance. Teams that give each other regular, honest, respectful feedback outperform teams that don't — consistently.

  • Model it yourself. Ask your team for feedback on how you're managing. Then act on what you hear. This single behaviour signals more about psychological safety than any culture initiative.
  • Create regular feedback rituals. Brief retrospectives after projects, explicit space for "what could have gone better" in team meetings, structured feedback in one-on-ones. Rituals normalise feedback so it's not a special, scary event.
  • Reward honest feedback even when it's uncomfortable. If someone raises a difficult truth and experiences a negative consequence, the message to the team is clear: don't do that. If they experience a positive response, the message is equally clear.

FAQ

What if the person gets emotional during feedback?

Pause and acknowledge it: "I can see this is landing hard — do you want to take a moment?" Emotion is information. It may mean the feedback hit something important, or it may mean the delivery needs adjusting. Either way, giving space is usually the right call. Don't push through the emotion to finish the script.

How do I give feedback to someone significantly more senior than me?

Carefully, specifically, and by framing it as wanting to contribute to a better outcome rather than criticising. Start by checking if they're open to it. If the culture genuinely doesn't allow upward feedback, you may be more limited — but the relationship and your own standing are both improved by being willing to try.

Is written feedback better than verbal?

For developmental feedback, verbal is usually better — tone and body language carry important signals, and it allows for real-time dialogue. Written is useful for documenting and confirming what was discussed, or for very formal performance contexts. Email-only difficult feedback often reads as cold and is more easily misinterpreted.

What if I give feedback and nothing changes?

Give it once more, more specifically. If there's still no change, it becomes a performance conversation rather than a developmental feedback conversation — and that has a different format and different consequences. Feedback without consequences eventually becomes background noise.