AgileKoc ToolsHow to Give Constructive Feedback (SBI Model + Real Examples)
Practical SBI feedback guide with real examples, scripts, common mistakes, and a 7-day practice challenge for modern teams.
Why most feedback fails
Most people do not avoid feedback because they do not care. They avoid it because they have seen feedback go wrong.
- "You're not proactive." (Translation: I'm annoyed, but I cannot explain why.)
- "Great job!" (Translation: I'm being polite, but you will not learn anything.)
- "You need to improve your communication." (Translation: I'm about to start a conflict.)
Constructive feedback is a real career advantage, not because it is nice, but because it is clear without being cruel.
This guide gives you a simple structure (SBI), scripts you can reuse, real examples, and the mistakes that make feedback backfire.
Why the SBI model works
SBI stands for Situation, Behavior, Impact.
- Situation: When and where did it happen?
- Behavior: What did the person do (observable, not interpretation)?
- Impact: What was the result for you, the team, or the work?
SBI works because it fixes the #1 feedback problem: people speak in labels instead of facts. Labels create defensiveness. Facts create conversation.
A true story: the feedback that almost made someone quit
A product designer (call her Elif) had just joined a team. A senior engineer told her, "You need to be more strategic." She did not know what that meant and felt lost.
Later, the manager coached the engineer to give SBI feedback instead:
- Situation: "In Monday's roadmap review with Sales..."
- Behavior: "...you presented three design options without recommending one."
- Impact: "Sales left confused, and we did not get a decision. It pushed the launch discussion to next week."
Same message, completely different effect. SBI turned a vague judgment into a solvable problem.
The SBI formula you can copy (plus one extra step)
- Situation: When we were in... / Yesterday during...
- Behavior: I noticed you... (observable action)
- Impact: The impact was...
- Request: Next time, could we...? (optional but powerful)
That fourth step makes feedback feel helpful, not just critical.
Good feedback vs bad feedback (same meaning, different result)
- Bad: "You're not proactive in meetings."
- SBI: "In the last two sprint reviews, you did not share your concerns about scope changes until after the meeting. We made decisions without key info and reopened them later. Next time, can you raise the risk in the meeting, even as a quick question?"
One triggers defensiveness. The other triggers improvement.
When to give constructive feedback
Best timing is close enough to be accurate, not so close it becomes emotional.
- If emotions are high, wait 30-120 minutes.
- If it is a pattern, do not wait months.
- If it affects delivery, do not wait until performance review season.
- Remote teams tip: sensitive topics should start voice or video first, then be summarized in writing.
Real SBI examples you can steal
- "You interrupted me."
Situation: In today's refinement call... Behavior: you spoke over me twice while I explained edge cases. Impact: I lost my train of thought and the team missed key details. Request: Next time, can you jump in after I finish? I'll keep it short. - "Your Slack messages sound harsh."
Situation: Yesterday in the #release channel... Behavior: your message was "This is wrong. Fix it now." Impact: it created stress and people stopped asking questions publicly. Request: Can you add a sentence like "I might be missing context" or ask a question first? - "You missed the deadline."
Situation: On the API delivery for billing... Behavior: the handover happened two days after the agreed date and we did not get a heads-up. Impact: QA could not test and we lost the release window. Request: If you see a delay coming, can you flag it 24 hours earlier?
SBI also works for positive feedback
Most praise is too generic to repeat. SBI makes it repeatable:
- Situation: In last Friday's incident call...
- Behavior: you summarized the issue, proposed two options, and asked for a decision.
- Impact: we aligned quickly and restored service faster.
- Request: Please keep doing that. Your structure helps the whole team.
The five mistakes that make feedback backfire
- Personality labels: "You're careless." -> "Two fields were shipped without validation."
- Vague language: "Be more professional." -> "In client calls, avoid sarcasm and confirm next steps."
- Saving feedback for the big talk: small feedback early prevents big drama.
- Public feedback that should be private: praise in public, correct in private.
- No request or path forward: SBI without a next step feels like a complaint.
Scripts for difficult conversations
Use this opening to lower defensiveness:
"Can I share an observation and get your perspective? My goal is to make our collaboration smoother."
Then SBI:
"In [Situation]... I noticed [Behavior]... The impact was [Impact]... What I'd like going forward is [Request]."
End with: "How does that land for you?"
FAQ
- What does SBI stand for? Situation, Behavior, Impact.
- Why is SBI better than the feedback sandwich? It reduces vagueness and defensiveness by focusing on observable behavior and outcomes.
- How do you give constructive feedback without offending? Use neutral facts, avoid labels, describe impact, and make a request. Ask for their perspective.
- Should feedback be written or spoken? Sensitive feedback should start spoken, then be summarized neutrally in writing.
- Can SBI be used for positive feedback? Yes, it is one of the best ways to reinforce repeatable high-performance behavior.
A 7-day SBI challenge
For the next 7 days, give one SBI feedback message per day:
- 3 positive
- 4 improvement-focused
Keep it short: one example, one request. By day 7, you will notice less defensiveness, clearer expectations, faster alignment, and fewer repeated mistakes.
İlgili Aracı Dene
Yıkıcı değil yapıcı, anlaşılır ve saygılı geri bildirimler üretmene yardımcı olur.
Geri bildirim aracı->Kültür Kazanır: Sahadan Ofise Çeviklik
Mikro yönetim, rapor takıntısı ve güven eksikliğini sahadan okuyun. Futbol sahasındaki dinamikler ile iş dünyasındaki kontrol refleksini paralel bir anlatımla keşfedin.
Kimler için?
Scrum Master, Agile Coach, Product Owner, Team Lead, Engineering Manager
Türkçe e-kitap
Scrum Master etkini görünür kıl + ücretsiz PDF
Her hafta kısa, uygulanabilir ipuçları al. İlk e-postada “Scrum Master Etki Panosu” PDF’iyle katkını görünür hale getirmeye başla.
Scrum Master olarak katkını nasıl kanıtlarsın?
Velocity’ye takılmadan: 5 metrik + 6 haftalık planla görünür etki hikayesi çıkar.
- 5 metriklik etki panosu
- 6 haftalık uygulama planı
- Yöneticiye anlatım şablonu
Gizliliğine saygı duyuyoruz. E-postanı sadece PDF ve haftalık ipuçları için kullanırız.
Spam yok. İstediğin an çıkabilirsin.