Giving feedback well is one of the most-requested and least-trained management skills. Most people learned it by accident, absorbing whatever style their own managers used — good or bad. The result is a lot of feedback that is either too vague to act on, too delayed to matter, or so cushioned in politeness that the actual point gets lost. None of that is a personality problem. It is a structure problem, and structure is fixable.
What changed in 2026
- Async feedback tools grew up. More teams now route routine feedback through written, asynchronous channels (Slack threads, review docs, recorded loom-style clips) rather than saving everything for a scheduled 1:1, which shortens the delay between behavior and feedback.
- "Radical candor" backlash matured into something more useful. The industry conversation shifted from blunt-is-better toward specific-is-better — bluntness without specificity is still just an opinion.
- Manager training budgets tightened, which means more managers are expected to self-teach feedback skills from guides like this one rather than attend formal workshops. Check what your own company still offers before assuming you are on your own.
The SBI framework: Situation, Behavior, Impact
The most reliable structure for feedback is also the simplest. State the Situation (when and where), describe the observable Behavior (what the person did or said, not your interpretation of their character), and name the Impact (what resulted, on the team, the project, or you).
"You were rude in the meeting" is an interpretation. "In today's planning meeting, when Priya proposed the timeline, you cut her off twice before she finished — it meant her concern about the deadline never got heard" is SBI. The second version is harder to argue with, because it describes what happened rather than judging who someone is.
Feedback types compared
| Type |
When to use |
Risk if done wrong |
| In-the-moment |
Immediately after a specific behavior, low stakes |
Can feel like public correction if others are present |
| Scheduled 1:1 |
Recurring patterns, higher-stakes topics |
Delay between event and feedback weakens impact |
| Written async |
Detailed points, remote teams, things worth rereading |
Loses tone; can read harsher than intended |
| 360 / peer review |
Blind spots, promotion cycles |
Anonymity can produce vague or unaccountable comments |
None of these replace the others — most healthy feedback cultures use at least three of the four routinely, matched to the situation rather than defaulting to whichever one is easiest for the giver.
Giving negative feedback without damaging trust
Three things determine whether corrective feedback lands as useful or as an attack: privacy, specificity, and a clear ask. Correct in private, even when the mistake was public — public correction optimizes for the audience's comfort, not the recipient's ability to hear you. Be specific using the SBI structure above. And close with a concrete ask: what should happen differently next time, not just what went wrong this time. "Do better" is not an ask. "Send the draft by Wednesday so I can review before the client call" is.
If you manage people and want to build this into a recurring team habit rather than a one-off skill, pairing feedback practice with structured retros gives the team a regular, low-stakes venue to practice giving and receiving it.
Common mistakes
- Saving everything for the annual review. Feedback that is six months old has lost most of its behavioral relevance and mostly produces surprise rather than change.
- Feedback sandwiches. Burying a real point between two compliments trains people to distrust your praise, since they learn criticism is coming next.
- Feedback about identity instead of behavior. "You are not a team player" is unfalsifiable and undiscussable. "You did not loop in the design team before shipping" is specific and correctable.
- No follow-up. Feedback without a later check-in on whether the change happened tells the recipient it was not actually important.
FAQ
How often should feedback be given?
Continuously for small, in-the-moment items; on a fixed cadence (weekly or biweekly 1:1s) for anything that needs more context or nuance. Waiting for a quarterly or annual review as the only mechanism is too infrequent to change behavior.
What if the person gets defensive?
Defensiveness is common and does not necessarily mean the feedback was wrong. Stick to observable behavior rather than character judgments, and give the person space to respond rather than pushing through to a resolution in the same conversation.
Should feedback always include something positive?
No — forcing positive framing into every piece of feedback is what produces the compliment sandwich problem. Positive feedback should be given because it is true and specific, not as a courtesy wrapper around criticism.
Is written feedback worse than spoken?
Not inherently, but it strips out tone, so precision in wording matters more. For anything emotionally loaded, a live conversation (even a short call) is usually safer than a written message.
Where to go next