The Feedback Sandwich Is a Lie and Everyone Can Taste It

"So was that a telling off or not?"

An engineer asked me that in the corridor, about ninety seconds after his lead had given him what she genuinely believed was balanced, supportive feedback. He'd come out of the room unable to tell whether he was in trouble. He spent the rest of the week assuming he was.

The mechanics are worth being honest about. You open with something positive to soften the ground. You deliver the actual message. You close with something positive so the person leaves feeling good.

What you've built is a signal that anyone recognises after the second time. Praise now predicts criticism. So the next time you tell someone their incident write-up was excellent, they brace. You have taken your genuine appreciation, which is one of the few tools you have, and made it into a warning noise.

Worse, the middle gets lost. Under the pressure of a positive opener and a positive close, most people compress the difficult bit until it disappears. "Your documentation could maybe be a bit more detailed in places" was meant to carry "operations couldn't run the failover from your runbook at 3am on Sunday and had to ring you". Those are not the same message. One of them changes behaviour.

I'm not arguing for bluntness as a personality. Warmth is fine. Warmth is good, actually. Just don't use it as packaging.

Most feedback fails on one of two axes, and both are fixable without any courage at all.

Vague is the first. "Your communication with the client needs work" gives somebody nothing to change on Monday. What did you actually see? "On Thursday's call, the client asked twice when the firewall work completes and both times you answered with what the team's been doing rather than a date." That's a thing a person can do differently. It might be unwelcome, but it isn't confusing.

Late is the second, and it's the more common failure among technical leads because we tell ourselves we're waiting for the right moment. The right moment was Thursday. By the time the quarterly review comes round, you're asking someone to relitigate an event from nine weeks ago that they remember differently, and they will reasonably wonder why you sat on it.

There's a deeper cost to storing it up. Feedback held for a quarter arrives with interest on it. You've watched the behaviour four more times, you're now mildly annoyed, and that leaks into your delivery no matter how carefully you phrase it. The person hears the annoyance, not the point.

Say it within a couple of days, while it's small and while you're still neutral about it.

The rule is old and it holds up: praise in public, correct in private.

Public praise costs you nothing and it's one of the few genuinely free things in the job. Specific, in the channel or the standup, naming what they did. "Ravi spotted the certificate expiry before it took out the portal" travels. "Great work everyone" does not, and repeated often enough it reads as noise.

Correction needs a room with a door, or a private message, or a walk. Not because the message is shameful, but because a person who is being observed while receiving criticism is spending most of their attention on how they look. They can't think about what you said until later, and by then they've spent the intervening hours composing a defence.

The exception people ask about: what if the mistake was public? Somebody said something factually wrong to a client, or committed to a date in front of a room. You can correct the fact in public, neutrally, right then. "Just to be accurate, the migration date is the 14th, not the 7th." That's correcting information. The conversation about why they committed to a date they hadn't checked happens afterwards, privately. Two different conversations, and conflating them is how you get a team that stops speaking up in meetings.

Here's the shape I'd use, from a real situation with the details changed.

A 32-person technology team at a veterinary group. A senior engineer finished an on-call rotation and went on leave without handing over two open incidents. Not malicious, just tired. His lead found out on the Monday when a practice manager asked about a ticket nobody was tracking.

The sandwich version would have been: "You've had a really strong quarter, the caching work was excellent. One small thing, the handover last week was a bit light. But overall we're really happy with how you're doing."

He'd have heard: strong quarter, they're happy. The handover would have happened again.

What she said instead, on the Tuesday, in a room with a door, in about forty seconds: "When you went on leave on Friday, incidents 4412 and 4418 weren't handed over. A practice chased one of them on Monday and nobody here knew it was open. What happened?"

Then she stopped and let him answer. It turned out he'd tried to hand over to someone who was in a workshop all afternoon, and had run out of time. So the fix wasn't a lecture about diligence, it was a rule that handover happens in writing in the channel regardless of whether a conversation occurs.

She told him the caching work was excellent on the Wednesday, in the team channel, unattached to anything. He believed it, because it wasn't attached to anything.

Give the feedback, feel relieved, never check. That's the standard pattern, and it's why the same conversation happens twice a year forever.

Put a date on it when you deliver it. Three weeks out, four, whatever fits the thing. Then actually look, and say what you saw. "The last two handovers were in the channel, both clear. That's sorted, thank you." Thirty seconds, and it does two jobs: it tells the person the change was noticed, and it tells them you meant it the first time.

If nothing changed, that's a different and more serious conversation, and it's one you've now earned the right to have.

You're sitting on a piece of feedback right now. Almost everyone reading this is, and you've already thought of the name.

Book fifteen minutes with that person before Wednesday. Write one sentence beforehand describing what you actually observed, with the day and the specifics in it, and no adjectives about them as a person. Say the sentence, ask what happened, and put a date in your calendar three weeks out to check whether it changed.