42 weak and strong peer review feedback examples

“In sprint reviews they open with the one decision they need from us, so the meeting ends with an answer instead of a follow-up meeting.”

Why it works: It names a repeatable habit and the time it saves the group.

“When they handed me the reporting work before their leave, their note listed what was done, what was open, and who to ask, so I picked it up on Monday without a single call.”

Why it works: It describes the handoff note itself and the concrete benefit it gave the rater.

“Decisions on our shared project tend to get made in side conversations I am not in, so I usually find out a plan changed after I have already built against the old one.”

Why it works: No character judgment, just a pattern and its cost.

“In our last three handoff threads the actual request sat at the bottom of a long message, and twice I answered the wrong question. Putting the ask in the first line would save us both a round trip.”

Why it works: It points at a repeated pattern and its cost, then offers a change small enough to try tomorrow.

“When our projects overlap, they flag the dependency in writing before it becomes my problem, so I have never once been blindsided by their timeline.”

Why it works: It points at a specific habit and the exact benefit the rater gets from it.

“When I was stuck on the data migration last month, they paired with me for an afternoon and wrote down the queries we used, so the next person on the team ran it without either of us.”

Why it works: It shows what the help looked like and why it outlasted the afternoon.

“My last two review requests on our shared spec sat for three or four days, and I shipped both without their input on the parts they know best. A one-day turnaround, or a note when that will not work, would let me plan around it.”

Why it works: It describes the delay and what the work lost because of it, then asks for one agreement.

“In the onboarding design review they rejected two alternatives before the people proposing them had finished, and neither of those people spoke again that meeting. Asking one question about an idea before judging it would keep those voices in the room.”

Why it works: It describes the behaviour and its visible effect on others without calling the person difficult.

“When the vendor missed their deadline last month, they rebuilt the import script themselves over two days and posted an update before anyone had to ask where it stood.”

Why it works: It names a real event, what they did, and the part that went beyond the brief.

“The week our onboarding doc still pointed to the old tool, they rewrote it the same afternoon without being asked, so the two people who joined that week set up the right tool on day one.”

Why it works: It shows initiative through one small, checkable action and who benefited.

“This quarter, bugs they spotted outside their area got a comment in the channel and then sat unowned, so the same export issue came back twice. Opening a ticket with an owner before moving on would close the loop.”

Why it works: It separates spotting a problem from closing it without assigning blame.

“Two action items from our March retro had their name on them and were still open at the April retro with no update in between. A short note when something is going to slip would let the rest of us pick it up or re-plan.”

Why it works: It sticks to a checkable fact and asks for an early signal instead of perfection.

“On the search rewrite they broke each big ticket into pieces small enough to ship in a day, so I could review their work as it landed instead of in one huge pull request at the end.”

Why it works: It explains how they are fast, which is the part others can learn from.

“With two days left before the board deck was due, they cut the analysis down to the three charts the board would ask about, which got it out a day early and gave the founders time to rehearse.”

Why it works: It shows judgment about scope and the specific benefit it created.

“The last two estimates they gave in planning were about half the real time, so I moved my own work around twice to cover the gap. Giving a range when they are unsure would let me plan for it.”

Why it works: It names the specific slip, the knock-on effect, and one way to reduce it.

“Their standup updates on the billing ticket said "nearly done" for four days in a row, so I could not tell when to start my part. Saying what is left and when they expect to finish would let me line up behind them.”

Why it works: It quotes the behaviour, says why it matters to the rater, and asks for one specific detail.

“After our retro on the search bug, they read up on indexing and ran a short session for the team the next week. I use what they showed us most days.”

Why it works: It connects their learning to something the team now does.

“They asked to pair with me on the billing module because it was the part they knew least, and within a month they were the one answering my questions about it.”

Why it works: It shows the choice they made as well as the result.

“When I left comments on their onboarding design last month, they replied to each one defending the original choice, and I stopped leaving comments after that. Asking one question about a comment before answering it would keep the reviews coming.”

Why it works: It describes the reaction and its effect, which is hard to argue with.

“In the last two planning cycles they picked frontend tickets and passed on the API work, so I am still the only reviewer for API changes. Taking one API ticket next sprint, with me pairing, would spread that knowledge.”

Why it works: It connects a pattern to a team risk and offers a supported first step.

“Every Monday they post the three priorities for the week and what they are deprioritising, so when two requests collide I know which one to drop.”

Why it works: It names the ritual and the decision it saves the rater from making alone.

