Performance review prep: build the record before you write the review

There are two ways to sit down to a self-review.

You can try to reconstruct the year. Open the calendar. Search old messages. Scroll through project folders. Try to remember what you were doing in February and whether that thing in June turned out to matter.

Or you can start with a record you already have.

The difference isn't that one person has a better memory or is more disciplined. One simply kept the details while they were still easy to know.

By the time review season arrives, the work shouldn't be remembering the year. It should be deciding which parts of it best explain what you contributed.

Keep what will be hard to reconstruct

A calendar can tell you that a meeting happened. A project tracker can tell you that something shipped.

Neither necessarily tells you what was difficult, what you changed, why your part mattered, or what someone said afterward. Those are the details most likely to disappear.

When something feels worth keeping, try to capture four things:

You won't have all four every time. You don't need to.

The goal isn't to write the review as you go. It's to keep enough of the raw material that you don't have to recreate it later.

Keep the detail while it still feels ordinary

One reason good review examples disappear is that work stops feeling notable once it becomes normal.

You solve the recurring problem and then stop having the problem. You take on something that once felt like a stretch and six months later it simply feels like your job. You get a thoughtful message from a colleague, appreciate it, and continue with your afternoon.

By November, the new process is just the process. The difficult responsibility is just something you do. The message is somewhere in a thread you may never find again.

Write those things down before familiarity edits them out.

Feedback is especially worth keeping when you're permitted to retain it. Your own summary can be reconstructed later. Someone else's words usually can't.

Don't turn every month into a performance review

You do not need to evaluate yourself every week. In fact, that can make the practice harder.

When something happens, record it plainly. Then every so often, take a few minutes to look back. You might ask:

• What happened recently that I haven't written down?
• Did anyone give me feedback I may want later?
• What went wrong, and what did I do differently afterward?
• Did I take on something that wasn't mine before?
• Which moments still seem important now that a little time has passed?

That last question matters. Not everything worth recording will belong in a review. And not everything that looked important in March will still matter in November.

You don't have to know which is which when you capture it.

When review season comes, select before you write

This is the part that gets a process, because it only happens once a cycle.

Start with the record, not the form. Read what you kept from the period and notice what repeats.

Maybe several of your strongest examples involve simplifying work that had become unnecessarily complicated. Maybe you kept stepping into difficult customer situations. Maybe your role quietly expanded from doing the work to helping other people do it well.

Those patterns are more useful than a month-by-month recap. A chronological review often gives everything equal weight: January, I did this. February, I did this. March, I did this. But a year of work rarely makes sense because of the order in which it happened.

Group the strongest examples around the ideas they support. Depending on your work, that might be customer impact, better operations, craft or technical depth, collaboration, judgment, leadership, or expanded scope.

Don't decide the themes first and force the year into them. See what the record actually says.

Once you have the record, the process gets much simpler:

You won't use everything you kept. That's a feature of having a source record, not a problem with it. You kept the year so that later you could choose.

Show what changed, including when nothing shipped

Compare these:

The difference isn't polish. The second version gives the reader something the first one doesn't: a before, your contribution, and an after. That's usually enough.

Use numbers when they genuinely tell the story, and don't manufacture one because an accomplishment seems more legitimate with a percentage attached. Some work is naturally measurable and some isn't. Neither becomes more real by forcing it into the other's language.

The same move works for the contributions that produced no obvious artifact, which are often the hardest to find at review time. The problem you prevented. The decision you helped clarify. The person you got unstuck. The difficult conversation you handled well. The context you carried between teams when nobody else had the whole picture.

These sound vague when you describe them as traits.

You don't need to label yourself collaborative. The example does the work.

Keep the parts that didn't go perfectly

A useful record shouldn't contain only wins.

Keep the project that missed. The approach you changed. The call you would make differently now. The responsibility you weren't ready for at first.

Not because every mistake belongs in your self-review. Because sometimes the most useful evidence of growth is the distance between how you handled something then and how you would handle it now.

If the review asks what you learned, where you struggled, or what you want to develop next, you won't have to manufacture reflection on demand. You'll have something real to draw from. If writing any of it down still feels like self-promotion, that's what a brag document for people who hate bragging is about.

See where the year points

A good record can answer questions the review form never asks.

What work did you keep volunteering for? Where did people repeatedly turn to you? What became easier over the course of the year? What responsibility gradually became yours? Which entries still make you think, I want more of that?

Sometimes the clearest clue about what you want next isn't a goal you wrote six months ago. It's the pattern in what you've already been doing.

Make review season an editing job

Worth Noting is built for the part that happens before the self-review.

Keep a line when something happens. Add the context that's likely to disappear. Save feedback you're allowed to keep while you can still find it.

Then, when review season comes around, you can search and filter the record you've built, then export what belongs. With Pro, that can be a Review PDF with only the fields you choose.

You still have to decide what the year meant. You just don't have to remember it from scratch.

Next: how to track accomplishments without creating more work, or 50+ work accomplishment examples.

Make your next review an editing job. Start your record.