How to give critical feedback without crushing someone
A teammate's work isn't good enough — the draft misses the point, the code is fragile, the deck buries the story — and you're the one who has to say so. You keep softening the message until it no longer says anything.
Where it goes wrong
Vague kindness is the most common failure: "just a few small tweaks!" followed by a rewrite teaches people not to trust your compliments. Bluntness without context misses differently — "this isn't working" lands as a judgment of the person, and a person busy defending themselves can't hear anything about the work. And the famous compliment sandwich mostly trains people to flinch whenever you say something nice.
What to do instead
- 1
Critique the work, not the person
"The intro buries the main point" can be fixed by Tuesday; "you're not a strong writer" can't be fixed at all. Keep every sentence pointed at the thing on the page.
- 2
Be specific enough to act on
"Make it punchier" is a mood; "cut the first two paragraphs and open with the result" is a task. If your feedback can't be turned into a to-do list, it isn't done yet.
- 3
Say what's working, and mean it
Genuine positives aren't padding — they tell the person what to keep, which is half the instruction. One honest "the data section is exactly right" outranks three reflexive "great job overall!"s.
- 4
Size the delivery to the stakes
Typos go in a comment; "this whole approach is off" goes in a conversation, not a 9pm message they'll reread all night. The bigger the critique, the more human the channel should be.
- 5
Leave room to be wrong
"I might be missing context — can you walk me through the approach?" costs you nothing when you're right and saves you when you're not.
Before and after
The vague pass
Looks pretty good overall! Just a few thoughts, nothing major, maybe see if it could be a bit tighter in places? But honestly it's fine either way!
The research section is strong — keep that as is. The intro buries your best finding, though: move the cost numbers into the first paragraph and cut the background to two sentences. Happy to read another pass tomorrow.
Names one thing to keep and two concrete moves, so the praise carries information instead of just cushioning.
The drive-by
This isn't what I asked for. Did you even read the brief?
This isn't matching what I had in mind, and some of that might be my brief's fault. The piece I need most is the comparison table — can we take 10 minutes before you revise?
Owns part of the gap and points at the missing piece, which lets the other person fix the work instead of defending the effort.
Try it with a real message
Common questions
Should critical feedback be in writing or face to face?
Deliver the headline live, then follow with written specifics they can work from. Reverse that order and they read your toughest sentence alone, with no tone of voice attached to it.
What if they get defensive anyway?
Defensiveness is usually about the stakes, not your wording. Don't retract — re-anchor on the shared goal: "I want this ready for Friday; what would help most?"
Does the compliment sandwich work?
Not for long — people learn the pattern fast and stop trusting the bread. Honest, specific praise works; praise deployed as anesthesia doesn't.