360 feedback is eating your calendar. Here's how to run it in less time.
Read more 360 Reviews
The continuous-feedback-versus-annual-review debate is mostly a marketing fight. One side sells software that runs weekly check-ins, the other defends a ritual everybody privately dreads, and the actual question gets lost in the noise. Here is the version that matters: continuous feedback and annual reviews are not two options you pick between. They are two rhythms, and the thing that decides whether either one works is not the format at all. It is rhythm, how close the feedback lands to the moment and how often it happens.
I build a feedback tool, so treat my view accordingly. But I am not here to sell you “continuous.” I am here to argue that the whole binary is a distraction, and that you can get feedback badly wrong with either format and quietly right with a mix of both.
Key Takeaways
- Continuous vs annual is a false binary. Both are formats; the variable that actually matters is rhythm: frequency plus proximity to the event.
- A continuous cadence is for development and course-correction in the moment. Its failure mode is constant low-grade check-ins nobody acts on. Continuous done badly is worse than annual done well.
- A periodic structured checkpoint does a job continuous cannot: the deliberate, multi-source, written-down assessment. Replace the annual ritual, keep a periodic beat.
- “Just switch to continuous” usually fails, because swapping the format without fixing rhythm changes nothing. Teams that drop the annual review and add nothing structured often get less feedback.
- Stop shopping for a format. Design a rhythm: a light continuous habit plus a structured periodic round, both decoupled from pay.
Strip away the vendor framing and feedback has two properties that determine whether it is useful: how close it lands to the thing it is about, and how often it happens. Call that rhythm.
Proximity is the one people underrate. Feedback given six months after the moment is generic by default, because the specific example has already faded from memory, and a general impression is all anyone has left to offer. That is true whether the format is a once-a-year review or a quarterly one. The format is not the problem; the delay is. It is the same reason feedback so often comes back vague: distance from the event flattens the specifics before anyone writes them down.
So “continuous vs annual” is really a proxy argument for rhythm. Continuous formats tend to have better proximity, that is their genuine advantage. But a poorly run continuous habit can have terrible rhythm too, and a well-timed periodic round can have excellent proximity. The label tells you almost nothing. The rhythm tells you everything.
A continuous cadence, a quick word after a project, a standing prompt in a one-on-one, a note while the work is fresh, is built for one job: development and course-correction in the moment. It keeps small things small. It stops a year of unspoken observations from piling up into one high-stakes reckoning. When it works, feedback stops being an event people brace for and becomes a normal part of how the team operates.
That is the version vendors sell. Here is the part they leave out: continuous feedback done badly is worse than annual feedback done well.
Imagine a team that decides to “go continuous” and, in practice, just adds a recurring feedback item to every weekly one-on-one. Nobody has anything specific to say most weeks, so the slot fills with “yeah, going well, keep it up.” The ritual generates volume and no signal. Now feedback is both constant and meaningless, which trains everyone to tune it out. Frequency without proximity or substance is not a rhythm. It is noise with a calendar invite.
The honest case for keeping a periodic, structured moment is that it does something a continuous drip cannot: the deliberate, considered, multi-source, written-down assessment. Once or twice a year, you stop and gather a fuller picture from the people who actually work with someone, on purpose, in a form you can hold onto and act on.
A structured 360 round is a good fit for that periodic beat. It is not the daily habit; it is the checkpoint, run as a contained round a few times a year rather than a rolling stream. Note that this is a different axis from the one people usually argue about. Whether to run a 360 or a manager-led performance review is a question about the source and purpose of the feedback, multi-source development versus single-source evaluation, and I have worked through that separate decision elsewhere. Cadence is its own axis. You can run either instrument on a continuous or a periodic rhythm; the two choices are independent.
Here is where the false binary does real damage. A team reads that annual reviews are broken, concludes the fix is to abolish them, and switches to “continuous” by deleting the annual review and adding nothing structured in its place. Six months later they have less useful feedback than before, because the one deliberate moment is gone and the continuous habit never actually formed.
The annual review genuinely is badly designed for the job it claims to do, that argument stands, and I will not repeat it here. But “the annual review is broken” does not imply “continuous is the answer.” It implies “fix the rhythm.” Swapping one format for another without changing proximity, frequency, or the safety to be specific changes nothing. You can abolish the ritual and still have terrible feedback. The format was never the lever.
And rhythm is downstream of culture, not software. A cadence only produces honest feedback if people feel safe being specific, which is slow, relational work that no tool and no schedule creates on its own. That part, building the culture underneath the rhythm, is the real prerequisite, and it is worth reading before you touch the cadence at all.
So stop choosing a format and design a rhythm instead. For most teams under a couple of hundred people, the shape that works looks like this: a light continuous habit for the day-to-day, plus a structured periodic beat for the considered assessment, with both kept away from pay decisions so honesty survives.
The continuous habit is mostly a management discipline: feedback while the example is fresh, in one-on-ones and after projects, small and low-stakes. The periodic beat is where a little structure earns its place. Running a full multi-source round a couple of times a year is tedious to do by hand, which is exactly why teams default to the dreaded annual event instead. A structured feedback round that handles the logistics, so the periodic beat happens on schedule without you chasing it, is the part where tooling genuinely helps. The habit stays human; the checkpoint stays on the calendar.
Picture a roughly 50-person company that gets this right. Managers give quick, specific feedback in their regular one-on-ones, close to the work. Twice a year, the company runs a structured round for a fuller multi-source picture, decoupled from compensation, aimed purely at development. Neither rhythm is doing the other’s job, and neither one is a once-a-year ambush. That is a feedback system. It is not “continuous” or “annual.” It is both, on purpose.
The continuous-versus-annual question feels like a strategic decision, and it mostly is not. It is a distraction from the only thing that reliably makes feedback useful: rhythm. Feedback close to the event, often enough to stay fresh, safe enough to be specific, and decoupled from pay so people can be honest. Get that right and the format sorts itself out. Get it wrong and no format will save you.
So do not pick a side in a debate the vendors invented. Design a rhythm you can actually sustain, a light continuous habit plus a deliberate periodic beat, and let the label be whatever it turns out to be. If you want the periodic part to run without becoming a second job, you can set up a structured round in Lynxify.me. But the rhythm matters far more than the tool, and far more than which format you tell people you use.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
