Not a performance review. Just two people naming what broke, and choosing to fix it, and not each other.

The same conversation can build someone up or quietly take them apart. We call both of them "feedback," as if the word were neutral. It isn't. Feedback is one of the most powerful tools a leader has, and one of the most routinely mishandled. Done one way, it's fuel — it sharpens people and pulls them closer. Done another, it's poison — it makes them careful, defensive, and a little smaller every time.

The difference isn't whether you're honest. It's where you're standing when you say it.

Why feedback turns to poison

Most feedback goes wrong before a single word is spoken, because of the mindset underneath it. The leader has already decided this is a right-versus-wrong situation. There's a correct way it should have gone, the other person failed to do it, and now the job is to point that out.

That's the binary trap — and people feel it instantly. The moment feedback arrives as a verdict, the other person stops listening and starts defending. You're no longer two people solving a problem; you're a prosecutor and a defendant. Nobody grows in a courtroom.

There's a subtler version, too. When someone isn't responding the way we want, the instinct is to turn up the volume — say it harder, sharper, with more edge. That's not feedback anymore. That's shame. And there's a real line here: healthy correction names a fault and invites someone to rise. Shame just keeps cranking the dial when they don't move fast enough. One develops people. The other just makes them brace.

Feedback is really about a broken agreement

Here's a reframe that changes everything. Most of the time, the feedback you want to give is actually frustration in disguise — and frustration is almost always a should. It should have been done this way. They should have known. When you hear "should" in your own head, there's a broken agreement underneath it.

So before you deliver the verdict, find the agreement. What did the two of you actually agree to — explicitly or implicitly? Was it ever clear? Did they have what they needed to keep it? Suddenly the conversation isn't "here's what's wrong with you." It's "here's the agreement we had, here's where it broke, here's what we each do to repair it." Same issue. Completely different room. One assigns guilt; the other restores how you work together.

Feedback only lands on a table that can hold it

I think of a team like a table. The top can only hold weight if it's standing on four solid legs: honesty, responsibility, respect, and loyalty. Feedback is weight you're setting on that table. If the legs are missing, it crashes.

Respect is the one people skip. Real respect isn't politeness — it's treating someone as fully capable of growing, and being genuinely curious about their side before you conclude. Loyalty is the unspoken promise that you're for them, even in the hard conversation. When respect and loyalty are present, even blunt feedback lands as care. When they're absent, the gentlest feedback still reads as an attack — because the person can feel that underneath it, you've already written them off.

That's why the same words work from one leader and wound from another. The words were never the variable.

The delivery is your job, not theirs

If your feedback is technically true but the person can't receive it, that's not their failing. It's yours. The burden is on the communicator to package the message so it can actually be heard — same truth, different wrapping. Insisting on delivering it your way, take it or leave it, isn't principle. It's just ineffective.

A leader I work with had someone on her team who kept missing the mark, and her patience was running out. Instead of escalating, she did something sharper. She reminded the person of a time they'd handled something genuinely hard and handled it well — and used their own track record as the standard: you already know how to do this; I've watched you do it. Then she named the gap, calmly. Her phrase for the whole approach stuck with me — be the wiser one, not the stronger one. She didn't turn up the volume. She built a bridge from the person's own competence to the thing she was asking for. That's feedback as fuel.

Every conversation is a deposit

You're not just addressing one performance issue. Every piece of feedback you give is teaching your whole team what it costs to fall short around you — whether it's safe to take risks, surface problems early, and stay in the room when it's hard. That accumulates. It becomes the culture, one conversation at a time.

So the question isn't just "is this feedback true?" It's "what is this conversation depositing into the culture I'm building?" Poison compounds. So does fuel.

This is the workability mindset in practice — one of the four shifts in the Shift In Life manifesto.

If your feedback keeps landing as poison no matter how you soften it, the fix is usually upstream of the words. Let's talk →