How to make peer feedback useful, not awkward

Peer feedback is usually the most valuable input a firm collects and then wastes. The colleagues who pair on a build, share a client call, or carry the slack when someone coasts see the day-to-day — reliability, craft, how a person actually works on a team — that a rotating lead never witnesses. It turns awkward and useless for two fixable reasons: no clear purpose and fear of consequences. Fix both. Give peer feedback one job — help a colleague grow, not judge them — ask specific behavioural questions instead of "rate your peer 1–5," collect it from the people who actually worked together while the engagement is fresh, keep it separate from the rating so nobody sanitises or colludes, and make sure the person turns it into an action. Structured that way, peers give honest, rich, genuinely useful feedback — and stop dreading the form. The awkwardness isn't human nature; it's a design flaw.

The stakes are in the numbers. A single reviewer's read is unreliable — about 62% of rating variance is the idiosyncratic rater, not the person (Scullen, Mount & Goff, Journal of Applied Psychology, 2000) — which is exactly why the independent, close-up viewpoint of a peer matters. But feedback is not automatically useful: across 607 studies it lifted performance only modestly (d ≈ .41), and over a third of interventions made performance worse (Kluger & DeNisi, Psychological Bulletin, 1996). Purpose and delivery decide which side of that line your peer feedback lands on.

Why is peer feedback worth the effort?

Because peers are the closest witnesses to the work. In a firm of rotating leads, they are often the only consistent observers of how someone really operates day to day. A partner or engagement manager sees the deck, the client outcome, the milestone — the visible surface. The peer sees the process: who unblocked the junior at 6pm, who quietly redid a sloppy handoff, who went silent when the scope slipped.

That close-up view matters more than it looks, because one reviewer's rating is dominated by the rater's own idiosyncrasies — about 62% of the variance is the rater, not the person (Scullen, Mount & Goff, Journal of Applied Psychology, 2000). A second, independent vantage point isn't a nicety; it's how you get nearer the truth. Peers also cover a blind spot leads structurally can't: collaboration, generosity, reliability — the behaviours that make a team fast and never show up in a solo deliverable. Waste that input and you're rating people on half the evidence.

Why does peer feedback so often turn awkward or useless?

For two fixable reasons: no clear purpose, and fear of consequences. When people don't know what the feedback is for, they default to bland ("great to work with!") or generic. When they suspect it will feed a rating, a bonus, or a partner-track decision, two failure modes appear. They sanitise — nobody wants to hurt a colleague they'll be staffed with again next quarter — or they collude and retaliate: you protect my score, I'll protect yours. Either way the signal collapses into noise.

And feedback isn't risk-free even when it flows. Over a third of feedback interventions actually reduced performance (Kluger & DeNisi, Psychological Bulletin, 1996). Add the fact that candour depends on safety — people withhold when speaking up feels risky (Edmondson, Administrative Science Quarterly, 1999) — and an anonymous 1–5 form dropped onto busy, billable people produces exactly what you'd expect: thin, guarded, or quietly weaponised. The form isn't broken because peers are cowards. It's broken because no one told them what it was for and left them afraid of what it would do.

Developmental or evaluative — what should peer feedback be for?

Developmental. Give it one job: help a colleague grow. The moment peer input feeds the rating, comp, or ranking, honesty becomes expensive and people manage the score instead of telling the truth. Keep peer feedback on the development side of the line, and keep the grade to the calibrated cycle owned by the leads who staffed the work — feedback and appraisal are different jobs, and fusing them makes candour costly (DeNisi & Murphy, Journal of Applied Psychology, 2017). Developmental doesn't mean gentle; it means aimed at next time rather than a verdict on last time.

And don't expect the form itself to change anyone. After multisource feedback, measured improvement is small across every source — largest from direct reports, smaller from peers, essentially nil for self-ratings (Smither, London & Reilly, Personnel Psychology, 2005). What actually moves performance is the follow-up: coaching and a concrete goal. Feedback is receiver-driven — it works only when the person can take it in and use it (Stone & Heen, Thanks for the Feedback, 2014). Peer feedback earns its keep only when it turns into an action.

What questions actually produce useful peer feedback?

Behavioural ones. Ask what the person did and what it was like to work with them — not for a verdict or a score. "Rate teamwork 1–5" produces noise: people rate others' abstract traits unreliably, and most of that score reflects the rater rather than the person (Buckingham & Goodall, "The Feedback Fallacy," Harvard Business Review, 2019). Ask instead about the rater's own experience of the work.

1. What should they keep doing? The specific strengths worth doubling down on — named, not "good team player."
2. What would make working with them easier? The one friction, framed forward — the single most useful thing a peer can offer.
3. Describe one moment. Anchor to a single observable situation, not a general impression — a behaviour, not a label (Center for Creative Leadership, SBI model).
4. Where did they help you or the client? Surfaces the invisible collaboration a lead never sees.
5. One thing for the next engagement. Forces a single, actionable takeaway instead of a report card.

