Performance review notes: how to keep fair notes all year

Review season arrives, you open the form, and you try to remember the year. What comes back is mostly the last six weeks: the project that just shipped, the meeting that went badly on Tuesday. The other forty-six weeks are gone.

That is recency bias, and it makes reviews less fair for everyone, including the people who did their best work in March. The fix is not a better memory. It is short performance review notes, written through the year, on the day things happen. This guide covers what to write, how often, and how to turn a year of notes into a review.

Why reviews drift toward the last six weeks

Memory keeps what is recent and what was emotional. A quiet, steady quarter leaves almost no trace. A single tense week leaves a lot. So a review written from memory overweights the end of the year and the dramatic moments, and underweights everything else.

It also tends to drift toward labels. “Strong communicator.” “Needs to be more proactive.” Labels are what is left when the details are gone, and they are hard to act on. Nobody knows what to do differently after reading “be more proactive”.

What a useful observation looks like

An observation is two or three sentences written the same day:

1. The situation. Where and when.
2. What the person did. The behavior you saw.
3. What it changed. The effect on the work, the team or a customer.

Facts you saw, not labels. Compare:

Label	Observation
Great team player	In Tuesday’s design review she asked the quiet people for their view first, and two good ideas came from it.
Needs to be more proactive	The release slipped two days because a test failure he saw on Monday was not raised until Wednesday.
Strong with customers	On the call with the delayed customer, he explained the new date and the reason before they asked. They renewed the next week.

The second column is useful a year later. The first is not, and it is also the kind of thing people argue with in a review, because there is nothing to point to.

Write both kinds

Write what went well as often as what could grow. Two reasons:

• Feedback is easier to give and to hear when it is balanced. A review with only growth notes reads like a case file, even when it is not meant as one.
• Good work is easy to forget. Problems demand attention when they happen; quiet good work does not, so it goes unrecorded unless you make a habit of it.

If one side is empty for three months, that is worth noticing. “Nothing in went well” usually means you have not been looking, not that nothing went well.

Growth notes are not a file against someone. They are what makes the next conversation specific. Most growth notes should reach the person long before review time, in a 1:1 or right after the moment. The review should hold no surprises.

How often to write

A habit that works for most managers: at least one observation per direct report every two weeks, written in two minutes, on the day. For a team of six, that is about 150 short notes a year, and about six minutes a week of writing.

The trigger is simple. When you catch yourself thinking “that was good” or “that did not land”, write it down before the next meeting starts. A 1:1 is another natural place to note one; see one-on-one meetings.

Turning a year of notes into a review

At review time, put the period’s notes in one place, grouped by kind, together with the work the person finished. Then write the review from there:

• Read everything first, before writing a word. Patterns show up that single notes do not.
• Pick three themes, usually two strengths and one area to grow, each backed by two or three observations.
• Quote the specifics. “In the March release…” carries more weight than any adjective.
• Check the balance. If your draft is all one side, go back to the notes on the other.

Keep reviews and goals apart

Observations describe how someone worked. OKR scores describe whether the team’s bets paid off. Mixing the two pushes people toward safe targets; there is more on that in common OKR mistakes.

How Manager Kit helps you keep fair notes

In Manager Kit, each person’s page has an Observations tab. A note is one of three kinds, went well, to grow or a plain note, and you can write one from the person’s page or during a 1:1. The tab shows the balance of the last 90 days and nudges you when one side is empty, and a direct report’s page reminds you when there has been no observation for 30 days. At review time, Period summary puts any period’s notes and finished work into one plain text to copy into your company’s form. A passphrase in Settings → Privacy keeps observations encrypted on your computer. Forget it and those notes cannot be recovered, by you or by us.