01 June 2026

There’s a familiar reflex in most organisations the week before performance reviews open. Calendars fill with one-on-ones. Managers dig through six months of half-remembered work. Employees rewrite their own narratives. A neat document gets filed, ratings get calibrated, and then the system goes quiet for another half-year. In 2026, that rhythm finally looks like what it is: a beautifully formatted summary of feedback that never actually arrived in time to change anything.

The skills-based shift has made this gap impossible to ignore. If capability is supposed to be moving every week — through practice, application, and small course corrections — then the once-a-year review is an X-ray of a body that’s already healed or already broken. The teams making real progress on skills aren’t replacing the review with a better template. They’re replacing it with a continuous feedback rhythm that runs alongside the work, and treating the formal review as a periodic stocktake of a system that’s already doing its job.

Why the Annual Review Stopped Working

The annual review wasn’t designed to develop capability — it was designed to rationalise pay, manage risk, and document performance for the record. It does those things reasonably well. What it has never done well is help someone get better at the work in front of them. By the time the feedback lands, the project is closed, the team has moved on, and the moment when the lesson could have changed behaviour has long passed.

In a skills-based model that gap compounds. The taxonomy is moving in week-long increments. Practice cycles are running across days, not quarters. The library is being refreshed against real capability signals. Bolting a six-monthly conversation onto a weekly system was always going to feel slow, and in 2026 it finally feels obsolete. The question isn’t whether to keep the review — most organisations still need a formal cadence for compensation and progression. The question is what runs in the long stretches between them.

What “Continuous Feedback” Actually Means in Practice

Continuous feedback is one of those phrases that has been used to mean almost anything — from a Slack thumbs-up to a quarterly check-in re-labelled as “always-on”. The version that actually moves capability is narrower and more disciplined than that. It’s a short, specific signal — tied to a named skill, attached to a piece of real work, and delivered close enough to the moment for the person to act on it. It doesn’t need to be long, and it doesn’t need to be formal. It needs to be timely, concrete, and traceable.

The teams getting this right have stopped trying to invent a separate feedback ritual and started threading it into the work itself. A reviewer marks up a draft against the same rubric the course used. A manager spends three minutes after a client call naming what was strong and what to tighten next time. A peer leaves a structured comment on a deliverable using a shared framework. None of those moments looks like a “feedback meeting”, and that’s precisely why they work.

Feedback as a Skills Signal, Not a Performance Verdict

One of the quieter changes in 2026 is that feedback has stopped being framed primarily as a judgement and started being framed as a signal. The shift sounds semantic; it isn’t. A judgement is a closed loop — the person was good or wasn’t, the rating goes into the record, the conversation ends. A signal is an input — it tells the skills profile something specific, it nudges the next development action, and it accumulates into a much more honest picture of capability than any single review could produce.

That reframing changes what gets captured and how. Instead of one composite rating per person per cycle, the system captures many small signals against named skills: a manager’s rubric score on a deliverable, a peer’s qualitative note on a collaboration moment, the outcome of a deliberate practice cycle, an evaluator’s structured response inside evaluations and feedback. Each signal on its own is small. In aggregate they’re the most reliable read of capability the organisation has ever had.

The Manager’s Job in a Continuous Feedback Rhythm

The instinct, when feedback frequency goes up, is to assume managers need to do more. The honest answer is that they need to do less of one thing and more of another. Fewer end-of-cycle essays. More short-form, in-the-moment notes attached to real work. The managers who land this well aren’t suddenly trained coaches — they’re operating a much smaller loop, repeatedly: name what good looks like before the task, name what was strong and what to tighten after it, and let the system carry the rest.

Where the formal cadence still matters — in performance and development reviews and progression decisions — the manager’s job is no longer to manufacture feedback in the room. It’s to read the signals that have already accumulated, surface the patterns the day-to-day notes can’t, and decide what changes in the next development cycle. The review stops being where feedback happens and starts being where feedback is interpreted.

Closing the Loop: From Feedback to Capability

The reason continuous feedback finally pays back in a skills-based world is that the loop actually closes. A signal lands against a named skill. The skills profile shifts. The next piece of content, the next practice opportunity, the next stretch assignment is chosen against that updated picture rather than the stale one. Analytics and reporting stop telling leaders what was delivered and start telling them what’s moving — which skills are accelerating, which are stuck, which managers are running the loop and which are not.

There’s nothing flashy about any of this. No new platform category. No keynote-friendly rebrand of the performance review. It’s a quieter discipline: shorter feedback, more often, attached to specific skills, captured in a way the system can read. Done consistently, it does what every previous attempt to fix the annual review never quite managed — it turns feedback from a once-a-year ritual into the operating rhythm of how capability gets built. In 2026, that’s the half of the conversation worth investing in.