Why small companies should skip annual performance reviews

A twelve-person company spends the last two weeks of January doing performance reviews because that's what companies do. The founder writes twelve assessments, each manager fills in a form built for a 5,000-person org, everyone rates everyone on a 1-to-5 scale nobody believes, and the whole thing produces exactly one outcome: a slightly awkward meeting where each person hears a summary of feedback they could have used nine months earlier. Then everyone goes back to work, relieved it's over, and nothing changes until next January.

This happens because annual reviews feel like a sign of being a real, grown-up company. They're not. They're a tool built to solve problems that large organizations have and small ones mostly don't — and at small scale the tool doesn't just fail to help, it actively crowds out the feedback rhythm that would. The case for skipping the annual review at a small company isn't anti-feedback. It's the opposite: the annual review is what's standing between your team and feedback that actually lands.

What the annual review was actually built to do

To see why it doesn't fit, you have to see what it was for. The annual performance review evolved inside big organizations to do four specific jobs, and it's worth being precise about each.

Legal defense for termination. In a large company, firing someone without a paper trail is a lawsuit risk. The annual review creates a documented record of underperformance that protects the company. This is a real job — for a company with a legal department and hundreds of people it can't track individually.

Calibration across managers. When forty managers each rate their reports, the company needs a way to make a "4 out of 5" mean the same thing in engineering as in sales. Calibration meetings exist to normalize ratings across people who've never met. Again — a real problem, at scale.

Compensation distribution. Big companies tie raises and bonuses to review scores so that a finite raise budget gets distributed defensibly across thousands of people. The review becomes the input to a spreadsheet.

Individual development. The one job everybody thinks is the point — helping a person get better — is, in practice, the fourth priority, and the one the format serves worst.

Now look at a ten-to-fifty-person company and ask which of those four you actually have. The legal-defense need is minimal — you know everyone, terminations are rare and rarely surprising. Cross-manager calibration is close to meaningless when there are three managers who talk every day. Compensation at small scale is usually set by judgment and market, not by a score. What you're left with is the fourth job — development — bolted onto a machine built for the other three. (We make the longer version of this argument in the pillar piece on alternatives to performance reviews, which lays out the four-jobs framework in full.)

Why the bolted-on development job fails

Even granting that you keep the annual review only for development, the format sabotages that goal in three predictable ways.

The feedback is stale before it's delivered. A thing your colleague did badly in March, surfaced in January, is no longer actionable — it's archaeology. The person can't picture the moment, can't reconstruct what they were thinking, and can only nod at a generalization. Useful behavioral feedback has a half-life measured in days, not quarters; by the time the annual review compresses a year into one sitting, every specific has decayed into a vague impression.

Recency bias eats the year. Because nobody can actually remember twelve months of behavior, the review disproportionately reflects the last six weeks. The strong Q1 is forgotten; the rough December dominates. The review purports to assess a year and actually assesses a month, which means it's both unfair and uninformative.

The stakes poison the conversation. When the same meeting decides your raise and is supposed to help you grow, the development half loses every time. Nobody explores their weaknesses honestly in a conversation that sets their salary. Samuel Culbert, the UCLA management professor whose case against the performance review has been making this argument for over a decade, puts it bluntly: bundling evaluation and development into one annual event produces a conversation that does neither well, and mostly teaches people to manage the impression rather than the work.

The result at small scale is the worst of both worlds — you pay the full cost of the ritual (time, anxiety, paperwork) and get almost none of the development it promises.

"But we'll lose the discipline"

The honest objection to skipping the annual review isn't that the review works. It's: if we drop the calendar event, won't feedback just stop happening? For a lot of teams, the annual review is the only thing forcing the conversation at all, and removing it risks replacing a flawed rhythm with no rhythm.

This is a real risk, and it's why "skip the annual review" is only half the advice. The other half is non-negotiable: you replace it with something more frequent and lighter, or you don't skip it. The goal is to swap one heavy, stale, high-stakes event for many small, fresh, low-stakes ones — not to swap it for silence. A team that drops the annual review and installs nothing in its place will, within a year, have worse feedback than when it started. The discipline objection is correct; it just argues for a different structure, not for keeping the broken one.

What to run instead

The replacement isn't a smaller annual review. It's a different shape entirely — feedback anchored to the rhythm of the work rather than the rhythm of the calendar. Three pieces do most of the job.

A light recurring check, monthly or quarterly. Not a form — a short, structured conversation that asks the few questions that matter and surfaces issues while they're still small enough to fix in a sentence. The whole point is frequency: a problem caught in month two is a quick correction; the same problem caught in month eleven is a "development area." Picture an engineer who's quietly become a bottleneck because every change routes through them. Caught in month two, it's a ten-minute conversation about delegating two specific responsibilities. Left until the annual review, it's eleven months of a frustrated team, a defensive engineer, and a "needs to develop delegation skills" line that lands as an accusation instead of a nudge. Same issue, two completely different costs — and the only variable is when it got named. We've written separately about the continuous-vs-annual choice and why the third option — rhythm-based, not continuous-noise and not annual-silence — is what actually fits a small team.

Feedback tied to work cycles, not the calendar. The natural unit of feedback at a small company isn't the year — it's the project. When something ships, the observations are fresh, the outcome is visible, and everyone's already reflecting. Catching feedback at those moments is both easier and more accurate than reconstructing it in January. This is the project-based feedback angle: review the work while it's still warm.

A structured quarterly rhythm for the bigger picture. Some reflection genuinely benefits from stepping back — patterns across a quarter, trajectory, the slow-moving stuff a single project doesn't reveal. That deserves a real structure, just not an annual one. A quarterly check-in with a tight agenda gives you the lookback without the staleness, four times the resolution, and a quarter of the dread.

Notice what this does to the four original jobs. Compensation gets decoupled from development and handled on its own honest footing (market, judgment, a separate conversation). Development gets the frequency it always needed. And the legal/calibration jobs you didn't really have stop costing you anything.

Keep the one part that was working

Skipping the annual review doesn't mean throwing away the one genuinely useful instinct buried inside it: the idea that people deserve a periodic, structured look at how they're actually doing — including, crucially, the manager. The annual review's deepest irony is that it almost always points downward. The founder reviews the team; nobody reviews the founder. At a small company, where the leader's blind spots shape everything, that's exactly backwards.

The version worth keeping is the one you run on yourself. Before you ask your team to reflect, reflect first — answer a focused set of questions about how you're leading, then ask the people around you the same questions and read the gap between your view and theirs. That's the rhythm Mirorly is built for: our quarterly check-in template gives you a tight, repeatable structure you can run every ninety days — on yourself first, then with your team — so the lookback stays fresh, honest, and pointed in the direction that actually moves a small company. Not a once-a-year verdict. A quarterly habit that catches things while they're still small.

The one-line summary

The annual review solves four problems your ten-person team doesn't have and fails at the one it does — so skip it, but only if you replace it with a lighter, more frequent rhythm anchored to the work, starting with the review you run on yourself.