Jump to section
Picture the articling student who just handed you a factum with three good arguments and one missing limitation period. You want to fix the miss without crushing the person, so you reach for the old reliable: say something nice, slip the problem in the middle, close with something nice. By the time the meeting ends, the student remembers you liked the structure and has no idea the limitation issue nearly cost the client a claim.
That is the compliment sandwich, and it fails for a reason worth naming. It is designed to protect your comfort, not the other person's growth. Feedback that changes behaviour does the opposite: a little uncomfortable to give, precise, and pointed forward. Let me make the case.
Why the Compliment Sandwich Fails
The sandwich promises a hard message goes down easier between two soft ones. In practice, the structure buries the message. People are pattern-matchers. Once someone learns that praise from you is the opening move before a correction, the praise stops landing and the correction gets buried as an aside. You have trained your team to brace whenever you say something kind, which undermines the genuine compliments you will want to give later.
Worse, the sandwich muddies the signal. A junior clerk cannot tell whether the middle note was a passing observation or a real problem, so they judge it by tone. The thing you most needed them to hear is the thing your delivery taught them to discount. That is not kindness. It is a communication failure dressed up as one.
Warn. If your team goes quiet every time you say "great work," the praise is no longer information. It is the sound of a shoe about to drop.
Specific Beats Nice Every Time
"Good job on the discovery prep" tells someone nothing they can repeat. "Your chronology pulled every key date onto one page, so I walked into examinations without flipping through the file" tells them exactly what to do again. Specificity is the whole game. Vague praise feels good for a moment and teaches nothing; vague criticism feels bad and teaches nothing. Specific feedback, warm or critical, is the only kind a person can act on.
This is where a lot of well-meaning supervisors stall. They confuse being nice with being useful. Test every piece of feedback against one question: could the recipient repeat or repair the behaviour based on what you just said? If not, keep talking until they can.
Pleasant is a mood. Useful is a description of the work concrete enough that the person knows exactly what to repeat or fix. On the difference that matters
Feedback Has a Shelf Life of About a Day
Feedback decays fast. The correction you save for a quarterly review is one the person can no longer connect to a specific choice. They have written twenty memos since and cannot remember which one you mean, and even if they can, the moment to adjust has passed. Feedback delivered three months late is nearly useless for changing behaviour.
Timely does not mean instant, and it does not mean in front of the whole office. It means close enough to the work that the person still has the context loaded in their head. A same-day note after a bad client call beats a polished summary three weeks later. This is the strongest argument for lightweight, frequent check-ins over the dreaded annual sit-down.
Tip. If you find yourself saving feedback for a scheduled review, the review is too rare. Small, current corrections are worth more than one big annual reckoning.
Point at the Work, Not the Person
"You are careless" is a verdict about character. It invites defence, not change, because no one can fix who they are on the spot, and most people fight the label rather than accept it. "This affidavit went out with the client's name spelled two different ways" is a fact about a document. It sits on the desk between you, and you can both look at it. One of these is a conversation. The other puts the other person on trial.
The shift sounds small and changes everything. When you point at the work, you become an ally against a shared problem instead of a judge ruling on a person. This matters in law, where competence is bound up with identity and a bruised ego can turn into avoidance. Keep the person on your side of the table and the work on the other. That posture also keeps ordinary coaching from escalating into a difficult performance conversation: the earlier you point at the work, the less often the hard talk becomes necessary.
Ask Before You Tell
The best feedback often is not a statement at all. It is a question. "Walk me through how you decided to serve on Friday" surfaces the reasoning behind a choice, and half the time the person already knows what went sideways. When they name it themselves, they own the fix. When you name it for them, they own only your opinion of them, which is heavier and less useful to carry.
Asking first also protects you from being wrong. You did not see the whole file. Maybe the clerk served Friday because opposing counsel begged for the weekend and you would have agreed. Lead with a question and you leave room to learn something before you correct something. A shared record where the reasoning lives, whether practice notes or the matter timeline in something like A1 CMS, means fewer conversations start from a blank memory. But the tool is not the point. The habit of asking is.
| Instead of | Try |
|---|---|
| "Great work, but the cite is wrong, otherwise good." | "The Smith cite points to the wrong paragraph. Everything else is ready to file." |
| "You need to be more careful." | "Two dates in this timeline conflict with the retainer. Can we reconcile them now?" |
| "We will discuss it at your review." | "Have five minutes today? I want to flag something from this morning's call." |
| "That was the wrong call." | "Walk me through the reasoning, then I will tell you what I would have done." |
None of this is soft. Specific, same-day, work-focused feedback that starts with a question is harder to give than a sandwich, because it asks you to be clear and present instead of polished and safe. But it is the only kind people trust, and trust is what makes the next correction land without a fight. Start with your next handoff. Skip the bread, describe the work, ask one question, and watch the guardedness drain out of the room. To go further, the sibling piece on running one-on-ones that people value builds on the same posture, the rest of the people and hiring library treats feedback as part of building a firm people stay at, and you can read more on the author page or the knowledge base.
