← Blog  ·  Product use cases

The performance review you could write in ten minutes

Most self-reviews take hours because they start from a blank page. They don't have to.

Published September 24, 2026 · NextNorth Team · 4 min read

TL;DR

  • Self-reviews take hours mostly because of the format they start in: a blank text box and a vague memory of “what did I do this year.”
  • If you'd been jotting down wins, decisions, and outcomes as they happened, the review becomes an editing task — picking the best entries and trimming them to fit — instead of a research project.
  • Most self-review prompts map directly onto what a running work log already captures: impact, challenges, growth, what you'd do differently.
  • The hard part of a self-review was never the writing. It was remembering, and remembering under deadline pressure is exactly when people write something too vague or something quietly exaggerated.
  • A ten-minute review isn't about writing faster. It's about not having to do the remembering and the writing at the same time.

Where the hours actually go

Not typing — remembering. Most of a self-review session is spent trying to reconstruct six or twelve months, which is a research task disguised as a writing task.

What changes with a running log

If wins, decisions, and outcomes were captured close to when they happened, review season becomes selection and editing: pick the best five entries, trim them to the prompt, done. The research is already finished.

Mapping prompts to entries

Most review forms ask some version of: what did you accomplish, what was hard, what did you learn, what's next. Those map almost directly onto Situation/Task/Action/Result entries captured over the year — the review just needs the right few pulled out and reworded for the audience.

Why deadline pressure makes reviews worse, not just slower

Under deadline pressure, tired memory does one of two things: understates real work because the details are gone, or overstates it because a vague version is easier to write than a precise one. Neither is what you want in a document that affects your rating or your case for promotion.

Copy this prompt

  • “Look back through the work log I've shared and pull out the strongest examples from this review period for: what I accomplished, a challenge I worked through, something I learned, and what I'd focus on next.”
  • “For each one, keep it specific and grounded in what's actually in the log — don't round anything up or add impact I didn't record.”
  • “Give me the raw list first. I'll pick the strongest ones and write the final review myself.”

Frequently asked questions

What if I haven't been logging anything and review season is next week?

Start now with what's recoverable — recent chats, tickets, calendar events, anything with a date attached — and treat this review as the reason to start the habit going forward.

How many entries do I actually need for a good review?

Fewer than you'd think — four or five well-documented, specific moments usually outweigh a long list of vague ones.

Does this work for peer or upward feedback too, not just self-reviews?

Yes — the same running record of specific moments is just as useful when you're asked to write feedback about someone else's work, or give feedback upward.

Isn't this basically just a brag doc?

Close — a brag doc is the running record; a self-review is one of the things you eventually pull from it. See our piece on building a brag doc with AI for the full version.

Related reading: How to build a brag doc with AI.

Try bulk import →