Here’s an uncomfortable truth: 70% of employees experience anxiety when they hear the words “Can I give you some feedback?” Not negative feedback — any feedback. Their palms get sweaty, their heart rate spikes, and their brain starts preparing for danger.
And yet, 40% of employees who receive no feedback at all become actively disengaged. Meanwhile, only 26% of employees strongly believe the feedback they receive actually helps them do better work.
So people dread getting feedback, and they suffer without it. Something in our approach is broken.
The problem isn’t that feedback is a bad idea. It’s that most of us were never taught how to do it well. We default to vague comments (“Great job!” or “This needs work”), outdated techniques like the feedback sandwich, or we avoid the conversation entirely — which research shows is the worst option of all.
This guide gives you a different path. You’ll learn the neuroscience behind why feedback triggers a threat response, three proven frameworks for structuring feedback conversations, and 18 constructive feedback examples you can adapt for real situations — from missed deadlines to remote communication gaps.
Why Most Feedback Doesn’t Work (The Neuroscience)
When someone receives criticism — even carefully worded, well-intentioned criticism — the amygdala perceives it as a social threat. The same neural pathways that respond to physical danger activate. Cortisol and adrenaline flood the body. The prefrontal cortex, the part of the brain responsible for logical thinking and learning, gets temporarily hijacked by survival instincts.
In plain terms: the moment someone feels judged, they stop being able to think clearly about what you’re saying.
David Rock’s SCARF model explains this through five social domains that trigger threat or reward responses: Status (our relative importance to others), Certainty (our ability to predict what’s coming), Autonomy (our sense of control), Relatedness (how safe we feel with others), and Fairness (how equitable we perceive things to be). Traditional feedback threatens at least two of these — Status and Certainty — which is why even a kind delivery can land poorly.
This also explains why the feedback sandwich doesn’t work. Research shows that only 50% of sandwich recipients identified the critical feedback as the key takeaway, while 86% thought the overall message was positive. People learn to distrust praise when it always precedes criticism, and the Primacy-Recency effect means the middle message (the important part) is the least memorable.
The takeaway isn’t to avoid difficult conversations. It’s to approach them in ways that minimize the threat response and maximize the other person’s ability to actually hear you. That starts with using a framework — and recognizing that feedback and feedforward serve different but complementary purposes.
3 Frameworks That Actually Work
You don’t need to memorize scripts. You need a structure that keeps feedback specific, behavioral, and forward-looking. Here are three research-backed frameworks, each suited to different situations.
The SBI Model (Situation-Behavior-Impact)
Developed by the Center for Creative Leadership, SBI is the simplest and most versatile framework. It has three steps:
- Situation: Describe when and where the behavior happened. Be specific — “In Monday’s team standup” is better than “recently.”
- Behavior: State what you observed. Stick to facts you witnessed, not interpretations. “You checked your phone three times during the presentation” rather than “You weren’t paying attention.”
- Impact: Explain the effect. “It made the presenter feel like their work wasn’t valued, and the rest of the team noticed.”
The Center for Creative Leadership also recommends adding a fourth step — Intent — by asking an open-ended question: “What was going on for you?” This turns a one-way delivery into a two-way conversation.
Best for: Everyday feedback, quick corrections, both positive and constructive situations.
Radical Candor (Care Personally + Challenge Directly)
Kim Scott’s Radical Candor framework maps feedback along two dimensions: how much you care personally about the individual, and how directly you challenge them. This creates four quadrants:
- Radical Candor (high care + high directness): The goal. Specific, honest feedback delivered with genuine concern for the person’s growth.
- Ruinous Empathy (high care + low directness): Where most managers live. You care too much about short-term feelings to be honest, so you stay vague or stay silent. It feels kind, but it deprives people of the information they need to grow.
- Obnoxious Aggression (low care + high directness): The “brutal honesty” trap. Blunt feedback without empathy. It might be accurate, but the delivery ensures it won’t be received.
- Manipulative Insincerity (low care + low directness): The worst quadrant. Passive-aggressive behavior, backdoor complaints, or empty flattery.
Scott’s order of operations matters: solicit feedback from others first, then give specific praise, then offer criticism that is kind, clear, and actionable.
Best for: Building a feedback culture, coaching managers on their default patterns, reframing how your team thinks about honesty.
The DESC Model (Describe-Express-Specify-Consequences)
DESC is particularly useful when the conversation is emotionally charged or when you need to set clear expectations:
- Describe: State the facts objectively. “In the last two sprint reviews, the client-facing deliverables contained formatting errors.”
- Express: Share your concern or feeling. “I’m worried about the impression this creates with the client.”
- Specify: Clearly state what you’d like to see change. “I’d like you to run a final formatting check before anything goes to the client.”
- Consequences: Outline what happens next — both positive and negative. “This would strengthen the client’s confidence in our work, and I’d feel comfortable giving you more client-facing projects.”
Best for: Recurring issues, setting boundaries, situations where previous informal feedback hasn’t stuck.
18 Constructive Feedback Examples for Every Situation
Theory is useful, but most people searching for constructive feedback examples for colleagues need something they can adapt right now. Here are 18 examples organized by situation, each following the principles above: specific, behavioral, and forward-looking.
Missed Deadlines
1. “The Q3 report was due Friday at 5 PM, and I received it Monday morning. When deliverables arrive late, the review team has to compress their timeline — and that pressure cascades downstream. Can we talk about what got in the way and whether the original deadline was realistic?”
2. “I’ve noticed three of your last five deliverables came in after the agreed deadline. What concerns me isn’t the occasional miss — it’s that I’m finding out after the fact rather than before. If a deadline is at risk, I need to know at least two days in advance so we can adjust.”
3. “You mentioned you’d have the client proposal ready by Thursday. It’s now Friday and I haven’t received it or an update. I want to help you hit these targets — can we look at your workload and set milestones that feel realistic?”
Quality Issues
4. “The financial model you shared with leadership last week had two calculation errors in the revenue projections. When numbers at that level are wrong, it affects the team’s credibility with the executive team. Before sharing models with senior stakeholders, let’s build in a second review step.”
5. “I appreciate how quickly you turned around the marketing copy. I did notice several typos and a broken link in the final version. Speed is great, but I’d rather you take an extra day and send me something polished. Quality and speed aren’t competing goals here — they go together.”
6. “The code you shipped last sprint introduced three bugs that the QA team caught in staging. I know you were working under time pressure, but the rework ended up costing more time than the original task. What would help you catch these before they reach QA?”
Communication Problems
7. “In yesterday’s cross-team meeting, you shared the project timeline change without giving the design team a heads-up first. They felt blindsided, and it created tension that carried into the rest of the meeting. For decisions that affect other teams, can you loop them in before the announcement?”
8. “Your Slack messages sometimes lack enough context for the reader to act without a follow-up conversation. For example, yesterday’s message just said ‘need the file’ without specifying which file, by when, or for what purpose. Adding a sentence of context would save everyone a round-trip.”
9. “I’ve noticed you tend to go quiet in team meetings, even when you clearly have relevant expertise. In last week’s design review, you had insights about the user research that would have changed the direction of the conversation. I’d love to hear your perspective more — even a brief comment helps the team make better decisions.”
Attitude and Collaboration
10. “In the last two retrospectives, you’ve responded to suggestions from other team members with ‘that won’t work’ without offering an alternative. I know you have strong opinions — and that’s valuable — but shutting down ideas without building on them discourages others from contributing. Can you try responding with ‘what if we…’ instead?”
11. “When Sarah presented her project update on Tuesday, you were visibly checked out — on your laptop, not making eye contact. Regardless of your interest level in the topic, that body language sends a message to the presenter and the rest of the team. I’d ask that you give colleagues the same attention you’d want when presenting.”
12. “I’ve heard from two team members that they feel uncomfortable raising concerns in your presence because they worry about a sharp response. That’s a problem I take seriously, because we need everyone to feel safe contributing. I’d like to understand your perspective on this — and figure out how we can move forward together.”
Remote Work Situations
13. “You’ve been joining our morning standups 5-10 minutes late for the past two weeks. In a 15-minute meeting, that means you’re missing a third of the context. If the time doesn’t work with your schedule, let’s find a slot that does — but I need you present for the full meeting.”
14. “Your camera has been off in our last several one-on-ones. I understand camera fatigue is real, but for feedback conversations and check-ins, being able to see each other’s expressions makes a big difference. Could we aim for cameras-on for our biweekly syncs, at minimum?”
15. “I noticed your response time on Slack has stretched to 24+ hours on several time-sensitive threads this month. I know deep work requires focus blocks, but the team needs a way to reach you for urgent items. Could you set up a system — maybe a dedicated channel or status — so we know when you’re in deep work versus available?”
Growth and Development
16. “Your technical skills on this project have been exceptional — the architecture you designed is exactly what we needed. Where I see room for growth is in how you bring others along. When you make decisions without explaining your reasoning, junior team members miss the learning opportunity. A brief ‘here’s why I went this direction’ would go a long way.”
17. “You’ve been doing great work at the individual contributor level, and I want to see you grow into more of a leadership role. One area to develop: delegation. Right now, you take on everything yourself, which limits what you can accomplish and what your team members can learn. Let’s identify two tasks this sprint you can hand off.”
18. “I’ve noticed you haven’t signed up for any of the professional development opportunities we’ve offered this quarter. I want to make sure you know they’re available and encouraged — not optional in the ‘we say optional but mean mandatory’ sense, but genuinely supported. What kind of development would actually interest you?”
How to Receive Constructive Feedback
Giving feedback well only works if the other side knows how to receive it. Whether you’re a manager modeling this behavior or an individual contributor looking to grow, here’s how to take feedback without getting defensive.
Listen before you respond. Your first instinct will be to explain, justify, or push back. Resist it. Let the other person finish completely before you say anything. The goal is to understand their perspective, not to win the conversation.
Ask clarifying questions. “Can you give me a specific example?” or “What would ‘better’ look like in this situation?” are powerful responses that show engagement without defensiveness. They also help you get actionable information instead of vague impressions.
Separate the message from the delivery. Sometimes feedback is delivered poorly but the content is still valuable. Try to extract the useful information even if the packaging isn’t perfect. This is a skill, and it gets easier with practice.
Thank the giver. This is hard when the feedback stings, but saying “Thank you for telling me — I want to think about this” accomplishes two things: it signals maturity, and it gives you time to process before responding substantively.
Take action and follow up. Feedback without follow-through is wasted on both sides. Pick one specific thing to work on, make a visible effort, and circle back with the person who gave you the feedback. This closes the loop and encourages them to keep being honest with you.
Receiving feedback well is also a core skill in coaching and mentoring relationships — and it’s something the best leaders practice deliberately, not just tolerate.
When NOT to Give Feedback
Not every moment is a feedback moment. Knowing when to hold back is just as important as knowing how to deliver. Here are situations where pressing pause is the right call:
When you’re emotionally charged. If you’re angry, frustrated, or feeling personally attacked, wait. Feedback delivered in the heat of the moment is almost always perceived as an attack — because, honestly, it usually is one. Give yourself a few hours or a night to process before having the conversation.
When the recipient is exhausted or stressed. Research shows that people process negative feedback more defensively when they’re tired, frazzled, or dealing with high cognitive load. If someone just came out of a crisis or is working against a tight deadline, your feedback can wait.
In public. Critical feedback delivered in front of others threatens the Status domain of the SCARF model in the most visible way possible. Always deliver constructive feedback privately. (Positive feedback, on the other hand, can often be shared publicly — though even that depends on the person’s comfort level.)
When it’s about personality, not behavior. “You’re disorganized” is a judgment about who someone is. “The last three project plans were missing key milestones” is an observation about what they did. If you can’t point to a specific, observable behavior, you’re not ready to give feedback yet.
When you don’t have an alternative to offer. Feedback that only identifies what’s wrong without suggesting what “right” looks like isn’t constructive — it’s just criticism. Before starting the conversation, make sure you can articulate what you’d like to see instead.
Psychological safety is the foundation that makes all of this work. If people on your team don’t feel safe enough to hear honest feedback, no framework in the world will help. Build the safety first, then use these tools.
Giving Feedback to Remote and Hybrid Teams
Feedback is harder when you can’t read body language, and it’s easier to misinterpret text than tone of voice. Remote and hybrid teams need adjusted practices.
Use video for sensitive feedback. A Slack message or email strips out tone, facial expression, and the ability to pause and check in. For anything beyond quick positive recognition, get on a video call. It doesn’t need to be long — even five minutes of face-to-face conversation prevents the misunderstandings that text creates.
Follow up in writing. After a verbal feedback conversation, send a brief summary of what you discussed and what was agreed upon. This creates clarity, prevents “I thought you meant…” moments, and gives both people a reference point for the follow-up conversation.
Be extra specific. Without the context of shared physical space, remote feedback needs to work harder to be clear. Include dates, project names, and specific examples rather than relying on shared context that might not exist across time zones.
Use async for positive recognition. A thoughtful Slack message or a shout-out in a team channel is a great way to reinforce good work without requiring a scheduled meeting. Save synchronous time for conversations that benefit from real-time dialogue.
Your regular one-on-one meetings and employee check-ins are natural homes for feedback conversations — build them into the rhythm rather than treating feedback as a separate, formal event.
Building a Feedback Culture That Sticks
Individual feedback skills matter, but they work best inside a culture that expects and supports honest conversations. Here’s how to build that:
Start by asking for feedback yourself. The fastest way to normalize feedback is for leaders to model vulnerability. Ask your team: “What’s one thing I could do differently to better support you?” Then actually act on what you hear. This signals that feedback flows in all directions, not just top-down.
Make it regular and low-stakes. When feedback only happens during annual reviews, it carries enormous weight and pressure. When it happens weekly in casual check-ins, it becomes routine — and far less threatening. Frequency reduces anxiety for both the giver and the receiver.
Connect feedback to recognition. Teams that regularly celebrate wins and recognize good work are measurably more receptive to growth-oriented conversations. Feedback and recognition aren’t opposites — they’re two sides of the same coin. When people feel genuinely appreciated, they’re more open to hearing how they can improve.
Create shared language. When everyone on your team knows what SBI means, feedback conversations become easier because the structure is expected. Pick one framework, teach it, and practice it together.
The Bottom Line
Constructive feedback isn’t a talent — it’s a skill. Like any skill, it improves with practice and deteriorates with avoidance.
Start with one framework. Try SBI for your next feedback conversation. Focus on observable behaviors, not character judgments. Be specific about the impact and clear about what you’d like to see instead. And remember that the goal isn’t to be “nice” or “tough” — it’s to be genuinely helpful.
The best managers don’t avoid hard conversations. They’ve just learned to have them in a way that leaves the other person feeling informed, respected, and capable of doing better next time. That’s constructive feedback at its best.