Give constructive feedback by naming specific behavior, its impact, and one clear next step—never character labels. Use private 1-on-1s, the SBI feedback model, and ask what support they need. Pair correction with genuine recognition so the person leaves knowing what to change and that their contribution still matters.
Why does feedback so often backfire?
Most managers intend to help when they raise a concern. Yet the same conversation can leave a senior engineer quietly updating a résumé. The gap is rarely honesty; it is how the brain interprets social threat. When feedback sounds like a verdict on who someone is—“you’re careless,” “you’re not leadership material”—the amygdala treats it like status loss. Motivation drops, risk taking freezes, and the very behaviors you wanted to improve get hidden behind compliance or withdrawal.
Research on learning and performance consistently shows that people improve fastest when they believe the standard is high and that they belong on the team working toward it. That is the heart of feedback without demotivating: preserve dignity, clarify the bar, and co-own the path forward. For engineering leads, this matters twice over. Your reports often tie identity to craft; a vague “this wasn’t good enough” reads as “you’re not a good engineer.” Specificity is kindness.
What is the SBI feedback model?
The SBI feedback model (Situation, Behavior, Impact) is a simple script that keeps constructive feedback observable and fair. You anchor in a moment everyone could replay on video, describe what the person did (not what you assume they meant), and explain why it mattered for outcomes, trust, or customers.
| SBI step | What to say | Example (engineering context) |
|---|---|---|
| Situation | When and where; shared context | “In yesterday’s incident retro, when we reviewed the rollback timeline…” |
| Behavior | Observable actions, not labels | “…you interrupted Priya three times before she finished the sequence diagram.” |
| Impact | Effect on team, quality, or goal | “…we missed her root-cause note, and the action items skewed toward your first hypothesis.” |
After SBI, add a forward-looking request: one behavior to try, a metric to watch, or a rehearsal before the next meeting. That turns criticism into a experiment both of you can track in the next 1-on-1.
How do you give feedback to an employee without crushing confidence?
When learning how to give feedback to employee reports (or peers you influence), think in ratios over time, not a single perfect speech. Kim Scott’s “radical candor” popularized caring personally while challenging directly; the practical version for busy leads is smaller, steadier doses. People demotivate when correction is rare, dramatic, and disconnected from the good work they already do.
Use this five-step flow in a dedicated 1-on-1 slot—not squeezed into standup:
- Open with intent. “I want us to win on reliability; I’m going to share one pattern I’m seeing and brainstorm fixes with you.”
- Deliver SBI. Stick to one behavior cluster per conversation so the brain can act.
- Invite their map. “How did you see that moment? What was going on for you?” Listen fully before defending your read.
- Co-design one change. Agree on a concrete next step with a date: shadow a review, pair on the next design doc, use a checklist before merge.
- Reaffirm contribution. Name a recent win that is unrelated to the issue so identity stays tied to growth, not shame.
Avoid stacking unrelated issues in one meeting. A laundry list feels like a performance case file even when your tone is calm. Queue secondary topics for a follow-up after the first change sticks.
What language should managers avoid?
Words that sound small to you land large on someone whose promotion or visa sponsorship sits in your hands. Swap absolutes (“always,” “never”) for frequency you can evidence. Replace identity language (“you’re disorganized”) with behavior (“the last two handoffs arrived without the runbook link”). Skip sarcasm in writing; Slack lacks the vocal warmth that softens intent in person.
Also watch comparative praise—“You’re the only one who gets this”—which can demotivate the rest of the team and trap the recipient in a hero role. Compare people to standards and past versions of themselves, not to colleagues in public channels.
When should feedback be public versus private?
Recognition and learning that benefits the whole team can be public: celebrating a thoughtful postmortem, thanking someone for raising a risk early. Corrective constructive feedback belongs in private unless the issue is a broken team norm everyone already agreed to enforce (and even then, start 1-on-1 before escalating to the group). Public correction teaches people to perform agreement, not to improve.
If you must address a pattern in a team forum—say, recurring missed estimates—describe the system and invite fixes: “Our last three commits slipped after we skipped estimation review. I’m changing our process to require a second pair of eyes on dates.” That keeps accountability on process without pinning one person under a spotlight.
How do 1-on-1s make feedback stick?
Feedback dies in the hallway. Without a follow-up thread, reports assume you forgot—or that the issue was fatal. Reserve five minutes in recurring 1-on-1s to revisit agreed changes: what worked, what was hard, what to adjust. This loop is where psychological safety compounds; people see that speaking about mistakes leads to support, not surprise rating drops months later.
Document lightly for yourself: date, SBI summary, agreed action. You are not building a case file; you are preventing drift. When review season arrives, neither of you should encounter “new” criticism that was never discussed live. That surprise is one of the fastest paths to demotivation and attrition.
What about high performers who only hear “more”?
Stars demotivate when every conversation is “great job, now do more with less.” They still need constructive feedback on how their strengths scale: delegation, mentoring, saying no, or tolerating imperfect code from others. Frame growth feedback as unlocking the next level of impact, not fixing deficiency. “Your designs are consistently clear; the next lever is teaching two mid-level engineers to run design reviews without you in the room.”
Ask explicitly: “What kind of feedback helps you most—real-time nudges or structured 1-on-1 blocks?” High performers often prefer crisp SBI in the moment for tactical issues and deep dives for career themes. Honoring preference increases uptake more than forcing a single style.
How do you recover if a conversation goes poorly?
If you raised your voice, mixed in personal frustration, or spoke without SBI, repair quickly. Name what you regret, restate care for the person, and offer a redo: “I didn’t describe the impact clearly Tuesday; can we take ten minutes tomorrow and run it again with specifics?” Repair builds more trust than pretending the moment did not happen.
If they went silent or defensive, do not litigate tone in email wars. Pause the thread, meet live, and use questions: “What would make this useful?” “What am I missing?” Defensiveness often signals accumulated unfairness or fear of hidden documentation—not stubbornness about one incident.
Frequently asked questions
What is the SBI feedback model?
SBI stands for Situation, Behavior, Impact. You describe when and where something happened, the observable behavior (not personality), and the effect on the team, customer, or goal. It keeps constructive feedback factual and actionable.
Should I give constructive feedback in public or in a 1-on-1?
Give corrective constructive feedback in a private 1-on-1. Public criticism triggers threat responses and shame, which demotivates even strong performers. Praise can be public; course correction belongs one on one.
How soon should I deliver feedback after a mistake?
Within a few days while context is fresh, after you have cooled down and can stick to facts. Delayed pile-ons feel punitive; instant reactions in Slack often skip the SBI structure and damage trust.
What if my employee shuts down when I give feedback?
Pause, name the tension without debating character, and ask what would make the conversation useful. Offer one concrete change, invite their view, and schedule a short follow-up so feedback feels like partnership, not verdict.
Related: Beyond the rating: 5 questions to build psychological safety in your next performance review, Stop being a Super Doer: 5 truths about the jump to leadership, High impact engineering 1:1: a framework for elite leadership.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.