The Error of Using a ''Compliment Sandwich'' for Serious Feedback

You’re staring at the draft of an email, the cursor blinking. In fifteen minutes, you have a performance conversation with an employee who is, in most respects, excellent. But there’s a recurring issue, a significant one, that’s damaging team morale and affecting client retention. You know you have to address it directly. Your notes for the meeting look like this: Start with praise (Q3 report was great), then the main point (abrasive in meetings), then end on a positive (valuable team member). You’re building a classic compliment sandwich, a technique you were probably taught years ago. But something feels off. You find yourself typing into your search bar, “how to give negative feedback to a good employee” because you have a sinking feeling this conversation is about to go wrong.

That feeling is your professional experience telling you the truth: for serious issues, the compliment sandwich isn’t just ineffective, it’s corrosive. The technique is seductive because it promises to soften the blow and make the conversation easier for you. But it operates on a flawed premise. Instead of making the message clearer, it creates a mixed message, a communication trap where the other person can’t tell what’s important. They are forced to respond to two opposing signals at once: praise and criticism. This cognitive dissonance means their brain will grab onto one and discard the other, almost guaranteeing they will miss the point. And worse, they’ll walk away feeling that your praise was just a disingenuous prelude to an attack, damaging the trust you need to solve the actual problem.

What’s Actually Going On Here

When you deliver a mixed message, you put the other person in a double bind. They hear, “You’re great, but you’re also a problem.” This isn’t a nuanced perspective; it’s a contradiction. Anxious or less-secure employees will only hear the criticism. The praise evaporates, and all they register is the threat. They go on the defensive, and the conversation becomes about protecting their ego, not solving the business issue. More confident or narcissistic employees will do the opposite: they’ll latch onto the praise, treat the criticism as a minor footnote, and change nothing. They leave the meeting thinking, “My boss thinks I’m a valuable team member,” genuinely missing the urgency of the core feedback.

This pattern is often reinforced by the organisation itself. The way managers are evaluated and promoted implicitly rewards those who keep things smooth and avoid overt conflict. A manager who has a tense, difficult, but ultimately productive conversation might get a reputation for being “difficult.” A manager who uses the compliment sandwich gets a reputation for being “supportive,” even if none of their employees’ underlying performance issues ever get fixed. The system rewards the appearance of harmony over the reality of progress. The compliment sandwich becomes a tool not for effective management, but for personal risk mitigation within a conflict-avoidant system. You’re not just trying to make the employee feel better; you’re trying to avoid triggering an organisational immune response.

What People Usually Try (and Why It Backfires)

Faced with this pressure, even experienced managers reach for the same broken tools. The moves feel logical, but they are designed to manage the manager’s anxiety, not to fix the problem.

• The Classic Sandwich: You deliver the feedback packaged neatly between two positive statements.

  • How it sounds: “You did a fantastic job on the Miller proposal. That said, I’m concerned about your turnaround time on internal requests. But overall, your dedication is a real asset to the team.”
  • Why it backfires: The praise feels like a setup, an insincere formality before the real criticism begins. The employee learns to brace for impact every time you compliment them, eroding trust and making future positive feedback feel unsafe.

• The Vague Softener: You avoid specifics and use abstract labels, hoping they’ll get the hint without an explicit confrontation.

  • How it sounds: “In the leadership meeting, you just need to demonstrate a bit more ‘executive presence’.”
  • Why it backfires: This isn’t feedback; it’s a judgment disguised as a suggestion. The employee has no idea what to do. What does “executive presence” mean? Talk more? Talk less? Change their posture? It’s un-actionable and feels like a personal critique, not a professional one.

• The “Drive-By” Mention: You bring up a serious issue as a casual afterthought at the end of an unrelated meeting, trying to downplay its importance.

  • How it sounds: “Great chat about the Q4 projections. Oh, and by the way, just try to be a bit more responsive on Slack with the design team.”
  • Why it backfires: By framing it as unimportant, you give them permission to treat it as unimportant. The message received is that this is a minor preference, not a major performance issue that requires immediate change.

The Move That Actually Works

The counter-intuitive but effective move is to stop trying to manage the other person’s emotions. Your job isn’t to make them feel good about receiving difficult feedback. Your job is to be clear, respectful, and focused on the shared reality of the work. This requires separating the message from the noise. Instead of sandwiching, you isolate.

This means you schedule a meeting with a single, clear purpose. You state that purpose at the outset. The goal is not to deliver a verdict, but to define a problem that you both need to solve. Your position shifts from a judge delivering a sentence to a partner in problem-solving. You are not there to talk about their value as a person or even their overall contribution. You are there to talk about a specific, observable behaviour and its impact on the business.

This approach works because it honors the other person’s professionalism. You are treating them as a capable adult who can handle a direct conversation about their work. It removes the ambiguity and the emotional whiplash of the mixed message. The conversation is no longer about whether they are “good” or “bad.” It is about a specific performance gap and what is required to close it. This clarity is a form of respect. It allows the other person to focus all their cognitive energy on the problem, rather than wasting it on trying to decode your intentions.

What This Sounds Like

These are not scripts, but illustrations of how to frame the conversation around a single, clear purpose. Notice how each line does a specific job.

• To open the meeting: “Thanks for making the time. I’ve set this meeting aside to talk about one specific topic: the client feedback from the Henderson account last week. My only goal for this conversation is to make sure we’re aligned on what happened and what we need to do next.”

  • Why it works: It immediately defines the scope and removes all ambiguity. The employee isn’t waiting for the other shoe to drop. They know exactly what the subject is.

• To state the problem using data: “In the project debrief, the client said that they felt their primary concerns weren’t addressed. I re-read the meeting summary, and I can see that the three issues they raised in the email beforehand were not covered on the final agenda.”

  • Why it works: It points to observable facts and third-party data, not your personal opinion or a vague accusation like “you’re disorganized.” It moves the issue from a personal failing to an operational breakdown.

• To connect the behaviour to the business impact: “The risk here is that the Henderson account is up for renewal in two months. If they feel we aren’t listening to their core concerns, we could lose them. We can’t afford that.”

  • Why it works: This clarifies why you are having this conversation. It’s not because you are on a power trip; it’s because there is a material consequence to the business. It makes the problem a shared one.

• To shift to a collaborative solution: “Before we talk about solutions, I want to understand your perspective. What was your read on that meeting?”

  • Why it works: It signals a shift from diagnosis to problem-solving and invites them to contribute. It presumes they are a competent professional with a valid viewpoint, which is essential for getting their buy-in on any solution.