The Comment They'll Keep: Writing Peer Feedback That Survives the Read-Back

Appraisal season has a way of making normally articulate people write like fortune cookies. A form lands in your inbox asking you to comment on a peer, and suddenly the options feel like either 'lovely to work with' or a three-paragraph grievance you've been saving since February. Neither helps the person, the manager reading it, or you.

The awkward truth is that peer feedback is a document. It gets read by people who weren't in the room. It may be summarised in a calibration meeting. Increasingly, it is shared with the person it's about. So the question isn't just 'is this honest?' It's 'does this still make sense, and still feel fair, when it's read back by someone else?'

Start with what the form is actually asking

Peer feedback is not a character reference, and it isn't a chance to settle a score. It's an input to a decision about someone's work. Read the prompt properly. If it asks about collaboration, don't use it to complain about deadlines. If it asks for one strength and one development area, don't write five of each and hope the manager sorts it out.

There's also a difference between peer feedback and upward feedback. Commenting on a colleague is one thing; commenting on your manager is another. Same principles apply, but upward feedback needs more care around power, because the person reading it may also be the person who signs off your next opportunity.

Vague praise is a quiet way of opting out

'Great team player' feels safe. It is also almost completely empty. The reader learns nothing, and the one specific comment you do make starts to carry more weight than it should. If you want to be helpful, give the person something they can actually recognise.

You don't need a personality profile. You need one moment. 'In the September migration, you spotted the duplicate records before we sent the file' tells the person what good looks like. 'You're always brilliant with detail' doesn't.

Separate what you saw from what you concluded

This is the habit that stops feedback turning into a haunting. Describe the observation, not the interpretation. 'You arrived after the agenda had been set' is an observation. 'You don't care about planning' is a story you've written about them.

The first is defensible. The second invites an argument about motive, and you probably don't have the evidence for it. Stick to what happened, when it happened and what changed as a result. If it really is a pattern, say where you saw it: 'in the two project meetings I sat in on' is more credible than 'you always'.

Don't ambush them in writing

Written feedback should not be the first time someone hears a significant concern. If it's serious, say it live first. Ask for a conversation. Then use the form to record what you've already discussed, not to drop a grenade in a shared document.

This matters even more in organisations where feedback is shared or summarised back to the person. A comment that reads as a surprise attack will be remembered as one, regardless of how carefully you phrased it.

Write it as if they'll read it, because they might

The practical test is simple: would you be comfortable reading this aloud to them? Would you be happy to put your name next to it? Would it still sound reasonable to someone who wasn't there?

If not, edit. Cut the code. 'Needs to be more visible' can mean anything from 'speak up in meetings' to 'stop going over my head'. Say which one you mean. 'Jokes about deadlines landed badly in the client call' is specific. 'Unprofessional' is a label, not feedback.

A three-line structure that works

When in doubt, use three lines. First, what you saw: a specific situation. Second, what it made possible or what got in the way: the effect on the work, not on your feelings. Third, what you'd suggest they keep doing or try next: something forward-looking.

For example, instead of 'communication needs work', try: 'In the run-up to the client review, the deck changed twice without a note in the channel. I found out on the morning. Next time, a two-line heads-up would let the rest of us plan.' That's honest, useful and hard to misread.

Upward feedback: same rules, more care

When commenting on a manager, focus on process and clarity rather than personality. 'I'd benefit from knowing which decisions are yours and which are mine' is more useful than 'you micromanage'. Use 'I' statements where you can, because you're describing your experience, not their character.

And don't use the form to settle a score. If something needs resolving, raise it directly first. The written form is a record, not a weapon.

What to leave out

Leave out scores you can't evidence, second-hand gossip, jokes, and anything about someone's personal life. Leave out the feedback sandwich, too. People can taste the bread. If you have a genuine development point, say it plainly and kindly. If you don't, say something small and true rather than something large and vague.

Before you hit submit

Read it once as the person. Read it once as their manager. Read it once as someone in HR who has to defend it. If any of those readings makes you wince, edit.

Feedback is a leadership act, even when you're not the boss. Write the comment you'd want to receive: plain, specific and fair. The test isn't whether it feels brave in the moment. It's whether it still stands up when the room reads it back.