What to Say in a Performance Review When You Can't Remember What You Did

If you can't remember what you did all year, rebuild it from records: scroll back through your calendar, messages, sent email, project tracker, code history and documents, list everything, rank it by impact, and rewrite each item as an outcome. If the list is thin, discuss that honestly.

  1. Work from records, not memory.
  2. Scroll back month by month through each tool.
  3. Rank the list by impact, not date.
  4. Rewrite each item as an outcome.
  5. If the year really was thin, say so and discuss why.

Updated October 9, 2026 · By the DeftBrain team

Reconstructing a year of work for a performance review is easier from records than from memory, because recent weeks tend to crowd out earlier months. Calendars, chat threads, sent email, project trackers, code history and shared documents together hold a dated record of meetings attended, decisions made and work shipped. Scrolling back through each, collecting everything, then ranking by impact and rewriting items as outcomes produces a fuller and more accurate self-review.

The self-review needs eight bullets and you can confidently fill three. You worked hard all year, but memory returns the last two months in detail and very little before that.

How to do it
1

How do you remember what you did for your performance review?

A common mistake at this stage is sitting in front of a blank document trying to summon memories. Memory is unreliable for routine work — the kind that fills most of the year — and reliable mostly for crises and recent events. The fix is to stop relying on memory entirely. Open the systems you used over the past year: calendar, Slack, email, code repository, project tracker, design tool, document folder. Each of these is a record of what you actually spent time on, dated and searchable. Working from artifacts, you'll find weeks you'd completely forgotten and projects you'd half-erased. The unlock is treating the year as a research problem with sources, not as a memory test.

What to say

"Open six tabs: Calendar, Slack search of your name, Sent email, Git commits, Project tracker (Jira/Linear/Asana), Document folder. Scroll back to January. For each, capture every substantial thing into one running list — no filtering yet."

This is the artifact sweep, which is the move that recovers most of the lost year in about forty minutes. The instinct is to filter as you go ('that's not bullet-worthy,' 'that's too small') — resist it. Capture everything; filter later. You'll find you forgot about projects that ran for a month, meetings that led to decisions, and contributions to launches you only remembered as 'something the team did.' The unfiltered list always has more material than the memory-only list, and the gap is where most of the year's quiet work lives.

2

Which tools help you reconstruct a year of work?

Each tool tells a different part of the story. Calendar reveals what meetings you attended — which projects pulled your time, who you collaborated with, where you led versus participated. Slack shows the conversations you drove and the decisions you were part of. Email captures the cross-functional work and external touchpoints. Code commits and project tickets show what you actually shipped. Document folders surface what you wrote, designed, or analyzed. The technique: scroll back month by month in each tool and capture anything that strikes you as substantial. Don't filter at this stage; just collect. A search for your name in Slack from January will surface things you've forgotten you led. A skim of your calendar will surface meetings that turned into decisions. The list often grows from a half-remembered three to a documented twenty in under an hour.

3

How do you choose what to include in a performance review?

Once you have the raw artifact-based list, sort it by impact rather than chronology. The biggest thing you shipped, drove, or contributed to goes at the top — even if it happened in February and you'd forgotten about it. The smallest goes at the bottom. This sorting matters because performance review bullets aren't a chronicle; they're an argument for your value, and the argument lands when the strongest items are visible first. Build the list backward from biggest to smallest in passes: pass one, capture every candidate; pass two, add detail (impact, scope, who was affected); pass three, group related items into themes. By the end of pass three you have something like fifteen candidate bullets, ranked, with enough material that picking the best eight is a curation problem rather than a creation one.

4

How do you turn tasks into accomplishments for a review?

Once you have the list of what you did, translate each item from activity to outcome. 'Worked on the migration' becomes 'Led migration that retired three legacy systems and saved $X annually.' 'Helped onboard new hires' becomes 'Built the onboarding doc the last six hires used, cut ramp time from eight weeks to four.' For each item, ask: what changed in the world because of this? Who was affected? What got faster, cheaper, more reliable, or unblocked? If you can't answer those questions for an item, either the work was less impactful than it felt (which is real signal) or you have impact data you haven't surfaced yet (which is recoverable). The translation is the work that turns 'I did things this year' into a bullet that holds up in calibration.

5

What if you really didn't accomplish much this year?

There's a category of performance review fog that isn't just memory — it's accurate. Sometimes the year was, in fact, thin: lots of busy time, few high-impact outcomes, plenty of meetings that didn't go anywhere. The artifact sweep returns a list, but the list is mostly small or routine items that don't add up to a strong case. This is a real signal worth taking seriously. The right response isn't to inflate the list; it's to engage with what the year actually was. Maybe the role had less scope than it should have. Maybe organizational priorities shifted in ways that left your function under-resourced. Maybe you were learning a new domain and the impact will land next year. The honest performance review acknowledges what's actually there — and that conversation often opens the door to the real one about scope, support, or trajectory. Faking a strong year on paper produces a calibration outcome that surprises nobody and resolves nothing. The harder conversation produces actual change.

Try it now — free

Stop trying to remember — use the Memory Jogger

Brag Sheet Builder's Memory Jogger button asks role-specific prompting questions across six categories — projects led, problems solved, people developed, processes improved, customers served, decisions driven — surfacing accomplishments you'd forgotten. Combine with the Accomplishment Journal for next year and you'll never have to reconstruct twelve months from artifacts again.

Memory Jogger — role-specific prompting questions across 6 categories Accomplishment Journal — log wins weekly, import them at review time Before/After bullets — turn vague memories into outcome statements Metrics Excavator — replace estimates with real numbers Strength Radar — scores your sheet against role expectations, finds gaps
Open Brag Sheet Builder → No account required to get started.

Found this useful? Link to it.

https://deftbrain.com/guides/career/what-to-say-in-a-performance-review-when-you-cant-remember

Free to read, no account, no paywall — link away.

Related situations

💡 Missing something?

Didn’t find what you need? Suggest a tool. We read every suggestion, and the best become new tools.

📮 Newsletter

One useful tool a month — the one worth knowing about before life demands it.