Continuous feedback and the annual review aren't rivals — they do two different jobs, and dropping either one breaks the system. Continuous feedback is real-time steering: it corrects the work while it's still in flight and builds the trust that makes candor safe. The periodic review is the aggregation layer: it rolls signal up across projects and leads, calibrates it fairly, and drives the decisions people care about — growth, ratings, promotion, pay. Kill the reviews and feedback never becomes a fair decision; kill continuous feedback and the review becomes a once-a-year surprise built on recency and thin memory.
So the real question isn't "which one" — it's how to wire them together. The evidence cuts both ways: feedback given daily rather than annually makes people 3.6× more likely to be motivated to do outstanding work (Gallup, 2022; updated 2024), and firms that dropped ratings and reviews entirely saw performance fall about 10% and manager conversation quality drop 14% (CEB/Gartner, 2016). In a firm where people are staffed across engagements under rotating leads, you especially need both — per-engagement feedback captured while it's fresh, then rolled up and calibrated in a cycle.
What job does each one actually do?
They solve different problems: continuous feedback steers the work; the review cycle decides. Confusing the two is why most firms do one badly and skip the other.
Continuous feedback is the ongoing, forward-looking, low-stakes exchange that happens in 1:1s, engagement debriefs and milestone moments. Its job is to correct course while the work can still change, to build skill, and to make candor normal. It's frequent and small, and it works best kept out of the pay decision — feedback given far more often than once a year is what tracks with engagement (Gallup, 2022; updated 2024).
The review cycle is the periodic aggregation-and-decision layer. Its job is to gather signal from everyone who saw the work, calibrate it across leads so a rating means the same thing firm-wide, and produce the decisions people care about — grade, promotion, partner track, pay. This is exactly where a single lead's view is not enough: about 62% of rating variance is the idiosyncratic rater rather than the person being rated, and only ~21% is actual performance (Scullen, Mount & Goff, Journal of Applied Psychology, 2000). The cycle exists to correct for that; continuous feedback can't.
Why does annual-only feedback break down?
Because steering once a year isn't steering — it's a post-mortem. If the only structured feedback someone gets is the annual review, four things go wrong.
- Recency bias. A review written in November mostly remembers October. Eleven months of engagements collapse into whatever happened last — a known distortion in ratings, not a personal failing (DeNisi & Murphy, Journal of Applied Psychology, 2017).
- Thin memory across a year of projects. In a project-based firm, the person rating you may have staffed you for six weeks in Q1. Reconstructing that from memory in Q4 produces a vague, low-fidelity picture.
- Feedback arrives too late to act on. By review time the engagement is closed, the client has moved on, and the lesson is theoretical. Feedback only helps when there's still work to change.
- Surprise ratings. The single fastest way to destroy trust in a review is to raise something at the rating moment that was never raised during the work. A surprise at review time is a management failure, not a performance one.
None of this means the review is the problem. It means the review can't also be the steering wheel. That job belongs to feedback that happens continuously — which is why the fix for a bad annual review is rarely a better form, and usually more feedback before it.
Why does continuous-only feedback break down?
Because steering without a decision layer leaves you with lots of local signal and no fair way to act on it. "Just kill the annual review and give feedback all the time" sounds modern, but the firms that actually did it got a warning. When organisations removed ratings and the formal review, employee performance fell about 10% on average, and employees rated the quality of their performance conversations with managers 14% lower than at firms that kept ratings — managers also spent fewer hours on informal performance conversations, not more (CEB/Gartner, 2016).
Why does it fail? Continuous feedback alone has no aggregation and no calibration. Each lead's view stays siloed, and there's no mechanism to make one lead's "great" mean the same as another's. With no shared bar, promotion, partner-track and pay decisions get made on whoever advocates loudest — which is precisely the idiosyncratic-rater problem the cycle is built to contain (Scullen, Mount & Goff, Journal of Applied Psychology, 2000). Feedback also isn't automatically good: in a meta-analysis of 607 studies it raised performance only modestly on average (d ≈ .41) and over a third of interventions actually made performance worse (Kluger & DeNisi, Psychological Bulletin, 1996). Without a system around it, a stream of feedback doesn't add up to a fair outcome — it just adds up.
How do the two fit together without surprises?
Continuous feedback feeds the cycle, so the review contains nothing new — it just aggregates and calibrates what people already heard. That handoff is the whole design.
Picture two layers. The steering layer runs all year: per-engagement notes, 1:1 feedback, debriefs — small, specific, and mostly developmental. The deciding layer runs periodically: it pulls those documented signals together, calibrates across leads, and sets the rating and growth plan. Because the review is built from feedback the person already received, there are no surprises — the rating is a summary, not a reveal.
- Keep a shared record that rolls up. Feedback that lives only in someone's head can't be aggregated. A light, per-engagement note — captured when the work is fresh — is what lets the cycle assemble a fair, multi-lead picture instead of one manager's recency-weighted guess (DeNisi & Murphy, Journal of Applied Psychology, 2017).
- Decouple developmental feedback from the rating moment. Run growth feedback continuously and keep the pay/promotion decision to the calibrated cycle. This is why removing the cycle backfired and why cramming everything into the annual verdict backfires: honesty stays cheap only when today's candid note isn't tomorrow's comp risk (CEB/Gartner, 2016; Buckingham & Goodall, "The Feedback Fallacy," Harvard Business Review, 2019).
Two design rules make the handoff work: keep a shared record that rolls up, and decouple developmental feedback from the rating. Done right, this is also what leading practice has converged on — ongoing performance conversations running alongside, not instead of, a formal cycle (CIPD, Performance Management).
How do you combine them in a billable, multi-lead firm?
This is where "you need both" stops being theory. In an agency or boutique, people are staffed across several engagements a year under different leads — so both single-layer models fail harder here than anywhere. Annual-only asks one manager to rate work they barely saw; continuous-only leaves each lead's feedback siloed, with no calibration for promotion or the partner track. Combining them is what makes ratings fair across projects. Six moves, built to cost minutes, not a program:
- Capture feedback per engagement, while memory is fresh. When a consultant rolls off, the lead who staffed them leaves a short, specific note then — not eleven months later. This is the single highest-leverage habit; it's what feeds fair calibration.
- Attach feedback to work already happening. Put a standing five-minute feedback slot in 1:1s and make a two-way retro the default close of every engagement phase. No new meetings — feedback rides the rhythm you already have, so utilization pressure can't erase it.
- Aggregate and calibrate in the cycle. The periodic review pulls the per-engagement notes together and calibrates across leads, so "strong" means the same thing whoever staffed you — the direct fix for the idiosyncratic-rater effect (Scullen, Mount & Goff, Journal of Applied Psychology, 2000).
- Keep the developmental track separate from the rating. Continuous feedback is for growth; the calibrated cycle is for the grade and pay. Mixing them makes candor expensive and dries up the feedback (CEB/Gartner, 2016).
- Make client feedback a team ritual. Client-facing work throws off tough external feedback; debrief it together, separate signal from sting, and feed the durable part into both layers.
- Have leads and partners model it. A partner who asks their team for feedback on their own running of an engagement — and acts on it — makes candor safe faster than any policy. Frequent, in-the-moment, strengths-anchored exchange beats saved-up critique (Buckingham & Goodall, "The Feedback Fallacy," Harvard Business Review, 2019).
A quick both/and self-check
Score your firm: one point per "yes". Six or more and your two layers are wired together; four or fewer and you're running one layer and calling it a system.
- Feedback happens in 1:1s and engagement debriefs, not only at review time.
- Per-engagement feedback is captured while it's fresh, not reconstructed at year-end.
- The review aggregates documented feedback rather than one lead's memory.
- Ratings are calibrated across leads, so "strong" means the same firm-wide.
- Nothing raised at the review is a surprise to the person hearing it.
- Developmental feedback is kept separate from the pay/promotion decision.
- You haven't "just dropped" the review — decisions still trace to a calibrated cycle.
- Client feedback is debriefed as a team and fed into both layers.
Scored four or fewer? Book a call and we'll help you wire the two layers together.
FAQ
Do you really need both continuous feedback and an annual review?
Yes — they do different jobs. Continuous feedback steers the work in real time and builds the trust that makes candor safe; the periodic review aggregates signal across leads, calibrates it, and drives ratings, promotion and pay. Drop the reviews and feedback never becomes a fair decision; drop continuous feedback and the review becomes a recency-driven surprise. The evidence points both ways: daily feedback makes people 3.6× more likely to be motivated to do outstanding work (Gallup, 2022; updated 2024), but firms that removed ratings entirely saw performance fall ~10% (CEB/Gartner, 2016).
Isn't the annual review dead?
No — the annual-only model is what's broken, not the review itself. When firms removed ratings and the formal cycle, performance dropped about 10% and manager conversation quality fell 14% (CEB/Gartner, 2016). What leading practice actually did was keep a calibrated cycle and add ongoing performance conversations alongside it (CIPD, Performance Management). Replace the only, not the review.
How do we stop reviews from being full of surprises?
Feed the review from continuous feedback. If someone has heard specific, documented feedback throughout the year, the review is a summary, not a reveal. The fastest way to destroy trust in a rating is to raise something at review time that was never raised during the work — a management failure, not a performance one (DeNisi & Murphy, Journal of Applied Psychology, 2017).
How does this work when people are staffed across many leads?
Capture short, specific feedback per engagement while it's fresh, then let the periodic cycle roll those notes up and calibrate across leads. That's what makes a rating fair when no single manager saw all the work — and it's the direct fix for the idiosyncratic-rater effect, where about 62% of rating variance is the rater rather than the person (Scullen, Mount & Goff, Journal of Applied Psychology, 2000).
Should developmental feedback affect someone's rating?
Keep them on separate tracks. Run growth feedback continuously and keep the pay/promotion decision to the calibrated cycle. Mixing them makes honesty costly — today's candid note becomes tomorrow's comp risk — and dries up the feedback you need (Buckingham & Goodall, "The Feedback Fallacy," Harvard Business Review, 2019; CEB/Gartner, 2016).
