Can’t Remember Your Work Achievements? Keep One Note a Week

You remember the busy weeks. But what actually happened?

Imagine opening a performance-review form.

The question looks simple: What did you accomplish?

You remember rushed mornings, long message threads, meetings, fixes, requests, and deadlines. Yet when you try to turn that into an example, “I worked hard” or “I handled many tasks” is about all you can produce.

So you start searching old emails and documents, hoping something will bring the year back.

The problem is not that every week contained a major achievement. It is that useful details can disappear once the work has moved on.

A small weekly note solves a more practical problem: instead of asking your future self to reconstruct the past, leave enough information to recognise what happened.

The note only needs four parts:

Problem: What needed attention?
My judgment or action: What did I decide, change, fix, suggest, or clarify?
Change: What was different afterward?
Evidence: Where could I check this later?

This is a practical template, not a universal performance-review standard. As one example of how accomplishment evidence can be structured, the U.S. Office of Personnel Management says applicant accomplishment records often describe the problem or situation, the specific actions taken, and the results or outcomes; it also notes that a person who can verify the statements is usually requested. (U.S. Office of Personnel Management)

The useful distinction is simple: record a piece of work as something that happened, not merely as time you spent.

Turn “I was busy” into something you can explain

Suppose you write this on Friday:

Worked on improving the team handoff process.

It sounds positive, but a month later it raises more questions than it answers.

What was wrong with the process? What did you actually do? Did anything change?

Compare it with this fictional note:

Problem: Open items in our weekly handoff sometimes had no clear next owner.
My judgment or action: I added “owner” and “next action” fields to the existing handoff note instead of creating another document.
Change: At the next handoff, each open item had a named owner and next action.
Evidence: Revised handoff document and version history.

Nothing here needs to sound heroic.

The useful part is the chain: there was a problem, you made a choice, something observable changed, and there is somewhere to check the details.

That makes the note easier to reuse later. You can shorten it for a CV, expand it in an interview, or use it to remind yourself what actually happened before a review.

What if nothing impressive happened this week?

This is where an achievement log can go wrong.

If every Friday has to produce a “win,” ordinary work can start getting inflated.

A small improvement becomes a “major process transformation.” A routine task becomes a “critical initiative.” The record sounds stronger, but it becomes less precise.

Some useful contributions are quiet.

Consider this fictional example:

Problem: A new team member had to ask which of several procedure pages was current.
My judgment or action: I put the current procedure link at the top of the shared page and marked the older copy as archived.
Change: The current procedure could then be found directly from the shared page.
Evidence: Page history and the updated handoff document.

No revenue number. No dramatic launch. No claim that productivity suddenly increased.

But the note captures a real contribution.

There is also an equally valid counterexample: perhaps this week you completed routine work and cannot point to a meaningful decision, improvement, problem solved, or change.

Then you do not need an achievement note for that week.

The goal is not to manufacture one achievement every seven days. The weekly check simply gives real contributions a chance to be recorded before their details disappear.

Separate the team’s result from your part in it

There is another common problem.

Sometimes the result is real, but it belongs to several people.

Suppose your team completed a release on schedule.

Writing this—

I delivered the release on time.

—can make a shared result sound like an individual one.

Instead, you can preserve both facts:

Team result: The release was completed on schedule.
My contribution: I found two items in the launch checklist with no clear owner, raised them during the final review, and updated the checklist after responsibilities were agreed.
Evidence: Final checklist and review notes.

Now you do not have to choose between taking all the credit and making yourself invisible.

The team result stays a team result. Your part is still concrete.

A current U.S. federal performance system uses a similar distinction in its own context: USA Performance describes an employee self-accomplishment narrative as a summary of key achievements that highlights results, contributions, and examples while giving the supervisor context and evidence for the performance rating. Your workplace may assess performance differently, so its own rules come first. (USA Performance)

The principle here is narrower: claim the part you can explain, and label shared outcomes as shared.

Leave enough evidence for your future self

The four parts of the note do different jobs.

The problem explains why the work mattered.

Your judgment or action identifies what was actually yours.

The change keeps the note from becoming a task list.

The evidence gives you somewhere to return when the details are no longer fresh.

“Evidence” does not mean copying confidential company material into a personal archive. Depending on your workplace rules, it may simply be a ticket number, document name, approved report, version history, feedback message, or internal dashboard you are allowed to reference.

Before this week ends, one note can be enough:

Problem:
My judgment or action:
Change:
Evidence:
If shared: Team result / my contribution:

You are not writing your CV every Friday.

You are leaving a small trail back to the work you actually did.

Months later, when someone asks, “What did you achieve?”, you will have something better than a vague memory of being busy: one concrete example you can explain, check, and honestly call your own.