It's Sunday night, and you have eight reviews due Monday. You open last year's document for the first person on the list, change the name, and start swapping adjectives. Reliable stays. Needs to be more proactive stays. Forty minutes later you've written something that could describe anyone on your team.
On Tuesday, someone will read that document slowly, maybe twice, and wonder what you actually think of them.
A performance review is one of the few pieces of writing that can change how a person sees their own working life. It's also one of the pieces most often written fast, late, and from memory. The result is a document that feels safe to write and does very little for the person reading it.
The review you write is mostly about last month
The first problem is your memory, not your intentions. Recency bias is well documented: when you evaluate a long stretch of time, the most recent events weigh far more heavily than the earlier ones. In a December review, October stands in for the whole year.
So the person who had a rough fall after an excellent spring gets a review that describes the fall. The person who coasted for ten months and shipped something visible in November gets praised for the year.
The second problem is the halo effect. The psychologist Edward Thorndike described it in 1920, after noticing that military officers who rated their men as good on one trait tended to rate them as good on all of them. One strong impression leaks into every other judgment. If someone is charming in meetings, you'll quietly score their analysis higher. If someone is awkward, the reverse happens.
Neither bias is a character flaw. They're how memory works when you're asked to summarize twelve months in one sitting. The fix is to stop relying on your summary and start writing from specific moments.
Why adjectives fail
Here is the sentence that fills most reviews: Jordan is a strong communicator and a great team player.
It sounds like praise, but Jordan can't do anything with it. They don't know what they did that earned it, so they don't know what to keep doing. Worse, they can't tell whether you actually noticed or just reached for the standard phrase. It reads as the same sentence you'd write for anyone.
Vague criticism is worse. Needs to show more ownership lands as a judgment about who they are, not a description of something they can change.
There is real research behind why this matters. In 1996, Avraham Kluger and Angelo DeNisi published a large meta-analysis of feedback interventions in Psychological Bulletin. On average, feedback improved performance. But in more than a third of the cases, it made performance worse. A key factor was where the feedback pointed attention. When it focused on the task, meaning what was done and how it could be done differently, it helped. When it drifted toward the self, as in what kind of person you are, it often hurt.
Adjectives are self-talk in disguise. Proactive and reliable and not detail-oriented are all statements about a person. A specific moment is a statement about a task.
Write one scene, then one effect
The structure that fixes most reviews is small. For each point you want to make, write the moment, then what it caused.
Instead of Jordan is a strong communicator, try: In the March vendor delay, you sent the client a three-line update before they asked, with the new date and what we'd do if it slipped again. They told me afterward it was the reason they stayed calm.
That sentence tells Jordan what to repeat. It also proves you were paying attention, which is half of what a review is for.
The same structure works for the hard parts. Instead of needs to show more ownership, try: When the Q3 report went out with the wrong totals, the first I heard of it was from finance. I'd like to hear about problems like that from you the same day, even before you've fixed them. It names the moment, the effect, and the behavior you want, and it says nothing about Jordan's character.
There's a side benefit. When you write about a specific moment, you can't fake it. If you can't find one, that tells you something: either you haven't been paying close enough attention, or the point you wanted to make isn't as strong as you thought.
The real work happens before you write
The best performance reviews are mostly written months in advance, in tiny pieces. The year-end document is just assembly.
If you wait until review week to remember what happened, you will get recency bias and the halo effect no matter how careful you are. If you capture moments as they happen, you get the whole year, including the quiet wins from February that nobody remembers.
It also changes how you feel about the work. Writing a review from a folder of real observations is calmer than writing one from a blank page and a vague sense of unease.
Your next moves
- Start a running notes file for each person today. One document per direct report, with dated entries. When you notice something worth mentioning, good or bad, add one or two lines right then: what happened and what it changed. Thirty seconds, no polish.
- Set a recurring fifteen-minute reminder every other Friday to add anything you've missed. This is what protects the spring from the fall.
- Rewrite every adjective in your current draft. Highlight each word like strong, reliable, proactive, or great. For each one, replace it with a specific moment and what it caused. If you can't find a moment, cut the sentence.
- Check every critical point against the task, not the person. Does it describe something that happened and a behavior you'd like to see instead? If it describes who they are, rewrite it.
- Read the review aloud before you send it. Imagine saying each sentence across the table. Anything you wouldn't say to their face, or anything that sounds like a form letter, needs another pass.
Say it first, then write it
Most managers can describe someone's work vividly in conversation and then produce wooden prose the moment they sit at a keyboard. Ask yourself what Jordan did well this year, out loud, and you'll probably tell a story with details. Type the same question into a review field and you'll get strong communicator.
So don't write it first. Talk through each person the way you'd brief a colleague who is about to take over their work: what they're good at, what happened in March, where you worry. Then work from that.
That is where Quill earns its place for me. You can speak into any app, get clean text back, and everything stays on your device, which matters when the subject is a named person's performance. Talk through the observations in the car or on a walk, let them land in your notes as text, and use a one-tap rewrite to adjust the tone only after the substance is down. The details you'd have lost are already on the page.
If you want to try it, you can find Quill at quill.lumenlabs.works. But the idea works with any recorder and a notebook. Whatever you use, capture the moment while you still remember it, and write the review from that.