How to Take Notes for a Performance Review

The week before a performance review, most people do the same thing: they sit down and try to remember everything they did this year. It goes badly. You'll recall the last six weeks in vivid detail, one or two dramatic wins from months ago, and almost nothing in between. That's not a discipline problem, it's how memory works. The forgetting curve is steep by design, and a year is a long time for anything without a written trail to survive it. The result is a self-assessment that undersells you, not because the work wasn't good, but because you genuinely forgot half of it.

The fix isn't a better memory. It's not needing one.

Keep a running log, not a memory exercise

A brag document (also called a work log or achievement log) is a running list of what you did, kept as you do it, not reconstructed afterward. Each entry is small: a shipped feature, a piece of positive feedback, a metric that moved, a problem you solved that saved someone else time. The moment something happens is the cheapest moment to write it down, because it's still specific in your head instead of a fuzzy shape you'll spend an hour trying to redate later.

This only works if capture is low friction. If logging an entry means opening a spreadsheet, finding the right tab, and formatting a row, you'll do it for two weeks and stop. The capture habit survives on speed: one note, dated, tagged with a project or a skill, done in under a minute. A single running note works fine too, newest entry on top, so there's no system to maintain.

What's worth logging:

  • Anything you shipped or finished, with a number if there is one (users affected, time saved, revenue, bugs closed)
  • Feedback someone gave you unprompted, in their words, not your paraphrase
  • A problem you caught before it became one, even if nobody asked you to
  • Something you learned or a skill you used for the first time
  • Help you gave someone else that isn't visible in your own output

Tag entries loosely by quarter or project so you can filter fast when review season arrives. Tags beat folders here specifically because one entry often belongs to more than one category, a shipped feature is both a project and a skill demonstration.

Before the review: pull from the log, don't rebuild it

When it's time to prepare, your job shifts from remembering to selecting. Review what you've captured and pick the entries that map to what actually gets evaluated, usually your team's goals or the criteria on the review form. Write a short list of concrete questions you want answered too, not vague ones like "how am I doing," but specific ones: what's the one thing standing between you and the next level, which project mattered most from your manager's side, what got missed that you should have flagged sooner. A list of real questions makes the meeting a conversation instead of something that happens to you.

During the review: capture the feedback accurately

The instinct in the room is to remember the compliments and blur the criticism, or the reverse if you're anxious. Neither serves you. Write down what's actually said, as close to verbatim as you can, especially anything specific and especially anything you disagree with in the moment, you can process the disagreement later with a clear head. Vague praise ("great year") is worth less than specific praise ("the migration you led saved the team a quarter of rework"), and only the specific version is useful the next time you need to advocate for yourself.

After: turn action items into next steps

A review that ends with commitments and no record of them is a review that didn't happen. Whatever came out of it, a growth area, a goal for next quarter, a skill to build, write it down as an actual task with a date attached, not a memory you're trusting yourself to carry. This is also where the running log resets: the next entry in your brag document can be the first proof that you acted on what you heard.

We built this loop into Clair Mind on purpose. A quick note for each win as it happens, tags to pull them back up by project, and asking your notes what you shipped this quarter instead of scrolling to find out. It's a small habit that only pays off if you keep it going past review season, not just before it.

The honest version of this advice is that a brag document only works if you actually write in it. Not every day, not with ceremony, just often enough that nothing good gets lost between now and the next time someone asks what you've been working on.

More in How-to Guides

62 more notes on this branch.

Clair Mind connects your own notes exactly like this — automatically, privately, on your iPhone. Get the app →