Behavioural, first-person, specific — that's the difference between "he's a 4/5 on communication" and "he rewrote the client email so the junior wasn't thrown under the bus — do that earlier and louder."

When, and from whom, should you collect it?

From the people who actually worked together, around the moment an engagement wraps, while memory is fresh. Not a blanket, everyone-rates-everyone blast — that just yields thin feedback from people who barely overlapped.

1. The right people. The two or three colleagues who genuinely collaborated on the engagement — paired, handed off, shared the client. Proximity is the whole point; someone who shared one stand-up isn't a witness.
2. The right moment. At or just after the engagement debrief, not eleven months later at annual review. Detail decays fast; captured fresh, it stays specific.
3. The right amount. A couple of short, focused requests beat a mass survey. Multisource feedback makes a difference only when it's done sensitively, with questions that are short, clear and relevant to the job (CIPD, 360-degree feedback).
4. Per engagement, not per year. Capture a small note each time so it accumulates into the growth picture — rather than being reconstructed, or invented, under deadline.

Signed or anonymous — how do you keep it safe without breeding venting?

Signed by default; protected only when there's a real reason. Anonymous-by-default feels safe, but it breeds venting and score-settling — and in a small agency team, anonymity is a fiction anyway, because everyone knows who was on the engagement. Attributable feedback that the person actually sees builds trust and forces the giver to be constructive; you write differently when your name is on it.

What makes signed feedback safe isn't hiding names — it's psychological safety, the shared sense that honesty won't be punished (Edmondson, Administrative Science Quarterly, 1999), plus the guarantee that the feedback is developmental and won't be quietly fed into someone's rating. Keep an escape hatch — a confidential channel to raise a serious concern (harassment, ethics) with a lead — but don't make anonymity the default for everyday growth feedback.

1. Signed and shared with the person → trust, accountability, and better-written feedback.
2. Anonymous-by-default → venting, sanitising, and nobody owning their words.
3. A separate confidential channel → for genuine concerns only, kept apart from growth feedback.

How do you turn peer feedback into action across rotating project teams?

This is where peer feedback stops being a form and becomes part of how the firm grows people. In an agency or boutique, people are staffed across engagements under different leads, rated per engagement, and no single reviewer saw the whole year — so the peer's close-up view is often the most continuous record you have. Make it operational:

1. Capture per engagement, lightly. Two or three behavioural notes from real collaborators at each debrief — fresh, specific, low-cost. That cadence is what makes peer input comparable at calibration instead of a once-a-year scramble.
2. Roll it into the growth picture, not the rating. Peer themes feed the person's development conversation; the calibrated grade stays with the leads who staffed the work (DeNisi & Murphy, Journal of Applied Psychology, 2017).
3. Close the loop into one or two actions. Feedback pays off only when it's acted on — the follow-up, not the form, moves performance (Smither, London & Reilly, Personnel Psychology, 2005). End every round with a concrete next step, and check it at the next engagement.
4. Weight by proximity; read divergence as signal. The colleague who paired daily saw more than the one who shared a stand-up. When two peers disagree, that's information about context — not noise to average away.
5. Protect the staffing reality. Because these people will be on a team together again next quarter, keeping peer feedback developmental — never comp — is exactly what keeps it honest.

A quick peer-feedback self-check

Scored four or fewer? Book a call and we'll help you turn a dreaded peer form into feedback your teams find genuinely useful.

FAQ

Should peer feedback be anonymous?

Not by default. Anonymous-by-default breeds venting and score-settling, and in a small team it's a fiction anyway — everyone knows who was on the engagement. Signed, developmental feedback that the person actually sees builds trust and reads better. Safety comes from psychological safety and keeping the feedback out of the rating (Edmondson, Administrative Science Quarterly, 1999), not from hiding names. Keep a separate confidential channel for genuine concerns like harassment or ethics.

Should peer feedback affect someone's rating or bonus?

Keep it developmental and out of the rating. The moment it feeds comp or ranking, people sanitise or collude and the signal collapses; feedback and appraisal are different jobs (DeNisi & Murphy, Journal of Applied Psychology, 2017). Let the leads who staffed the work own the calibrated grade; let peers inform growth.

What questions should we actually ask peers?

Behavioural, first-person ones: what should they keep doing, what would make working with them easier, describe one moment, where did they help you or the client, one thing for next time. Avoid "rate teamwork 1–5" — people rate others' abstract traits unreliably, and most of the score is the rater, not the person (Buckingham & Goodall, "The Feedback Fallacy," Harvard Business Review, 2019).

Does peer feedback actually improve performance?

Only modestly, and only if it's acted on. After multisource feedback, measured improvement is small across sources and near zero for self-ratings (Smither, London & Reilly, Personnel Psychology, 2005). What moves the needle is the follow-up — coaching and a concrete goal. The form is the start of the change, not the change itself.

How often should we collect peer feedback?

Per engagement, while the work is fresh — a couple of short, focused requests from real collaborators — not one big annual blast. Captured lightly each time, it accumulates into a fair growth picture instead of being reconstructed under deadline (CIPD, 360-degree feedback).