Written feedback is harder than spoken feedback and more consequential: it arrives without your facial expression, it can be reread in the worst possible mood, and it persists. The same sentence that lands gently in a one-on-one can read as an indictment in a review comment. Yet writing feedback well is learnable, and the principles are consistent.
Describe the work and the impact, not the person
The foundation of feedback that gets heard rather than defended against:
- Person-framed (bad): "You're careless with details."
- Work-framed (good): "The last three reports each had numbers that didn't match the source data — the June one went to the client before we caught it."
Work-framed feedback is specific, checkable, and fixable. Person-framed feedback is an attack on identity, and identity defends itself instead of improving. The mechanical rewrite rule: replace every "you are X" with "the work shows X, here's an example, here's the impact."
Be specific enough to act on
"Communication could be better" is a horoscope, not feedback. The receiver should finish reading with zero guesswork about what to do differently:
- One concrete example of the pattern (recent, not archaeological).
- The impact — who was affected and how.
- What good looks like, explicitly: "For outage updates, lead with customer impact and ETA before the technical cause."
If you can't produce a specific example, you may not have feedback — you may have a vibe. Wait until you do.
Kill the softening rituals that backfire
- The sandwich. Praise-criticism-praise teaches people that your praise is a warning siren. Separate them: give genuine praise when it's earned, give criticism straight when it's needed, clearly labeled.
- Hedging into invisibility. "Maybe just possibly consider perhaps tightening..." — the receiver correctly reads this as optional and ignores it. Kind and clear beat kind and vague.
- The ambush of scope. Written feedback should never be the first time someone learns of a serious problem. Serious issues get a conversation first; the writing documents and structures what was discussed.
Reread it as the recipient — then once more, colder
Before sending, read the feedback as its recipient on a bad day. Any sentence that could be read as sarcasm, will be. Any absolute — "always," "never" — invites a counterexample hunt instead of reflection. This reread is the highest-stakes tone edit in workplace writing, and it's a natural place for a rewriting pass: a tool like Wrivio can take a draft that's accurate but sharp and return one that's accurate and hearable, with a word-level diff so you confirm the substance survived intact. The facts should never soften; the delivery almost always should.
Invite the reply
End written feedback with a genuine opening, not a verdict: "Does this match how you saw it? Happy to talk through any of it." Feedback that permits no response isn't feedback — it's a filing. And when the response comes and is uncomfortable to read: the standard you hold for giving feedback (specific, work-framed, generous) is exactly what you're owed and should model in receiving it.
Praise deserves the same craft
One asymmetry worth fixing: critical feedback gets carefully written; praise gets "great job! 🎉". Specific praise — "the way you structured the rollout doc made the exec decision take ten minutes instead of a meeting" — teaches what to repeat, and it's the cheapest retention tool that exists. Write it with the same specificity you'd spend on criticism.
