The Continuous Change Cycle

A continuous change cycle treats change as a loop rather than a project with a start and an end. The organization makes a small change, learns from the result, adjusts, and goes round again. Over many cycles, the small changes add up to a large one.

Karl Weick and Robert Quinn distinguished two kinds of organizational change. Episodic change is infrequent, discontinuous and intentional: a restructuring or a system replacement. Continuous change is ongoing, evolving and cumulative, made of many small adjustments in daily work.

Shona Brown and Kathleen Eisenhardt studied six computer firms that changed continuously and found that the successful ones combined limited structure with rhythmic, time-paced transitions.

The continuous change cycle is therefore a way of making change part of normal work rather than an interruption to it.

The best-documented loop comes from quality improvement. Walter Shewhart described a cycle of specification, production and inspection in 1939. W. Edwards Deming taught a version of it in Japan in 1950, where it became known as Plan–Do–Check–Act (PDCA). Deming later preferred Plan–Do–Study–Act (PDSA), arguing that "study" describes learning better than "check".

1. Plan: state the change, predict its effect and decide how to measure it.
2. Do: try it on a small scale.
3. Study: compare the results with the prediction.
4. Act: adopt, adapt or abandon the change, and plan the next cycle.

The diagram on this page shows PDSA as one sourced example. It is not the cycle defined in the APMG course text, which uses its own stages.

The continuous change cycle, in its PDSA form, is therefore a disciplined learning loop, not a one-off trial.

Brightwater Health wants to reduce missed outpatient appointments. Instead of redesigning the booking process at once, a clinic team runs short cycles:

1. Cycle 1: send a text reminder two days before appointments for one clinic, predicting fewer missed slots. Missed appointments fall a little.
2. Cycle 2: add a reply option to cancel. Freed slots are now rebooked, a gain the team had not predicted.
3. Cycle 3: extend the reminders to two more clinics and check whether the effect holds with different patient groups.

Each cycle is small enough to stop if it fails. The team records predictions and results, so learning builds across cycles.

The continuous change cycle works, as here, when the team can test changes quickly and measure their effect.

Continuous cycles suit changes where the right solution is not known in advance, where the environment keeps shifting, and where small tests are cheap and safe. They fit well with agile delivery, which also works in short iterations.

They fit less well when a change must happen at once: a regulatory deadline, a single-date system cutover or a merger. These are episodic changes, better handled with a planned approach, although continuous cycles can follow them to embed and improve the new way of working.

Many organizations combine both: episodic change for the structural shift, continuous cycles for refinement.

The continuous change cycle is therefore one approach in a change manager's repertoire, chosen to fit the situation.

Iterative cycles have a long record in quality improvement and are simple to teach. They also have limits.

• No single model. "Continuous change cycle" names a family of loops. Labels and numbers of stages differ between sources, which causes confusion.
• Weak execution. A systematic review of PDSA in healthcare by Michael Taylor and colleagues found that many reported projects did not follow the method's core features, such as iterative cycles and measurement over time.
• Change fatigue. Constant change without visible results can tire people.
• Local focus. Small cycles may miss problems that need structural or strategic change.

The continuous change cycle is therefore most useful when its discipline is respected and when it sits within a clear direction.