How to write a performance review when you cannot remember Q1
Review season is a few weeks away. Soon your HR system is going to open the review forms, and you are going to sit down in front of a blank box that asks you to describe a person’s entire year.
And you will remember the last three weeks.
That is not a character flaw. It is how memory works. The recent stuff is loud and the rest of the year is quiet, so the review you write from memory is really a review of October and November with a sentence about a project in March that you happen to remember because it went badly. The person reading it gets a distorted picture. The person it is about gets a raise, or does not, partly on the strength of what you could recall on a Tuesday afternoon.
If you are a first-time manager, this is probably the first time anyone has asked you to do this, and nobody showed you how. So here is the version I would want if I were sitting in front of that blank box.
Do not start writing. Start reconstructing.
The mistake is opening the form first. The form asks you to summarize, so you summarize from memory, and the memory is the problem. Spend the first hour rebuilding the year instead, from sources that were written down at the time and cannot be distorted by how you feel about the person today.
There are four places to look, and all four take less time than you think.
Your calendar. Scroll back to January and read the meeting titles. Your calendar is a record of what the team actually spent time on, month by month, and it will surface three or four things you had completely forgotten.
Their work. Wherever the work lives, the ticket tracker, the repo, the shared drive, the CRM, go back twelve months and look at what shipped and who shipped it. You are looking for outcomes with dates attached.
Your messages. Search your own Slack or email for their name. You are not reading conversations, you are looking for the moments you reacted to something, good or bad. Those reactions are dated evidence of what you noticed at the time.
Their self-review, if your company asks for one. Read it before you write, not after. Not because you are going to agree with it, but because it will remind you of work you never saw. The most common gap in a first review is not a disagreement about quality. It is the manager not knowing something happened.
Sort what you find into four buckets.
Once you have a page of raw material, sort it. Outcomes, which is what they delivered. Behavior, which is how they worked with other people. Growth, which is what they can do now that they could not do in January. Gaps, which is what is still missing.
The growth bucket is the one first-time managers skip, and it is the one the person cares about most. A review that lists four outcomes and no growth reads like a status report about a resource. A review that can name a specific thing this person got better at over twelve months reads like it was written by someone who was paying attention.
Write the evidence before you write the rating.
Every claim in a review should have a thing attached to it. Not “strong communicator.” Instead, “rewrote the onboarding doc in April after the two new hires got stuck in the same place, and the next hire got through it without asking.”
The test is simple. If you can delete the name from a sentence and it still makes sense about anyone on your team, the sentence is not doing any work. Cut it and put a real example in its place.
This is also where reconstruction pays off. You cannot write specifics from memory in November. You can write them from a calendar and a ticket list.
Say the hard thing once, plainly, with a date attached.
If there is a gap, the review is not the place to introduce it. If this is the first your report is hearing about a problem in a written review, the problem is not their performance, it is that you did not say it in March.
You still have to write it. Write it once, in plain words, with a specific instance and a date, and then write what you want instead. Do not bury it between two compliments. Everyone can see the structure and it makes the praise sound fake too.
If it genuinely is the first time you are raising it, say that out loud in the meeting. “I should have told you this in the spring and I did not.” That costs you nothing and it buys back most of the trust.
Then close the loop.
Deliver the review, then put the two or three things you agreed on into your next 1:1 and check them at the four-week mark. A review that changes nothing by February was a writing exercise.
The actual fix is upstream.
Everything above is recovery. It works, and you should not have to do it twice.
The reason review season is painful is that the record of a year is being assembled in one afternoon from a memory that holds three weeks. The alternative is not more discipline in November. It is five minutes after each 1:1, all year, writing down four things. What they said. What changed. What I owe them. What I noticed.
Do that for eight months and the review writes itself, because the review is just a summary of a record that already exists. You are not remembering the year. You are reading it.
That is the whole reason I built Drive My Path. It is a place to run weekly 1:1s and keep the record, so that review season is a reading exercise instead of an archaeology project. It is free to start for up to 4 teammates, and there is a Solo plan at $12 a month or $120 a year that includes review prep, with a 30-day trial and no card. If you want to look, start here.
But the method above works in a text file. Please use it either way. Somebody on your team is going to be read a description of their year in a few weeks, and it is worth more than what you can remember on a Tuesday.