How to Give Feedback That Actually Works: The Framework Leaders Need

If you're still softening your feedback to avoid hurting someone's feelings, you might be doing more harm than good.

I see this all the time with leaders. We think we're being kind when we dance around the issue. But as Brené Brown says, "To be clear is kind. To be unclear is unkind." And unclear feedback, no matter how warmly delivered, leaves people confused about where they actually stand.

Why the Feedback Sandwich Doesn't Work

Most of us were taught to sandwich feedback: start with a compliment, sneak in the real problem, then quickly wrap it in more praise. It feels polite. The problem is it rarely works. The message gets lost, and your team walks away confused instead of empowered.

Here's what usually happens. You say something like: "Mike, you're such a valuable team member and we really appreciate your enthusiasm. I was wondering if maybe you might consider, when you have time of course, possibly looking into whether there might be ways to perhaps get your reports in a bit earlier?"

Poor Mike leaves that conversation thinking he's doing great. Meanwhile, deadlines are still being missed.

The kindness was real. The clarity was not. And without clarity, there is no real feedback, just a conversation that made the leader feel better about having said something.

What Clear, Kind Feedback Actually Sounds Like

Here's the same situation handled differently. "Mike, what's working well is your thorough analysis. Your reports always include insights others miss. What's not working is the timing. When reports come in two days late, the client team can't incorporate your findings. I need your reports by 5 PM on Fridays. What support do you need to make that happen?"

No fluff. No guessing. Just clarity.

Mike now knows exactly what he's doing well, what needs to change, why it matters, and what the specific expectation is going forward. He's been treated like an adult who can handle honest feedback and grow from it. That's not harsh. That's respectful.

The "What's Working / What's Not Working" Framework

The structure behind that example is simple and worth keeping in your back pocket. Start with what's genuinely working, be specific about what's not working and why it matters, state the expectation clearly, and then ask what support is needed.

That last part is important. Ending with a question keeps the conversation collaborative rather than one-directional. It signals that you're invested in helping the person succeed, not just documenting the problem. And it often surfaces information you didn't have, obstacles or misunderstandings that, once addressed, make the whole issue easier to resolve.

This framework works because it replaces ambiguity with real accountability. You're not being mean. You're being clear. And a team that receives clear feedback consistently develops a shared understanding of the standard, which means less correction needed over time, not more.

What Happens When Your Team Actually Knows Where They Stand

When your team knows exactly what's expected of them and why it matters, they don't just improve. They own their work. There's a difference between a team member who is trying to guess what good looks like and one who has been told directly, specifically, and respectfully. The second person has everything they need to deliver.

Stop cushioning your feedback so much that it bounces right off. Your team deserves clarity, and frankly, so do you.

Ready to bring this kind of leadership to your business? Visit bethfahey.com to learn more about working with me as your EOS Implementer.