Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Give Negative Feedback That Actually Lands
Transcript
- Lucas: You know that moment when you're about to tell someone their work isn't meeting the bar, and you can already feel the conversation going sideways before you've said the first word? Luna: Oh, I know that feeling. My stomach clenches, and I start mentally rehearsing three different versions of the same sentence. Lucas: Right. And the instinct is usually to soften it — 'Hey, great work on that project, but one small thing...' which is what a lot of people call the feedback sandwich. And it's almost always a disaster. Luna: Why do you think the sandwich fails so often? Lucas: Because the other person sees it coming a mile away. You say something nice, they brace for the 'but'. Then they spend the rest of the conversation trying to figure out whether your praise was genuine or just a setup. The actual feedback gets lost in the noise. Luna: So what's the alternative? Just raw honesty? Lucas: Not exactly. I think the better approach is something I've seen called the 'behavioral impact model'. It's a four-step structure, and I want to walk through it with a specific example. Let's say you manage a software engineer — let's call her Priya — who consistently misses her sprint deadlines by about three days. Luna: Three days every sprint. That's a pattern, not an anomaly. Lucas: Exactly. Step one: state the specific, observable behavior. Not 'you're unreliable' or 'you need to be faster'. You say: 'In the last three sprints, your stories have been delivered three days after the sprint end date.' No judgment, just data. Luna: That feels less personal. It's a fact she can't argue with. Lucas: Step two: state the impact. 'That means the QA team is rushed at the end of the release cycle, and we've had to push two features to the next sprint because of the delay.' Now she sees the consequence, not just the rule. Luna: Okay, so far it's data and impact. That's already way more concrete than 'you need to improve your time management'. Lucas: Step three is the part most managers skip: ask about the root cause. You say: 'Can you help me understand what's causing the delay? Is it scope creep, unclear requirements, dependencies, something else?' And then you listen. Luna: This is where you might find out she's waiting on another team, or the specs changed mid-sprint, or she's been pulled into unplanned meetings every afternoon. Lucas: Right. And if you jump to 'you need to work faster' without understanding the root cause, you're solving the wrong problem. Step four: collaboratively build a solution. 'What's one thing we could change next sprint to get those stories in on time?' She might say, 'If I could get the requirements locked by Monday instead of Wednesday, I could finish on Friday.' Now it's her idea, not your mandate. Luna: And that makes her invested. She owns the fix. Lucas: Exactly. And the whole conversation takes maybe five minutes. But it completely reframes the dynamic. You're not the critic; you're the coach helping her solve a puzzle. Luna: I want to extend this to something I've struggled with: giving negative feedback to someone who's defensive. What do you do when you hit step three and instead of a root cause, you get 'Well, everyone else is late too' or 'The estimates were unrealistic'? Lucas: That's a tough one. First, don't get pulled into defending the estimates or comparing them to others. Acknowledge their perspective: 'You might be right about the estimates. Let's set that aside for a second and focus on what's in your control.' Then redirect back to the behavior and impact. Luna: So you don't argue. You just hold the frame. Lucas: Yes. And sometimes you need to name the defensiveness gently. 'I notice you're pushing back on this. I'm not trying to blame you — I'm trying to understand what's happening so we can fix it together.' That can disarm it. Luna: There's another layer here: the feedback itself might be about something the employee can't change. Like if the company's onboarding process is broken and they're struggling because of it. Then the feedback isn't really about them. Lucas: That's a great point. And that's exactly why step three is so crucial. If the root cause is a systemic issue, then your feedback should be directed at the system, not the person. You might say, 'I see you're doing your best given the unclear requirements. I'm going to escalate that to the product team. In the meantime, let's figure out how to keep your work moving.' Luna: That's also a way to build trust. They see that you'll advocate for them. Lucas: One more thing I want to flag: timing. Don't save negative feedback for a quarterly review. Give it as close to the event as possible. If Priya misses a sprint deadline on Friday, have the conversation on Monday. The longer you wait, the more the pattern entrenches, and the harder the feedback feels. Luna: And the employee might not even realize it's a pattern. They could think it's a one-time thing. So bringing it up quickly helps them see the repetition. Lucas: Right. And you don't need a formal meeting. A quick 'Hey, got a few minutes?' at the start of the day is fine. The structure I described works just as well in a five-minute hallway chat as it does in a scheduled one-on-one. Luna: I want to ask about something else: what about when you need to give feedback to a whole team? Like the team's velocity is down, or there's a communication breakdown. Lucas: Team-level feedback is trickier because you can't call out individuals. But the same model applies. You state the observable trend: 'Our sprint velocity has dropped twenty percent over the last three sprints.' Then the impact: 'That means we're not delivering on our commitments to the business.' Then you ask the team: 'What do you think is causing this? What can we change together?' Luna: So you're modeling the same behavior you want them to use with each other. Lucas: Exactly. And that's the meta-skill here: the way you deliver feedback teaches your team how to deliver feedback. If you're direct, specific, and collaborative, they'll start mirroring that. If you use sandwiches or vague comments, they'll pick up that pattern too. Luna: I think one reason managers avoid negative feedback is they're afraid of damaging the relationship. They think, 'If I tell them they're doing something wrong, they'll resent me.' Lucas: But the research shows the opposite. A study by the Harvard Business Review found that employees who received honest, constructive feedback were more engaged and had higher trust in their manager than those who got mostly praise. The key is that the feedback has to be perceived as helpful, not critical. Luna: So it's about intent and delivery. If they believe you're on their side, they can handle the hard message. Lucas: Right. And if you never give negative feedback, you're actually doing them a disservice. They might be blindsided when they get a bad performance review or lose a promotion because no one told them the gap. Luna: That's a good point. You're protecting them from bigger surprises down the road. Lucas: And that brings me to something I think about a lot. If we've helped you navigate a tough conversation or make a better decision at work, that's the whole point of this show. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, it's a small thing that makes a big difference for us. Keeps the episodes ad-free and coming. Lucas: Alright, back to the feedback model. There's one more piece I want to cover: what to do after the conversation. You've given the feedback, the employee has agreed to try a new approach. Now what? Luna: Follow up, I assume? Lucas: Yes, but not the next day. Let it settle. Then after the next sprint or milestone, check in: 'How did that change work for you? Did it help with the deadline?' If it did, acknowledge it. 'I noticed your story was delivered on time this sprint. Nice work.' That reinforces the new behavior. Luna: And if it didn't work? Lucas: Then you go back to step three and dig deeper. Maybe the solution you both came up with wasn't the right one. That's fine. It's iteration, not failure. Luna: I love that framing. It takes the pressure off both of you to get it perfect the first time. Lucas: Exactly. And the more you practice this structure, the more natural it becomes. You stop dreading these conversations and start seeing them as what they are: opportunities to help someone get better. Luna: One last thing — what about giving feedback to a peer or a manager? Same model? Lucas: Mostly. The difference is you might need to ask for permission first. 'Hey, I have some feedback about how that meeting went. Is now a good time?' Giving them control over the timing reduces defensiveness. And with a manager, you might lean more on impact statements because they care about outcomes. Luna: Fair. And if they reject it? Lucas: Then you've still done your part. You've been honest and specific. The rest is on them. But most managers — good ones — will appreciate the candor if it's delivered respectfully. Luna: Alright, I think I've got a new framework to try. Thanks, Lucas. Lucas: Happy to. And if you try it and it works — or doesn't — let us know. We'd love to hear your stories.