Tracking your wins all year: the log that writes your review
Every performance review is written twice: once by the year you actually had, and once by the year you can remember in the forty minutes before the form is due. The second version is worse — shorter, vaguer, and strangely heavy on whatever happened in the last six weeks. The fix is not self-promotion. It's record-keeping: a small, boring log, kept while the evidence is fresh, that turns review season from archaeology into assembly.
Your memory is the worst archive
The case for the log starts with how memory actually behaves. Negative experiences stick harder than positive ones — you remember the stressful deadline, not the fact that you delivered early — so a year recalled from memory systematically under-reports the wins and over-reports the fires. And it's not just you: as Julia Evans puts it in the best-known version of this practice, your manager doesn't remember everything important you did either — and if you're honest, neither do you. The document she popularized, the brag document, is simply a running list of things you did that have value for your employer, kept so the review conversation works from a record instead of two people's patchy recollections. It doesn't need to be impressive week to week. Ten bulleted pages for a full year of work is, by her account, not too much — the document is allowed to be comprehensive, because its job is memory, not marketing.
The ten-minute weekly log
The working version takes about ten minutes on a Friday — ideally folded into a weekly review you already do — and answers three questions:
- What did I ship or complete? Projects delivered, tasks finished, documents written, things that moved from in-progress to done.
- What problems did I solve? Blockers removed, conflicts resolved, questions answered, the quiet fixes. These get under-logged because they feel like “just doing the job” — but solving problems is the job, and it counts.
- What did I learn or improve? New skills, a process made smoother, a relationship built. Growth counts even when it produces no tangible output that week.
Three lines a week is a good week. The entry format matters less than two habits layered on top of it. Capture the numbers while you have them: the metric that proves the win — turnaround cut, queue cleared, error rate down — is often visible only in the system, only now. A log entry that says “improved reporting” is a claim; one that says “weekly report now takes 40 minutes instead of 3 hours (timed twice in March)” is evidence. And save praise with its context: when a complimentary email or message arrives, drop it in the log with who sent it and what it was about. Career guides have advised keeping an accolade file for decades — the Army's version for recruits is literally a book of collected commendations — because third-party words, quoted with attribution, carry weight your own summary cannot.
What counts as a win worth logging
New loggers under-count in predictable places. Log the glue work: onboarding a new colleague, documenting the thing only you knew, organizing the process everyone uses — Evans' structure explicitly includes mentoring, leadership and documentation alongside projects, because reviews that only count shipped projects misdescribe most real jobs. Log work that prevented something: the error caught, the deadline rescued in week two rather than week ten; prevention is invisible by design, so the log is its only witness. Log work that didn't land, with the lesson attached — a project that was cancelled after your analysis showed it shouldn't proceed is a contribution, and the log is where its reasoning survives. And log credentials and development as they happen: certifications, training, awards and nominations are exactly the entries nobody can reconstruct in December.
The monthly roll-up
A weekly log is raw material; the roll-up is what makes it usable. Evans' structure suggests rolling the log up monthly or quarterly into summaries organized by project and goal: what the project was, your specific contribution, its impact, who you worked with and who couldn't have done their part without yours. Twenty minutes, once a month, while the weeks are still legible. The roll-up is also where themes surface — three entries about unblocking other teams is a strength your review should name; three about documentation is a case for the work you want next year. Keep the whole file somewhere you control: one practical warning from career guidance is that your employer owns their equipment and you can lose access to it, so your personal copy of the log belongs on your own machine or account, updated as you go.
Review season: assemble, don't remember
When the form arrives, the work is editing, not excavation. Pull the year's roll-ups under the review's headings — goals, projects, growth — quote the praise with its sources, and let the numbers you captured in the moment do the arguing. The same file then does double duty all year: it is the evidence base for a raise conversation, the raw material for updating a CV while the details are true, and — shared in summary with your manager at a monthly one-on-one — the easiest way to make sure the record they're forming matches the year you're actually having.
Anatomy of a useful entry
The difference between a log that writes a review and a diary that doesn't is entry quality, and it follows a four-part shape: what was done, for whom, what it changed, and the evidence link. Compare “Worked on the onboarding guide” with “Rewrote the onboarding guide for the spring intake (for: new hires and their buddies); buddy questions in the first week dropped from daily to twice that week by their lead's count; doc link + the lead's thank-you message saved below.” The second entry took forty seconds longer to write and does four jobs the first cannot: it names a beneficiary, it carries a before-and-after, it points at proof, and it banks third-party credit in the sender's own words. When you write the entry, also answer the question reviewers actually ask — not “what did you do?” but “what would have happened if you hadn't?” Work whose absence would have caused a visible problem is impact; work whose absence nobody would notice is activity, and the log should be honest about which is which.
Start Friday: three questions, ten minutes, one file you own. The first entry is the hardest because it feels trivial. By the fourth Friday it's a habit, and by review season it's the difference between “I worked on various projects” and a year of dated, numbered, quoted evidence.
Frequently asked questions
Isn't this just bragging? The document's audience order matters: it's written for future-you first, your manager second, and a review committee third. Keeping an accurate record of your work is bookkeeping; the bragging framing is just the memorable name Evans gave it.
What if my year was genuinely thin? The log tells you in October instead of at the review — early enough to ask for the project, the training, or the responsibility that would change it. That's a feature: a thin log is diagnostic, not just disappointing.
Should my manager see it? A summary version, yes — many people mark one one-on-one a month as the career conversation and walk through the roll-up. Keep the raw log, drafts and personal copy yours.