“In the last two planning sessions I raised the staffing risk and we moved on without addressing it. I cannot tell whether it was heard and set aside on purpose or just missed, and that uncertainty is what makes me stop raising things.”

Why it works: It names specific moments, the effect on the rater's behaviour, and stops short of accusing the manager of not caring.

“When design and engineering disagreed on the checkout flow, they got both of us in one room, wrote the options on the board, and let us pick. We shipped it that week.”

Why it works: It shows how they resolved friction and what came out of it.

“The roadmap for next quarter was shared as final, so the two concerns I had about the migration timeline had nowhere to go. Sharing a draft a week before it is locked would give concerns like mine a place to land.”

Why it works: It gives a real case and its cost without guessing at motives.

“When the launch date slipped, they told leadership the planning call had been theirs, and that made it safe for us to talk openly in the retro about what went wrong.”

Why it works: It shows ownership in public and the effect it had on the team.

“In our last three one-to-ones they said they would look into my promotion case, and I have not heard what happened next. A date for when I will hear back would let me plan around the answer.”

Why it works: It is countable, recent, and easy for them to act on.

“In the first week of Q3 they cut our plan from nine projects to four, and we finished all four instead of half of nine.”

Why it works: It credits a specific decision and its measurable result.

“Our last three planning meetings ran past the hour without a decision, so the team started each sprint with open questions. Ending the meeting by writing down each open decision and its owner would get us moving.”

Why it works: It names the meeting, what the team carries out of it, and one closing habit to fix it.

“They gave me the client demo in March and sat in only as backup. The notes they sent afterwards are the most useful feedback I have had this year.”

Why it works: It describes the opportunity and the follow-up that made it count.

“When I suggested in the last retro that we drop the Friday status meeting, they explained why it existed and moved to the next topic, and the rest of the retro had no other suggestions. Agreeing to try a change for two weeks, or saying what would convince them, would keep people suggesting things.”

Why it works: It describes one exchange, the chilling effect it had, and two specific ways to respond next time.

“They hand me the ambiguous problems and let me come back with an approach, then poke holes in it rather than taking it over. That is how I have gotten better at scoping work.”

Why it works: It describes what the manager actually does and the growth it produced, which is far more useful than "supportive."

“The tooling decision has been open for six weeks, and the team is now maintaining two setups while we wait. Setting a decision date and naming who makes the call would let us drop one of them.”

Why it works: It measures indecision by its cost instead of an adjective.

“Their weekly status updates on the migration start with anything that is blocked, so I can unblock them in the same hour instead of finding out on Friday.”

Why it works: It names a structural habit with a clear payoff for the manager.

“In last week's planning you mentioned the API risk to me afterwards, one to one, by which point we had already committed the sprint. Raising a risk like that in the meeting would let us schedule around it.”

Why it works: It shows they had the insight and where it needed to land.

“When our new analyst joined in May, they set up three pairing sessions without being asked, and the new analyst shipped their first change in week one.”

Why it works: It shows generosity through an action and an outcome.

“In code review this quarter you rewrote teammates' code instead of commenting on it, and two people have told me they now avoid asking you for review. Leaving comments and letting the author make the change would keep them coming to you.”

Why it works: It names a concrete behaviour and its real consequence without a label.

“When the Friday deploy broke, they stayed to trace it, wrote up what happened, and changed the checklist so the same failure cannot recur. Nobody asked them to do the last part.”

Why it works: It is a scene with a beginning and an end, and the detail (the checklist) shows the specific behaviour worth naming.

“Your execution is excellent once a task is defined. The next level for you is defining the task yourself, spotting the thing that needs doing before it lands on your plate. The doc cleanup last month is a good example of what I mean; you noticed it, but waited to be asked.”

Why it works: It separates what is already strong from the one specific thing to grow, and anchors the growth point to a real moment so it is not an abstract instruction.

“They shipped the export feature two days early and wrote the help article themselves, so support had it before the first customer asked.”

Why it works: It credits the extra step that made the work land.

“Over the last month your smaller tickets waited while you polished the reporting rewrite, so bug fixes that take an hour sat in the queue for a week. Clearing the small fixes first thing each morning would keep the queue moving.”

Why it works: It describes the trade-off being made without judging it and offers a simple routine.

“Six months ago they asked me for help with most estimates. This quarter they ran estimation for the whole team and were within a day on most tickets.”

Why it works: It shows growth as a clear before and after.

“You turned down the last two chances to present our work to other teams, and the credit went to people who did less of it. Taking the next demo slot, with me helping you prepare, would put your name on the work.”

Why it works: It shows what they are missing out on, in their own interest.