Ask any manager how long their last performance review actually took, and the honest answer is somewhere between three and five hours — and most of that time isn't spent writing. It's spent digging. Scrolling back through six-month-old Slack threads, hunting for the email where a client praised a project, trying to remember what actually happened in March.
Roughly 85% of the time a manager spends on a review goes to that research, not the writing itself. The annual review cycle isn't broken because managers are bad at feedback. It's broken because it asks one person to reconstruct twelve months from memory, once a year, under deadline pressure.
Where the Time Actually Goes
If you sat next to a manager writing a review, you'd see the pattern immediately: open Slack, search a name, scroll, open email, search again, check old calendar invites for context on a project that shipped in Q2. The writing itself — the part that actually helps the employee — gets whatever time is left over, usually not much.
That research time is a direct cost of the annual model. Because feedback was never captured when it happened, someone has to go excavate it months later, and excavation is slow.
The Recency Bias Problem Isn't an Accident
Ask a manager in December what an employee's best month was, and they'll usually describe something from October or November. Not because Q4 was necessarily the strongest stretch of the year — because it's the most recent, and recent is what's easiest to remember.
A once-a-year review, written from memory, structurally favors whatever happened in the six weeks before the deadline. That's not a bias some managers have and others don't. It's what happens to anyone asked to summarize a year using only what they can recall in the moment.
What "Broken" Actually Costs You
The direct cost is the hours — three to five hours per review, most of it research, multiplied across every manager and every report in the company, every cycle. The indirect cost is worse: reviews built on partial memory produce vague, generalized feedback ("consistently meets expectations, strong team player") because specifics are exactly what gets lost first when you're working from recall instead of a record.
Vague reviews don't help anyone improve, and they don't hold up well when an employee asks why a rating landed where it did.
What to Do Instead
The fix isn't a better annual review template. It's not asking managers to remember more, or write faster. It's removing the research step entirely by capturing feedback continuously, as it happens, instead of reconstructing it after the fact.
When feedback lives in a running record — peer comments, 1:1 notes, project retros, recognition moments, all logged in the moment rather than months later — review time shifts from excavation to synthesis. The manager isn't remembering a year. They're reviewing evidence that was already there.
This is also what actually neutralizes recency bias: if the record covers all twelve months equally, the review isn't structurally weighted toward whatever happened most recently. We go deeper on the mechanics of continuous collection in continuous performance management software: what it actually replaces, and on making that collection frictionless by meeting people in tools they already use in how to run performance reviews inside Slack.
If you want a closer look at how recency bias specifically distorts ratings, see overcoming biases in performance reviews.
Making the Case Internally
If you're building the case to move off annual reviews, lead with the hours, not the philosophy. Three to five hours per review, mostly spent on research that a continuous record would eliminate, is a concrete number a CFO or a skeptical exec can weigh against the cost of switching. "Annual reviews feel outdated" doesn't move a budget conversation. "Managers are spending 85% of review time hunting for evidence that should already be on file" does.
If you're ready to see what a continuous model looks like in practice, schedule a demo with WorkStory.
FAQ
Why do annual performance reviews take so long to write?
Most of the time isn't spent writing — it's spent researching. Managers have to reconstruct a year of performance from memory, Slack history, and old emails, and that excavation typically eats up around 85% of the total time spent on a review.
What is recency bias in performance reviews, and why does the annual cycle make it worse?
Recency bias is the tendency to weight recent events more heavily than earlier ones. An annual review written from memory naturally overweights the last month or two before the deadline, because that's what's easiest to recall — not because it was the strongest stretch of the year.
What's the alternative to annual performance reviews?
Continuous performance tracking — capturing feedback as it happens throughout the year instead of reconstructing it once at review time. It removes the research burden and produces a more balanced, evidence-based review.
