Skip to content
Kuza Ndoto Academy

Giving Feedback That Actually Helps: The SBI Model in Practice

A simple, respected structure for feedback that people can hear, understand and act on, with scripts you can use.

Leadership9 min read11 November 2026
A professional explaining a point in a meeting
By Kuza Ndoto Editorial · Photo: Pexels

Most of us have received feedback that left us confused, defensive or simply unchanged. "Good job." "You need to be more professional." "That presentation was not it." None of these tell you what to repeat or what to fix. Feedback is one of the most valuable things one person can give another, but only when it is clear enough to act on. This article teaches a simple, widely respected structure for doing exactly that, with scripts you can adapt for classmates, colleagues and even your boss.

Why most feedback fails

Feedback means information about how someone's actions affected a result or another person, shared so they can improve or keep doing what works. When it fails, it usually fails for one of three reasons.

  • It is vague. "Be more proactive" sounds meaningful, but the listener has to guess what you saw and what you want instead. Most people guess wrong, or do not try.
  • It is judgemental. "You are careless" is a verdict about who someone is, not information about what they did. People defend their identity far harder than they defend a single action, so judgement triggers defensiveness instead of learning.
  • It is late. Feedback about a meeting from six weeks ago is hard to use. Details have faded, the moment to adjust has passed, and the person may wonder why you waited.

The fix for all three is the same: describe a specific moment, describe what the person actually did, and explain why it mattered. That is the heart of the SBI model.

The SBI model, step by step

SBI stands for Situation, Behaviour, Impact. It was developed by the Center for Creative Leadership, an organisation that researches and teaches leadership. The idea is simple: good feedback has three parts, delivered in order.

  1. Situation. Anchor the feedback to a specific time and place, so the other person knows exactly what you are talking about. "In Tuesday's client meeting..." or "In the group report you submitted last night..."
  2. Behaviour. Describe what the person did, in terms a video camera could record. Not "you were rude", but "you interrupted Achieng twice while she was presenting". Observable behaviour is hard to argue with and easy to change.
  3. Impact. Explain the effect that behaviour had on you, the team, the work or the result. "...and she did not finish her point about the budget, so the client left without hearing it." Impact answers the question "why does this matter?"
Key idea

SBI separates what happened from what you think about the person. By describing a specific situation, an observable behaviour and its real impact, you give someone information they can use rather than a judgement they have to defend against.

Adding a forward-looking request

SBI explains what happened. To help the person improve, it often helps to add a fourth element: a clear, forward-looking request or question. For corrective feedback, this might be "Next time, could you hold your questions until she finishes?" Or, to invite their view: "What do you think would help in the next meeting?" Asking a question often works better than giving an instruction, because the person helps shape the solution and is more likely to own it.

Scripts you can use

SBI works for both positive feedback (reinforcing what someone should keep doing) and corrective feedback (helping someone change something). Many people only give feedback when something goes wrong, but specific praise is just as useful. "Good job" tells someone nothing; SBI praise tells them exactly what to repeat.

Worked example

Here is the same structure applied to four common situations. The names are illustrative.

  • Positive, to a classmate. "In yesterday's group presentation (situation), you put all our data into one clear chart and explained it in under two minutes (behaviour). The lecturer understood our main finding straight away and asked follow-up questions instead of being confused (impact). Could you show me how you built that chart? (request)"
  • Positive, to a colleague. "When the system went down on Thursday afternoon, you called each affected customer and told them when to expect an update. Two of them mentioned they appreciated being kept informed, and nobody escalated a complaint. Thank you. I would like to use your approach as our standard."
  • Corrective, to a teammate. "On our last two group assignments, your sections arrived on the morning of the deadline. That left no time to check them, and we lost marks for the sections not connecting. For the next one, could we agree to have drafts ready two days before the deadline? What would make that workable for you?"
  • Corrective, to someone you supervise. "In this morning's stand-up meeting, when I asked for the weekly figures, you said they were 'almost done'. I had promised them to the director at ten, so I had to ask her for more time. Next time something is running late, please tell me the day before, so I can plan around it. Is anything making those figures hard to finish on time?"

Notice what is missing from these scripts: labels like "lazy", "unprofessional" or "amazing". Every statement describes something the listener can recognise and either repeat or adjust.

