Most managers know they should give more feedback. Most managers also dread giving it — particularly the kind that involves telling someone their behavior is causing a problem. The avoidance is understandable. Poorly delivered feedback damages relationships, creates defensiveness, and often produces no change. The solution is not to avoid feedback but to get better at delivering it.
The difference between feedback that changes behavior and feedback that creates defensiveness is almost never about the content. It is about structure: whether the feedback is behavioral or personality-based, specific or vague, bidirectional or top-down. This guide covers the practical mechanics of delivering feedback that lands.
Step 1: Separate observation from interpretation
The most common feedback mistake is delivering interpretations as facts. "You do not care about the team" is an interpretation. "You have missed the last four team retrospectives without notice" is an observation. The first invites defensiveness and denial. The second invites a conversation.
Before any feedback conversation, write down what you actually observed — the specific words said, actions taken, or outcomes produced. Then separately note the interpretation you have made. Your job in the feedback conversation is to share the observation and invite the other person to help you understand it — not to assert that your interpretation is correct.
This matters especially when the behavior you have observed might have an explanation you are not aware of. Missing four retrospectives might mean disengagement — or it might mean a scheduling conflict, a personal crisis, or an unclear expectation about attendance requirements. Asking before concluding is both more accurate and more respectful.
Step 2: Use the SBI model
The Situation-Behavior-Impact (SBI) model is the most widely taught and reliably effective feedback structure. It keeps feedback anchored in observable reality rather than personality judgments.
- Situation: Name the specific context. "In last Tuesday's sprint planning meeting" is a situation. "You sometimes" is not.
- Behavior: Describe the observable action — what anyone in the room could have seen or heard. "You presented the engineering estimate without consulting the team beforehand" is a behavior. "You were dismissive" is a judgment.
- Impact: Describe the concrete result. "Two engineers told me afterward they felt excluded from the decision. The estimate was then challenged by three team members who had different information, which extended the meeting by 40 minutes."
The power of SBI is that it gives the recipient something to respond to. They can confirm the observation, provide context that changes the impact framing, or simply acknowledge and commit to change. What they cannot do is deny that the behavior happened or that the impact was real.
Step 3: Choose the right moment and setting
Timing and setting are the most underestimated elements of feedback delivery.
When to give feedback: Promptly — within 24–48 hours of the observed behavior. Feedback given two weeks later lacks the specificity and emotional connection that make it land. The only exception is significant emotional charge — if you or the recipient are visibly upset, a short cooling period improves reception.
Where to give feedback: In private, one-on-one. The 1:1 meeting is the natural venue for development-oriented feedback. Never give critical feedback in group settings — it creates shame and defensiveness, not learning.
In writing vs in person: Difficult feedback should be delivered in person (or video call), not in writing. Written feedback lacks tone, cannot respond to real-time reactions, and can be read and re-read in ways that amplify negative emotions. Use writing to follow up and confirm what was discussed, not as the primary delivery mechanism.
Step 4: Ask before you tell
The most powerful technique in feedback delivery is asking before telling. Starting with "How do you think that went?" or "What would you do differently next time?" gives the recipient the chance to demonstrate self-awareness — and often saves you the discomfort of delivering criticism at all.
When someone identifies their own gap, feedback becomes shared acknowledgment of a known issue, not a top-down verdict. The manager's role shifts from judge to partner. Development commitments made from this position of self-awareness are significantly more likely to be kept.
Step 5: Be specific about what you want instead
Feedback that only names the problem without pointing toward the solution is criticism, not coaching. The recipient leaves knowing what was wrong but not what to do differently.
Every piece of developmental feedback should include a specific behavioral ask — something concrete enough that the person knows exactly what to do in the next similar situation. Not "be more collaborative" but "before presenting an estimate to stakeholders, spend 15 minutes confirming it with the engineers who will do the work."
Step 6: Check for understanding and commitment
Before ending the feedback conversation, check two things: that the feedback was understood, and that the recipient has committed to a specific change.
"Does that land for you?" or "What is your take on this?" opens space for the recipient to process and respond — rather than ending with a monologue and hoping for the best. Then: "What will you do differently in the next sprint planning?" elicits a commitment that you can both reference in future check-ins.
Step 7: Follow up and recognize improvement
Feedback without follow-up produces temporary compliance, not lasting change. In your subsequent 1:1s, explicitly look for the changed behavior. When you see it, name it immediately: "I noticed you waited for everyone to weigh in before committing to the estimate in today's meeting — that is exactly what I was talking about."
Specific recognition of changed behavior is the most powerful reinforcement mechanism available to a manager. It closes the loop, demonstrates that you are paying attention, and creates the positive association with the new behavior that makes it stick.
Track feedback given and received in your team's feedback system so development conversations have documented continuity across review cycles.