Kotter published his eight-step model in 1995. Lewin’s Unfreeze-Change-Refreeze framework is from the 1950s. ADKAR was formalised in the late nineties. These are the dominant frameworks still being applied to change in 2026.
In 1995, a large organisation might run one or two significant change initiatives per year. The workforce had time to stabilise between them. Leaders had space to work through the steps.
In 2026, your organisation is probably running eight to twelve simultaneously. AI integration is ongoing. The operating model is being rethought. Two restructures ago is still being digested while the current one is announced. And your managers are being asked to lead all of it while also doing their actual jobs.
The sequential eight-step framework was not designed for this. Applying it to this environment is like using a roadmap from 1995 to navigate a city that has been completely rebuilt since then. The streets look familiar. You are still going to get lost.
Traditional change management approaches tend to be too rigid and waterfall-like. Change planning is typically highly detailed, developed early, and expected to remain static throughout execution. This rigidity is problematic because change initiatives require adaptability. The sequential assumption, that each step can be completed before moving on to the next, does not hold in environments where initiatives encounter unexpected roadblocks and require course corrections.
But the structural flaw runs deeper than rigidity. Linear models assume a consistent state of readiness across the organisation, and a predictable pace of movement through defined phases. Neither of those assumptions is true.
Two people in the same team, receiving the same comms, going through the same training, can be in completely different readiness states at any given point in a rollout. One is Optimal. One is High Risk. The framework treats them identically. The comms plan treats them identically. And then one of them quietly reverts and no one knows why.
Readiness is not static. An assessment conducted months before go-live captures a moment in time, not a prediction of future readiness. The same change affects different parts of the organisation differently. Finance functions often adopt new processes faster than frontline operations.
It is what happens when you treat continuous change like episodic change.
Rigid change management frameworks are too often focused on checklists and Gantt charts rather than the human psychology that makes change stall or succeed. Your people are not resistant to change. They are exhausted by being asked to absorb continuous change through a process designed for a world where change had a beginning, a middle, and a definitive end.
The Unfreeze-Change-Refreeze model assumes the organisation can refreeze. It cannot. There is no steady state to return to. There is only the next initiative landing on top of the current one.
Not a new framework. A different approach to the whole problem.
Treat readiness as a live condition to monitor, not a box to tick at the start. Run diagnostics before launch to know your real baseline, not your assumed one. Run them mid-rollout to catch adoption stalling before it becomes failure. Run them after to verify what actually embedded and what quietly reverted under pressure.
Stop assuming that because the comms landed, the message was received. Stop assuming that because training was completed, capability exists. Stop assuming that because leadership is aligned at the top, the sponsorship chain is functioning all the way to the manager layer.
The organisations consistently landing change in 2026 are not the ones with the most sophisticated frameworks. They are the ones who know, in real time, where their people actually are. That is a measurement problem. It is solvable.
RhythmEngine replaces assumption with measurement. Run the diagnostic before, during, and after. Know where your organisation actually is, not where your plan assumed it would be. Book a 30-minute demo.
