It's Thursday afternoon. You've got feedback for someone on your team. And you think: it's almost the weekend, I don't want to ruin it for them. I'll handle it Monday.

But then Monday comes - and the last thing you want to do is start the week with a hard conversation. Then you get busy... and it's been two weeks (or two months) and you can't quite remember why you didn't just say it in the first place.

If this feels familiar, you're not a bad manager - you're a human one. Almost every manager holds off on feedback at some point, and it's rarely because they don't care. It's because they're afraid of the reaction, they don't know how to phrase it, or things just get busy and it keeps sliding to next week. In this week's video, I break down why that happens and the reframe that actually gets you unstuck. Keep reading for the full framework, plus a script you can use today.

Flip It: What Would You Want From Your Boss?

Start here, because this is the question I've found changes everything else. Imagine your own boss had feedback for you - and sat on it because things were busy, or because they didn't want to upset you, or they weren't sure how to say it. Would you still want to know? Almost certainly yes. You'd just want it delivered in a way that didn't make you feel attacked, blindsided, or beaten down.

Now take that reframe and remember why it's important that you have the conversation. You're not choosing between kind and honest - you need both. And once you flip your mindset from "I'm holding back to protect them" to "I'd want to know this if I were them," the conversation stops feeling optional.

Know What You Know - And What You Don't

Before you say anything, separate fact from story. If a report is full of typos, that's objective - you can point to it. If a salesperson is missing target, that number's objective too. But what you don't know is the why behind either of these.

Maybe they were rushing to hit a deadline and didn't do a final read. Maybe something changed in their pipeline that you haven't heard about yet. Each scenario needs a conversation (and action on their part), but remember what you don't know. Go into the conversation with the facts you actually have, and ask about the rest instead of assuming it. That distinction - what you know versus what you're assuming - is what keeps feedback from turning into an accusation.

Skip the Compliment Sandwich

Praise, criticism, praise. You've likely heard this technique before. It feels safer to deliver feedback that way, but it usually backfires. People remember the "bread" (aka the good parts) and miss the "meat" in the middle, which means the actual message - the thing you needed them to hear - isn't heard. If something needs attention, say it clearly and directly, then give them the opportunity to give their perspective. That's not harsh - it's actually more respectful than burying the point.

A Script You Can Actually Use

Here's how that sounds in practice, using that typo-riddled report as the example:

"Hey, you're doing well on X and Y, but I wanted to call your attention to this - there have been a number of errors in this report, and I want to talk through it and get your perspective before we figure out next steps."

Notice what that does: it states the issue specifically, it doesn't assume intent, and it invites them to have a conversation instead of just delivering a verdict. If it's more serious, or if it's client-facing, add the stakes: "When clients see typos, it can make them question everything else about working with us." If it's internal, the stakes still matter: "Everything we send out, we want to be in the habit of proofreading closely." Context helps people understand why it matters, not just that it does.

Give Them the "Why," Then Ask for Theirs

Once you've specifically said the issue and the stakes, don't stop there - ask what's behind it. Sometimes you'll hear, “I was slammed and didn't have time to proofread, but that's what technology is for.” That's a fair point, and also a good moment to problem-solve together: running a spell check, or using an approved AI tool to catch errors before something goes out, or a trick I heard years ago and still use - printing something out and reading it on paper, because typos jump out differently than they do on a screen.

You can also talk honestly about workload: "I hear that you're busy, and we can absolutely talk about that and what you're handling and how to prioritize. But when it comes to things like typos, here's what we can do about it." That keeps the conversation collaborative instead of just corrective.

The Longer You Wait, the Harder It Gets

Feedback you give early is a quick, lower-stakes conversation. Feedback you sit on for months becomes a much bigger, more formal one - when people hear about something they did wrong long after the fact, they wonder if something else is going on. And by then, you're more frustrated, and so is the story you've built up in your head about why it happened. The longer you hold off, the higher the stakes feel by the time you finally say something.

So when you catch yourself saying, "I'll deal with it next week," take that as your sign. Set up the conversation, ask questions instead of assuming, and follow up in your next one-on-one. You'll feel better having said it - and you'll get to the bottom of it a lot faster than if you'd waited.

Managing a team and want a framework and more in-depth tips for performance conversations like this one? Our course Manager 101 walks managers through real situations like this - not just theory. Explore Manager 101 here.

In HR and want your managers to actually deliver feedback instead of sitting on it? We help organizations build this at scale. Set up a call and custom demo with our team here.