What is the SBI feedback model?

Situation, Behavior, Impact: when/where it happened, what they did (observable), and the effect on people, product, or delivery. Then make a clear ask.

Should I give feedback in Slack or in a 1:1?

Positive can be public or async. Corrective feedback is usually better live (or video) so tone doesn’t get lost — then summarize in writing.

How soon should I give feedback after an incident?

Same day when possible, within a week at most. Waiting for performance review turns a coaching moment into a surprise.

10 Feedback Scripts Engineering Managers Can Copy and Paste

Most managers don’t struggle with caring — they struggle with the words. Here are 10 copy-paste feedback scripts built on SBI (Situation, Behavior, Impact). Customize the brackets. Deliver live when it’s hard.

When the stakes are higher, pair these scripts with a full walkthrough of how to give difficult feedback to engineers.

1. Specific praise after a solid delivery

“In yesterday’s [release/demo], you [owned the cut list / unblocked design]. That let us [hit the date / avoid a scramble]. Keep doing that — it’s exactly the ownership we need.”

2. Missed deadline without drama

“On [project], we agreed [date]. We slipped without an early heads-up. That left [stakeholder] unable to plan. Next time, flag risk by [Wednesday] so we can re-scope together.”

3. Code review tone

“In the review on [PR], the comments read as [dismissive/personal]. The author shut down and we lost a day. Let’s keep feedback on the change — suggest alternatives, assume good intent.”

4. Dominating meetings

“In planning today, you spoke for most of the design discussion. Quieter folks didn’t weigh in, and we missed [risk]. I’d like you to leave space — ask two people for their view before proposing the path.”

5. Low visibility / radio silence

“This sprint I only heard updates when I chased them. That made it hard to support you with [X]. Let’s do a short Friday written update — blockers + next step — so I’m not guessing.”

6. Quality slip

“The last two PRs shipped without [tests/edge cases we agreed]. We spent [N] hours firefighting. Before merge, run through our checklist — I’ll review with you this week if helpful.”

7. Cross-team friction

“In the thread with [team], the tone came across as blame. They’re now escalating instead of collaborating. Next time, lead with shared goal + options. Want to draft it together once?”

8. Career nudge (positive stretch)

“On [project], you already do [skill]. To grow toward [level], I’d like you to own [stakeholder update / tech design] end-to-end. I’ll give air cover. Interested?”

9. Asking for reverse feedback

“What’s one thing I did this month that made your work harder? Be specific — I want to change it.” Then shut up and take notes.

10. Closing a hard conversation

“Here’s what I’m asking: [behavior change] by [date]. I’ll support you with [resource]. We’ll check in [day]. Does that feel clear — and fair?”

Harder conversations need more than a script — see 8 tips for giving difficult feedback to engineers.