Good feedback is specific, timely, and focused on behavior rather than personality. That single principle separates feedback that actually changes something from feedback that makes people shut down. Whether you’re talking to a direct report, a peer, or your boss, the mechanics are largely the same: describe what happened, explain the impact, and open a conversation about what comes next.
Why Most Feedback Falls Flat
The human brain treats vague criticism the same way it treats a physical threat. Neuroscientist David Rock’s SCARF model identifies five triggers that push people into a defensive “avoid” response: threats to their status, certainty, autonomy, relatedness, or sense of fairness. A comment like “you need to be more professional” hits nearly all five at once. It attacks identity, offers no specifics the person can act on, and feels like a judgment handed down from above.
Effective feedback sidesteps those triggers by keeping the focus narrow and concrete. Instead of labeling someone, you describe a moment. Instead of issuing a verdict, you share an observation and its consequences. The goal is to keep the other person’s brain in problem-solving mode rather than self-protection mode.
The SBI Framework
The simplest structure for any feedback conversation is the SBI model, developed by the Center for Creative Leadership. It has three parts:
- Situation: Name the specific context. “In this morning’s client call” is far more useful than “lately” or “in general.”
- Behavior: Describe exactly what you observed. Stick to actions, not interpretations. “You interrupted the client twice while she was explaining her timeline” is a behavior. “You were rude” is a judgment.
- Impact: Explain what the behavior caused. “She stopped sharing details after that, and we left the call without the information we needed to scope the project.”
SBI works equally well for praise. Telling someone “great job” is forgettable. Telling them “In yesterday’s presentation, you walked the room through the data before making your recommendation, and the executive team approved the budget on the spot” gives them a clear picture of what to keep doing and why it matters.
How to Deliver the Message
Structure is only half the equation. Delivery determines whether someone actually hears you.
Do it soon. Feedback loses power with every day that passes. “Right after the meeting” beats “sometime next month.” If the moment isn’t right, that same day or the next morning is a reasonable window. Waiting until a quarterly review to mention something that happened in week one guarantees the other person will feel blindsided.
Do it privately for criticism, publicly for praise. Corrective feedback delivered in front of others triggers a status threat that makes people defensive regardless of how carefully you phrase it. Praise, on the other hand, gains power when others witness it.
Ask permission first. A quick check like “Is now a good time to talk about something I noticed?” gives the other person a moment to shift gears mentally. If they’re in the middle of a deadline or visibly stressed, waiting an hour costs you nothing and buys you a more receptive listener.
Stay humble. You might be wrong, or you might be missing context. Framing your feedback as an observation rather than a verdict leaves room for dialogue. “Here’s what I noticed, and I’m curious how you see it” invites collaboration. “Here’s what you did wrong” invites a wall.
Giving Feedback to Your Boss
Upward feedback follows the same principles but requires more deliberate framing because the power dynamic runs against you. A useful structure for these conversations is the CORE model: Context, Observation, Result, Expected Next Step.
In practice, that sounds like: “In yesterday’s sync (context), you cut off two people mid-thought (observation). It seemed to shut down discussion (result). Could we try a round-robin format next time? (expected next step).” You’ve described a specific event, connected it to a team-level consequence, and offered a solution rather than just a complaint.
A few techniques that help when you’re talking to someone with authority over your career:
- Focus on outcomes, not character. “You’re really disorganized” is a label that invites defensiveness. “I noticed there were last-minute changes to the deck this morning, and it created some confusion with the client” is a fact your boss can evaluate without feeling attacked.
- Seek to understand before pushing your point. Starting from “I’d love to understand the rationale behind this decision, because it affected my workflow” positions you as a collaborator, not a critic. Sometimes the context changes your perspective entirely.
- Prepare lightly. For a high-stakes conversation, jot three or four bullet points on a sticky note. Not a script, just enough to keep you anchored so nerves don’t cause you to ramble or soften the message into meaninglessness.
Opening lines matter more than you’d think. “I want to share something that could make our meetings more effective” frames the conversation around improvement. “We need to talk” frames it around conflict. Choose the version that lowers the temperature.
What to Do When Someone Gets Defensive
Even well-delivered feedback sometimes lands hard. When someone’s voice rises, their arms cross, or they start deflecting blame, they’ve moved out of rational processing and into a threat response. Pushing harder at that point is counterproductive.
Instead, slow down. Simple questions like “Tell me how you’re feeling right now” or “How would you like to proceed?” give the person a chance to name their emotion, which helps the brain shift back toward reasoning. You can also acknowledge the difficulty directly: “I can see this is tough to hear, and that’s not my intent.” Sometimes the best move is to pause the conversation entirely and come back to it later that day.
The goal isn’t to win the moment. It’s to plant a seed the person can process on their own terms. People rarely change their behavior during the feedback conversation itself. They change afterward, when they’ve had time to sit with what you said.
Making Feedback a Habit, Not an Event
Feedback that only happens during formal reviews feels high-stakes by default. When you give small, specific observations regularly, each individual conversation carries less weight and less anxiety for both sides.
Before you give feedback, write down what you want to say and what outcome you’re hoping for. This takes two minutes and prevents the conversation from drifting into vague territory. If you’re nervous, practice with a trusted colleague first. Tell them, “I want you to help me refine and clarify this message.” Hearing yourself say the words out loud often reveals where your phrasing is too harsh, too soft, or too abstract.
You don’t need to have all the answers when you sit down with someone. Offering to work together on a solution is more effective than handing down a prescription. “I’ve noticed this pattern, and I’d like us to figure out what would help” treats the other person as a capable adult rather than a problem to be fixed. That distinction matters more than any framework.