How to Keep Track of Your Accomplishments at Work

You sit down to write your self-review. You know the year was busy. You know some of it was good. And what surfaces is two things from the last six weeks and a vague sense that there was more.

This is not a memory problem, and it is not a discipline problem. It is a mismatch between how work happens and how memory files it.

Why the year disappears

Work is continuous and memory is episodic. Memory keeps things that had an edge to them, a deadline, an argument, something that went wrong. It quietly discards the competent, unremarkable weeks, which for most people is most of the year and most of the value they delivered.

There is a second effect that is worse, because it removes exactly the things you should be reporting. The accomplishments you would be proudest of are usually the ones that were difficult at the time. Once you have absorbed a skill, the difficulty evaporates from the memory of it. The migration that consumed six weeks and taught you a great deal is filed, by December, as “the migration”. You have lost the part that made it worth mentioning.

So by review season you are not recalling your year. You are recalling a highlight reel assembled by the wrong criteria.

Why “keep a brag document” usually fails

The standard advice is to keep a running document of your wins. The advice is right and almost nobody sustains it, for three reasons worth naming, because each one points at its own fix.

It has no trigger. It is a task that depends on remembering to do a task. Everything else in your week is prompted by something: a meeting invite, a notification, a person waiting. This is prompted by nothing, so it happens in the first fortnight of January and then never.

It has no payoff for months. You do the work now and collect in eleven months. Habits that pay out that far away do not survive contact with a busy quarter.

The framing is uncomfortable. Sitting down to write about how good you are is a genuinely odd thing to do, and many people quietly avoid it without ever admitting that is what happened.

Each of those is fixable, and none of the fixes is “try harder”.

The system

1. Attach it to something already in your week

Do not create a new ritual. Attach the capture to a thing that already happens: the end of your Friday, your weekly one-to-one prep, the moment you close your laptop, your sprint boundary. A recurring calendar reminder is the crudest version and it works, because the point is to be interrupted rather than to remember.

Five minutes is the target. If it takes twenty, it will not survive a bad week, and bad weeks are exactly when the interesting work happens.

2. Record evidence, not adjectives

This is the part that decides whether the log is useful a year later. Compare:

Worked on the onboarding emails. Went well.

Rewrote the onboarding email sequence. Signup completion went from 61% to 74% over six weeks. Dashboard link. Priya asked me to write up the approach for the other team.

The first is a note that you were busy. The second is something you can put in a review, in a promotion case, or in an interview answer, unchanged, twelve months from now.

Three things make an entry survive: what changed, who it mattered to, and how you know. If you have a number, take the number now, because you will not be able to reconstruct it later and the dashboard may not go back that far.

3. Keep the difficult ones, especially

When something was hard, write down that it was hard and why, in one line. That sentence is worth more than the accomplishment itself, because it is the part that will be gone by December, and it is the part that turns “I did X” into “I did X when nobody had done it before and the documentation was wrong”.

4. Capture the things that are not projects

Most logs are lists of shipped work, which undercounts most jobs. The unbilled half of the year is real and usually invisible: the colleague you unblocked, the incident you handled at 11pm, the process everyone follows now because you wrote it down, the interview panels, the thing you learned. Add a line for it.

5. Note the praise while it exists

When someone thanks you in a message or a meeting, paste the sentence into the log with the date and who said it. This takes ten seconds and is the single highest-value entry type, because at review time it is the only evidence that is not you making a claim about yourself.

A template you can copy

Any tool works. Here is the shape:

Date	What I did	What changed	Evidence	Who it was for
14 Mar	Rewrote onboarding email sequence	Signup completion 61% → 74% over six weeks	Dashboard link	Growth team, new users
2 Apr	Ran the incident on the payment queue	Restored in 40 min, wrote the runbook	Incident doc, runbook	On-call team
19 Apr	Coached Sam through their first release	They shipped the next two unaided	—	Sam, my manager

Two columns people are tempted to add and should not: a rating of how well you did, and a category. Both add friction to the capture step, and neither helps at review time. Keep the entry cheap or you will stop making entries.

When the review actually arrives

Read the log start to finish before you write anything. Do not skim it, because the point is to override the recency-weighted highlight reel your memory is offering.

Then group into three or four themes rather than presenting a list of thirty entries. A list of thirty reads as busywork. Four themes with three concrete pieces of evidence under each reads as impact. The entries you cut are not wasted, they are what makes the themes credible.

Keep the raw log. It is the source for your next promotion case, your CV, and the interview question that begins “tell me about a time when”.

If your review is next week and you have none of this

Reconstruct it, and do not do it from memory. Work backwards month by month through the things that recorded your year for you: sent mail, your calendar, ticket or pull request history, documents you created, messages you sent in team channels. An hour of that will beat three hours of trying to remember, and it will surface the unremarkable weeks that memory has quietly deleted.

Then start the weekly habit, so that next year this is a five-minute job instead of an evening.

Where a tool helps, and where it does not

No tool fixes the capture step. If you will not spend five minutes on a Friday, software will not spend them for you, and most accomplishment trackers are a spreadsheet with a subscription.

What a system can do is stop the record from being purely a list of tasks. That is the part we work on at Vionter: building a picture of what you can actually do from evidence over time, so that “what did I do this year” and “what am I good at now” and “what should I learn next” are answered from the same accumulated record rather than reconstructed from scratch every time you need them. You can read what we build and how the rating works, and there is a related piece on why knowing something and being able to say it out loud are different skills, which is the same problem one step further down the line.

But start with the Friday five minutes. It is the part that does the work.