[NTTP]
Work & Meetings

How to write a performance review that is actually useful

September 20, 2026 · 4 min read

Most performance reviews fail for the same reason: they are built out of vague traits instead of real evidence. “Great team player.” “Needs to communicate better.” Both sentences could describe almost anyone, which means they tell the reader almost nothing. A review that actually helps someone, whether it is about your own work or a report’s, has to be built from the concrete examples underneath the trait, not the trait itself.

Specific beats generic, every time

A strength is only useful if it is tied to something that actually happened. Instead of “strong communicator,” something like “kept the client updated through a difficult delay without them ever having to chase for news” tells the reader exactly what to keep doing. The same goes for areas of growth. “Needs to be more proactive” gives someone nothing to act on. “Flagged the staffing problem two weeks after it started affecting the timeline, rather than at the first sign of trouble” tells them precisely what to change next time. The test for every line in a review is simple: could this sentence describe a different person doing something completely different? If yes, it needs a concrete example underneath it.

Two voices, one honest standard

A self-review and a review of someone else need different voices but the same honesty. Writing about your own work, the trap is swinging to one extreme or the other: false modesty that buries real wins, or overselling that inflates a routine quarter into a highlight reel. Aim for plain and confident: state what happened, let the result speak for itself, and resist the urge to either shrink it or dress it up. Writing about someone else, the standard is fairness backed by evidence. Every strength and every growth area should be something you could defend with a specific moment if the person asked “can you give me an example of that?”

A thin section is fine. A padded one is not

Not every review period has a rich list of growth areas, and not every quarter produces three standout wins. If your notes are thin on one side, let the review be thin there too, or say plainly that there is little to add. Inventing a growth area to look balanced, or inventing praise to soften real criticism, does not make the review more useful; it makes it less trustworthy, and the reader usually notices when a line does not match anything they actually did.

Summary: Delivered consistently strong client work this quarter, including leading the onboarding revamp that visibly cut new-hire ramp time. The main area to develop is speaking up earlier when something is off track, rather than letting a small delay become a bigger one. Strengths: - Led the onboarding revamp end to end and it noticeably cut how long new hires took to get up to speed - Reliable under pressure; stepped in to cover a teammate's workload during a busy sprint without being asked Areas for growth: - Tends to go quiet in disagreements rather than push back, which occasionally let a wrong assumption stand longer than it should have - A couple of deadlines slipped without an early heads-up; flagging risk as soon as it appears would give the team more room to adjust

Common mistakes

← All guides