Feedback and Recognition
Continuous feedback that lands — the SBI model, the candor balance, recognition that motivates engineers, and written vs verbal
Feedback and Recognition
If reviews are the low-frequency consolidation, feedback and recognition are the always-on layer underneath. This is where most of the actual development happens — in small, timely, specific moments, not in the quarterly meeting. A manager who gives good feedback continuously has reviews that write themselves and a team that keeps getting better between them. A manager who saves it all up has stale feedback, demoralized people, and reviews full of surprises.
The two halves are mirror images: feedback corrects course, recognition reinforces direction. Most managers are weak at both — they avoid the hard feedback and forget the recognition — and the team gets neither steering nor fuel.
Why Continuous Beats Periodic
Feedback has a short shelf life. The same observation is worth ten times more the day after the event than it is three months later in a review.
- It's actionable while the moment is live. "The way you framed the tradeoff in that meeting just now landed really well" tells someone exactly what to repeat, while they still remember the meeting.
- It's lower stakes. A small course-correction in a 1:1 is a normal conversation. The same point saved for a review becomes a Big Deal with a rating attached.
- It compounds. Many small adjustments over a quarter move someone further than one big download once a year.
- It prevents the ambush. Continuous feedback is the single thing that makes reviews surprise-free.
The mental model: feedback is not an event you schedule, it's a habit you run. The goal is to make it so normal that it stops being scary.
The SBI Model
The most reliable structure for delivering a specific piece of feedback — works for both reinforcing and corrective. Situation, Behavior, Impact.
- Situation — when and where, concretely. "In yesterday's design review…"
- Behavior — what they actually did, observable, no interpretation. "…you walked through three options and recommended one with reasons…"
- Impact — the effect it had. "…which meant we made the call in ten minutes instead of debating for an hour."
Why it works: it removes the two things that make feedback land badly — vagueness and character judgment.
| Without SBI | With SBI |
|---|---|
| "You're a great communicator" | "In standup today, you summarized the blocker in two sentences and proposed a fix — the room understood instantly" |
| "You need to be more proactive" | "On the auth ticket, the blocker sat unflagged for three days until I asked. Flag blockers the day you hit them so we can unstick them fast." |
| "Your code reviews are too harsh" | "On Maria's PR, there were 30 comments with no priority markers. She read it as a wall of criticism. Tag the must-fixes and let the nits go and the same feedback lands as help." |
For corrective feedback, you can extend SBI with a forward step: what to do instead. Don't leave someone knowing what went wrong but not what good looks like.
The Candor Balance
Kim Scott's Radical Candor frame is the clearest map here: two axes — how much you care personally and how much you challenge directly. The combinations:
| Challenge directly: low | Challenge directly: high | |
|---|---|---|
| Care personally: high | Ruinous Empathy | Radical Candor |
| Care personally: low | Manipulative Insincerity | Obnoxious Aggression |
The trap most managers fall into is Ruinous Empathy — they care about the person, so they soften, hedge, or withhold the hard truth. It feels kind. It is actually the cruelest of the failure modes, because the person never gets the information they need to improve, and finds out too late (often in a review or a layoff) that there was a problem all along.
Getting the balance right:
- Care is the prerequisite, not the goal. You earn the right to challenge directly by demonstrably being on the person's side. Challenge without care is just aggression; care without challenge is useless.
- Be direct about the work, gentle about the person. "This design has a race condition that'll bite us in production" is direct on the work. It is not a comment on their worth.
- The kindest thing is usually the most direct thing. Telling someone clearly that they're missing the bar — early, with support — gives them a chance to fix it. Withholding it robs them of that.
- Solicit it on yourself first. Asking for and visibly acting on feedback about your own management is how you make the channel safe enough for the hard stuff to flow.
Recognition That Motivates Engineers
Recognition is the half managers most often skip, and it's nearly free. But generic recognition does almost nothing — and for engineers specifically, the wrong kind can actively backfire.
What works:
- Specific, not generic. "Great job, team!" is wallpaper. "The way you instrumented the cache so we could actually see the hit rate is what unblocked the whole investigation" tells someone their specific contribution was seen.
- For the right things. Recognize the unglamorous wins engineers value — the careful migration that didn't break anything, the test that caught a regression, the doc that saved everyone a week. Reward only visible heroics and you train people to manufacture fires.
- Effort and judgment, not just outcomes. A well-reasoned call that didn't pan out still deserves recognition for the reasoning. Reward only outcomes and you punish smart risks.
- Calibrated to the person. Some engineers love public praise; others find it mortifying. Introverts often value a quiet, specific message far more than a shout-out in all-hands. Know which is which.
- Peer-visible where it counts. Recognition in front of the people whose opinion the engineer values (their technical peers) lands harder than top-down praise.
What backfires:
- Praise inflation. If everything is "amazing," nothing is. Reserve strong words so they keep meaning something.
- Spot bonuses as a substitute for fair pay. A pizza party does not compensate for a below-market salary, and engineers do the math instantly.
- Recognition that ignores the quiet contributors. The person keeping the lights on rarely gets the credit the launch hero does. Deliberately look for the invisible work.
Written vs Verbal
The medium changes how feedback and recognition land. Choose deliberately.
| Verbal | Written | |
|---|---|---|
| Reinforcing / praise | Good — warm, immediate | Better — durable, shareable, re-readable, can copy their manager |
| Minor correction | Best — low stakes, quick, in a 1:1 | Risks feeling heavy for something small |
| Serious / repeated issue | Necessary first — have the conversation | Also write it after — clarity and a record |
| Sensitive / emotional | Always — never deliver hard news in text | Follow up in writing to confirm the plan |
Rules of thumb:
- Praise in writing, criticize in person. Written praise is a gift that keeps working — forward it, drop it in a channel, cite it in a review. Hard feedback over text reads colder than you mean and invites defensive re-reading.
- Never deliver difficult feedback for the first time in writing. No tone, no chance to clarify, no room to respond. Talk first; document after if it's serious.
- Write down the things that need to stick. Expectations, agreements, and repeated issues belong in writing so there's no "I never heard that" later.
- Async feedback respects focus. A well-written async note about a non-urgent PR detail is often kinder than interrupting deep work to say it out loud.
Anti-Patterns
- Feedback hoarding. Saving it for the review. By then it's stale and lands as grievances. Give it in days.
- Ruinous empathy. Softening the hard truth out of niceness. The cruelest kindness.
- The compliment sandwich. Hiding real feedback between two compliments so it's missed. Be direct.
- Praise inflation. Everything is amazing, so nothing is. Words lose their currency.
- Recognizing only outcomes. Punishing smart risks that didn't land; rewarding lucky ones that did.
- All correction, no recognition. A team that only hears from you when something's wrong stops trusting your feedback entirely.
The Bar To Hold
Feedback given close to the event, structured so it's specific and not a character judgment, hard truths delivered with evident care rather than withheld out of niceness, and recognition that is specific, frequent, and calibrated to what each person actually values.
Feedback and 1:1s are the high-frequency loop. Run them well and reviews become a formality, and career conversations have real material to work with.