The Rule That Fixes Most Reviews
Observable behavior only. A review is a record of what someone did and what it caused, not a reading of who they are. The moment a review judges personality (attitude, energy, fit), it stops being feedback the employee can act on and starts being an opinion they can only resent. Behavior can change next quarter. Personality verdicts just sit there.
Every claim in the review should pass one test: could you point to the project, the metric, the date, or the incident? If not, either find the example or cut the claim.
Step by Step: Writing the Review
Step 1: Gather evidence before you write. Pull project lists, metrics, tickets closed, deadlines met or missed, and any notes you kept during the period. Recency bias is real. The last six weeks are not the year.
Step 2: Open with a summary that matches the rating. Two or three sentences. If the rating is exceeds expectations, the summary should make a calibration committee nod without reading further. If the words and the rating fight, rewrite until they agree.
Step 3: Strengths, each with behavior, example, impact. Not team player. Instead: volunteered to onboard two new hires in September, built the onboarding checklist the team still uses, and both hires passed QA in their first month. Same person, completely different defensibility.
Step 4: Growth areas as behavior, impact, next step. Not needs to communicate better. Instead: flagged blockers late on two October escalations, refunds sat for a week, next period surface blockers in standup the same day. One concrete change, not a trait transplant.
Step 5: Goals for next period in SMART form. Specific, measurable, achievable, relevant, time-bound. Own the onboarding checklist by end of Q1 beats improve onboarding. If you do not know the target number yet, write the placeholder and fill it in together in the meeting.
Step 6: Close forward. One or two sentences about what success looks like next period. The review should end with a direction, not a verdict.
Example: Manager Review (Excerpt)
Jordan had an exceptional period. After taking over the returns queue in August, average resolution time dropped from three days to one, and the macro library Jordan built is now standard across the support team (behavior, example, impact — no traits needed). The one area to tighten is escalation timing: two October cases sat for a week before the team heard about them, which delayed refunds. Next period, blockers get raised in standup the same day. Goals: own the new-hire onboarding checklist by end of Q1, hold first-response time under two hours.
Example: Self-Review (Excerpt)
This period I shipped the checkout redesign two weeks early and support tickets about payment errors dropped by a third (outcome with a number, tied to business impact). Where I fell short: I under-communicated during the migration in July, and two stakeholders were surprised by the cutover date. I have since started a Friday status note, and I want to keep that habit while taking on the reporting dashboard next quarter. I am not hiding the miss, and I am not volunteering for punishment either. One honest growth area with a fix already running is the strongest self-review move there is.
Phrases to Use
Consistently delivered [X] ahead of deadline. Reduced [Y] by [Z percent] by [action]. Took ownership of [failing process] and stabilized it. Needs to flag [blocker] earlier, because [observable consequence]. Next period, [specific deliverable] by [date]. Notice the pattern: every phrase has a slot for evidence. Fill the slot or drop the phrase.
Phrases to Avoid
Great attitude. Team player. Rockstar. Needs more confidence. Not a culture fit. Each one judges a person instead of describing work, none of them tells the employee what to do differently, and several create legal exposure if the review is ever read outside the room. If you catch yourself writing one, translate it: what did they actually do?
Common Mistakes
Surprising an employee with a problem never raised during the period. Rating inflation where everyone exceeds and the words say otherwise. Writing the review from the last month only. Copying last year and changing the dates. And the self-review classic: modest, vague, and forgettable, written by someone who did real work and then hid it.
Frequently Asked Questions
How do I write a self-review?
Start from outcomes, not effort. List what you delivered with numbers attached, tie each result to a team goal, name one honest growth area with the step you are already taking, and close with specific goals for next period.
What should I say in a performance review?
Say what the person observably did, the impact it had, and what changes next. Every strength needs a concrete example. Every growth area needs the behavior, the impact, and one concrete change to make.
What are good performance review phrases?
Behavior-based phrases: consistently delivered X ahead of deadline, reduced Y by Z percent, took ownership of a failing process and stabilized it. Avoid trait phrases like great attitude or team player, which prove nothing.
How long should a performance review be?
Long enough to cover the period with evidence, usually 300 to 600 words of narrative. If a strength has no example, cut the strength instead of padding.
Keep Going
Pair this with our how to write a cover letter guide when the next step is a new role, and keep your evidence sharp with the resume bullet generator.