Try this

Before giving feedback, write the three parts on paper or in your notes app. If you cannot name a specific situation, you are not ready. If your "behaviour" line contains an adjective about the person's character, rewrite it as an action you saw. If you cannot state the impact, ask yourself whether the feedback really matters.

Timing and setting

Good structure delivered at the wrong time can still go badly. A few practical guidelines help:

  • Give it soon. Aim to share feedback within a day or two, while details are fresh.
  • Praise in public, correct in private. Positive feedback in front of the team can be motivating (though some people prefer private thanks, so learn individual preferences). Corrective feedback should almost always be one-to-one.
  • Check the moment. Asking "Do you have five minutes? I wanted to share something about yesterday's meeting" gives the person a chance to be ready, and avoids catching them just before an exam or a deadline.
  • Keep it to one or two points. A list of ten corrections overwhelms. Focus on what matters most.

Receiving feedback well

Learning to receive feedback is as important as learning to give it, and it is what makes people willing to give you honest feedback again. When someone shares feedback with you:

  1. Listen fully before responding. Resist the urge to explain or defend yourself while they are still speaking.
  2. Ask clarifying questions. If the feedback is vague, use SBI to draw out details: "Can you tell me which meeting you are thinking of, and what I did that came across that way?"
  3. Thank them. Giving feedback takes effort and some courage. "Thank you for telling me" costs nothing and keeps the door open.
  4. Decide what to do with it. You do not have to agree with every piece of feedback. Take time to reflect, look for patterns across several people, and act on what rings true.
  5. Close the loop. A week or two later, tell the person what you changed. This shows respect and builds trust.
Watch out

The most common mistake when receiving feedback is to argue about the details ("It was not twice, it was once") while missing the main message. Even if some facts are slightly off, ask yourself what is true in what you are hearing.

Giving feedback upward

Giving feedback to a manager or a lecturer feels risky, especially early in your career. It can still be done well, and good managers value it. The key is to stay respectful, be specific and frame the feedback around shared goals.

  • Ask permission first. "Would it be helpful if I shared an observation about how the project briefings are working for me?"
  • Focus on impact on your work. "In the last two team briefings, the deadlines were shared verbally at the end. I missed one of them and only realised when the report was due. Would it be possible to also put deadlines in the group email?"
  • Offer, do not demand. Make suggestions, not instructions, and accept that the final decision is theirs.
  • Choose your moment. A scheduled one-to-one or a lecturer's consultation hours are better than a corridor or a crowded staffroom.

With a lecturer, the same approach works: "In this week's lecture, the slides moved quite fast through the worked examples, and several of us could not copy the steps. Would it be possible to share the slides afterwards?" That is specific, polite and easy to say yes to.

Respect and cultural sensitivity in East African workplaces

Feedback models often come from contexts where direct speech is the norm. In many East African workplaces, respect for age, seniority and hierarchy is strongly valued, and public disagreement with an elder or a senior colleague can cause real embarrassment. SBI still works well here, because it is built on facts rather than criticism, but you may need to adapt your delivery:

  • Use respectful openings. Phrases that acknowledge the other person's position, and greetings before business, set the right tone.
  • Prefer private conversations for anything corrective, and be especially careful never to correct a senior person in front of their juniors.
  • Soften without blurring. You can be gentle in tone ("I may have misunderstood, but...") while keeping the situation, behaviour and impact clear. Politeness and clarity are not opposites.
  • Read the relationship. Feedback lands best where some trust already exists. If you are new, invest in the relationship before offering upward feedback.

Cultures differ between organisations and individuals too, so observe how respected people in your workplace handle difficult conversations, and learn from them.

Clear feedback is a form of respect: it assumes the other person can use the truth to grow.

Key takeaways

  • Feedback usually fails because it is vague, judgemental or late.
  • The SBI model, from the Center for Creative Leadership, structures feedback as Situation, Behaviour and Impact, keeping it specific and factual.
  • Add a forward-looking request or question to turn feedback into a plan.
  • Use SBI for praise as well as correction, so people know exactly what to repeat.
  • Receive feedback by listening, clarifying, thanking and closing the loop.
  • Upward feedback works when it is invited, specific, private and framed around shared goals, delivered with the respect your workplace culture expects.

Keep reading