How to Give Feedback That Actually Changes Behaviour

2026-06-28 · 7 min read · 1:1 Meetings

Most managers give feedback constantly. Most of it is forgotten by the next morning.

Not because the feedback is wrong — but because it's delivered in a way the brain doesn't retain. You mention it in passing. You soften it so much the message gets lost. Or you say it once and assume the work is done.

Here's what actually works.

Why Feedback Fails

Feedback fails for three predictable reasons:

It's too vague. "Your communication could be better" tells someone nothing about what to actually change. "In yesterday's incident call, you skipped the root cause section and the team was confused about next steps" is actionable.

It's too late. Feedback given three weeks after the event is archaeology, not coaching. The person can't remember the context clearly enough to learn from it.

It's buried in positives. The sandwich technique ("great job... but... anyway, great job!") is well-intentioned but it teaches people to stop listening after the first positive. They know what's coming and they're just waiting for it to be over.

The SBI Framework

The most reliable feedback structure is Situation → Behaviour → Impact:

• Situation: the specific moment you're referring to
• Behaviour: what you observed (not your interpretation of it)
• Impact: the actual effect on the team, the project, or the people involved

Example:

"In the architecture review on Tuesday [Situation], you dismissed Priya's concern about the API rate limits without engaging with it [Behaviour]. She told me afterwards she felt her input wasn't valued, and she stayed quiet for the rest of the session [Impact]."

This is different from:

"You can be dismissive sometimes."

The SBI version is hard to argue with because it's factual. It also makes it much easier for the person to know exactly what to change.

When to Give It

The research on feedback timing is clear: the closer to the event, the better. Within 24–48 hours is ideal for corrective feedback. Within the same conversation is ideal for positive feedback.

The exception is emotionally charged situations. If someone just had a bad launch or a tense incident, wait until the dust settles — usually 24 hours. You want them to be able to hear you, not be in fight-or-flight mode.

The 1:1 Is the Wrong Place for New Critical Feedback

This is counterintuitive. Most managers save hard feedback for 1:1s because it feels private and safe. But showing up to a 1:1 with unexpected critical feedback puts the person on the back foot.

Better: give the feedback briefly and directly when it's fresh, then use the 1:1 to follow up — check in on how they're processing it, discuss what support they need, and track progress.

The 1:1 is for developing the conversation, not starting it cold.

Handling Defensiveness

Some people receive feedback well. Others get defensive, deflect, or go quiet. Here's how to handle each:

Deflection ("Yeah but the deadline was impossible"): Acknowledge the context, then return to the behaviour. "I hear you, the timeline was brutal. And I still want to talk about how you communicated to the team during it."

Silence: Don't fill it. Give them space to process. Ask "What's going through your mind right now?" rather than softening the feedback.

Counter-attack ("You never give me clear direction"): Separate the conversations. "That's worth discussing and I want to — let's make time for that. Right now I want to stay focused on what I raised."

A Template for Hard Conversations

Use this structure when you need to deliver feedback that's going to be uncomfortable:

1. State your intent: "I want to give you some feedback because I think it's important for your growth."
2. SBI: Deliver the specific feedback.
3. Check understanding: "How does that land with you?"
4. Explore together: "What do you think was going on in that moment?"
5. Agree on next steps: "What would you do differently? What support do you need from me?"

The goal isn't to make the person feel bad. It's to create a shared understanding of what happened and a clear picture of what better looks like.

Positive Feedback Is Underrated

Most managers give too little positive feedback. Partly because it feels unnecessary ("they already know they did well"), partly because the urgency of problems crowds it out.

Positive feedback serves three functions: it reinforces behaviour you want to see more of, it builds the psychological safety that makes corrective feedback easier to hear, and it tells people what "great" looks like in your eyes — which is more useful than most people realise.

Make it specific. "Good job on the release" is noise. "The way you caught that edge case in review saved us a production incident — that's the kind of attention to detail that makes the whole team better" is something someone will remember.

Track It

The best way to improve your feedback practice is to keep a log. After 1:1s, write down what feedback you gave and what the person's response was. Over time you'll see patterns — who responds well to directness, who needs more context, who tends to get defensive on which topics.

Emtricks tracks this automatically across your 1:1 notes. Over time you'll build a clear picture of each person's development arc — not just individual incidents.

The managers who give the best feedback don't have better observations than everyone else. They just follow through more consistently.