In 2022, the average employee experienced ten planned enterprise changes simultaneously. In 2016, that number was two. Gartner’s research on change fatigue documents what happened next: employee willingness to support change collapsed from 74% to 43% in the same period.

That collapse is not a cultural problem. It is a process problem. The change management process most organisations still use was designed for a world where major transformation happened once every few years. It was built on linear, sequential logic: assess, plan, deploy, embed. Each phase completes before the next begins. Business as usual is suspended while the change happens. Then it resumes.

That model has been structurally broken for some time. The organisations that are still using it are not just inefficient , they are actively making change harder for their employees. This article examines why the traditional change management process fails in a high-velocity environment, what a modern iterative approach looks like, and how to make the shift without starting from scratch.

Why the waterfall change management process struggles at pace

The traditional change management process borrows its logic from waterfall project management: define requirements, plan in detail, execute in order, hand over to operations. Its appeal is its clarity. Everyone knows where they are in the process. Progress can be tracked against a plan.

The problem is that this logic assumes a level of environmental stability that no longer exists in most large organisations. By the time a twelve-month change programme has completed its planning phase and is ready to deploy, the business conditions that informed the design have often shifted. Stakeholders who were engaged at the start have moved on. The technology landscape has changed. A new leadership priority has landed. The organisation that was going to receive this change is not the same organisation that commissioned it.

McKinsey research on agile organisations consistently finds that organisations using iterative methodologies succeed at significantly higher rates than those using linear approaches. The mechanism is straightforward: iterative approaches build in the capacity to learn and adjust, rather than treating every deviation from the plan as a failure.

The second structural problem with the traditional change management process is that it treats adoption as a phase rather than a continuous state. The “embedding” phase at the end of a waterfall change programme is meant to lock in new behaviours after go-live. But adoption does not work this way. Behaviour change is not a state you reach , it is something you continuously maintain, reinforce, and measure. A process that treats embedding as a finite activity will almost always underinvest in it.

The three levels of the modern change management process

Before redesigning the change management process, it helps to be clear about what a change management process is actually trying to achieve. McKinsey’s framework for change identifies three levels of ambition, each of which calls for a different process:

Level 1: Compliance

The goal is that people adopt new procedures, processes, or tools. This is the most transactional form of change management and requires the shortest change process. Communication, training, and structured support are the primary mechanisms.

Level 2: Mobilisation

The goal is preparing employees for broader shifts that require new behaviours and ways of working. This requires more sustained engagement, leadership involvement, and reinforcement over a longer period.

Level 3: Transformation

The goal is improving performance and organisational health by embedding new management practices that change the way the organisation operates. This is the most complex form of change and cannot be managed through a linear, time-bounded process. It requires continuous measurement, iteration, and leadership commitment over years, not months.

Most organisations apply the same process regardless of which level they are operating at. The result is that compliance-level changes get over-engineered, and transformation-level changes get under-resourced.

What a modern, iterative change management process looks like

An iterative change management process is not simply a faster version of the waterfall model. It is a fundamentally different design. Rather than completing each phase before beginning the next, it runs phases in parallel, builds feedback loops into the process, and treats each sprint or cycle as an opportunity to adjust.

Here is what each stage looks like in practice:

Stage 1: Orientation and framing (weeks 1-3)

Rather than a comprehensive upfront planning phase, orientation focuses on the essential questions: who is affected, how significantly, what are the non-negotiables, and what can flex? The output is a lightweight change canvas rather than a detailed change management plan. The canvas captures impact, stakeholder profile, key risks, and the initial hypothesis for the change approach.

This stage should be done with the project team, not after the project team has finished its planning.

Stage 2: Iterative cycles (throughout programme delivery)

Change management activity is structured in four-to-six-week cycles, each with a clear focus and a measurable outcome. A cycle might focus on leader alignment, a specific stakeholder group’s readiness, or the training design for a particular module.

Each cycle ends with a short retrospective: what did we learn? what changed in the environment? what needs to adjust? This retrospective is not a sign of failure , it is how the process gets smarter over time.

Key activities within each cycle include:

• Stakeholder pulse checks (short surveys or structured conversations)
• Review of adoption indicators (early usage data, support ticket patterns, manager feedback)
• Communication and engagement delivery against the current cycle’s priorities
• Adjustment of the next cycle’s plan based on what was learned

Stage 3: Go-live support (weeks surrounding each release)

Go-live in an iterative environment is not a one-time event. Multiple releases may occur across the programme’s life. For each release, the change process focuses on:

• Ensuring the affected groups are ready (not just informed)
• Having reinforcement mechanisms in place at the team level
• Monitoring adoption metrics from day one, not week four

Stage 4: Adoption management (ongoing, post-go-live)

This is the stage most waterfall processes either skip or treat as complete once training has been delivered. In an iterative model, adoption management continues until adoption indicators demonstrate genuine embedding, not just initial usage.

Adoption management activities include:

• Regular adoption reporting to programme and business leadership
• Targeted intervention for groups or roles showing lagging adoption
• Reinforcement through leadership visibility and peer recognition
• Updating supporting materials as practice evolves

The five principles that separate modern change management from the waterfall approach

Beyond the structural shift to iterative cycles, modern change management rests on five principles that distinguish it from its waterfall predecessor.

1. Start with impact, not activity. Traditional change processes generate activity plans: communication sent, training delivered, workshops run. Modern change management starts with impact data: which groups are most affected, how severely, and what does that mean for how they need to be supported? Activity follows from impact analysis, not from a template.

2. Measure behaviour, not completion. Sending a communication is not the same as people understanding the change. Delivering training is not the same as people being able to do their jobs differently. Modern change management tracks behavioural indicators , adoption rates, usage patterns, manager confidence, stakeholder sentiment , not just activity completion.

3. Run change management with the project, not after it. The persistent failure of change programmes that “bolt on” change management late is well-documented. Prosci’s research on change management timing consistently shows that early involvement in programme design, not just programme delivery, produces materially better outcomes.

4. Treat leaders as active participants, not passive sponsors. The role of executive sponsorship in change outcomes is one of the most consistently supported findings in the research literature. But modern change management goes further than securing a sponsor name on a communications template. It designs for active, visible leadership engagement at the moments that matter most to employees , particularly during transitions that affect role security, team structure, or ways of working.

5. Manage the portfolio, not just the programme. The Gartner finding that employees experienced an average of ten simultaneous changes underscores the problem with programme-level change management in isolation. Modern change management requires a portfolio view , tracking cumulative change load across the employee population and making explicit decisions about sequencing, pacing, and priority.

Common failure modes in the modern change management process

Even organisations that have adopted an iterative model run into predictable failure modes.

Iterations without real retrospectives. Running four-week cycles is not the same as running iterative change management. The value comes from the disciplined retrospective that follows each cycle , the honest assessment of what is working, what is not, and what needs to change. Organisations that go through the motions of iteration without genuine reflection get the overhead without the benefit.

Confusing speed with agility. Moving faster through the same linear process is not agility. Agility is the capacity to adjust direction based on new information. A team that compresses a twelve-month waterfall plan into six months is not running an iterative process , it is running a compressed linear one.

Under-resourcing the analytical function. An iterative change management process produces more data than a waterfall one. Adoption metrics, stakeholder pulse results, usage data, and portfolio load information all need to be collected, analysed, and acted on. Without the analytical capacity to do this, the feedback loops that make iteration valuable cannot function.

How digital tools support an iterative change management process

Iterative change management generates a data challenge that manual processes cannot easily handle. Change practitioners need to track adoption across multiple concurrent releases, monitor stakeholder sentiment across different groups, and maintain a real-time picture of cumulative change load.

This is where purpose-built change management platforms add operational value. Tools like Change Compass allow change teams to consolidate portfolio-level change data, track adoption metrics in real time, and generate the reporting that keeps programme teams and business leaders aligned on what is actually happening on the ground. For organisations running iterative change management at scale, this kind of digital infrastructure is not optional , it is what makes the process sustainable.

Making the shift: where to start

If your organisation is currently running a waterfall change management process and you want to move to an iterative model, here is a practical starting point.

Choose one active programme and run the next delivery phase as an iterative cycle rather than a phase-gate sequence. Define a four-to-six-week cycle, set one measurable adoption goal for that cycle, run a structured retrospective at the end, and adjust the next cycle based on what you learn.

You do not need to redesign your entire change methodology before starting. The iterative model is self-improving , each cycle builds the evidence base for the next one. What you do need is the leadership support to treat a retrospective’s findings as actionable, not defensive.

The organisations that have moved farthest toward modern change management are those that started with a small, visible experiment and used its results to make the case for broader adoption. That is, itself, an iterative approach.

Frequently asked questions

What is a change management process?

A change management process is the structured approach an organisation uses to plan, deliver, and embed change , covering everything from initial impact assessment through to adoption monitoring after go-live. A modern change management process is iterative rather than linear, running short cycles with feedback loops rather than sequential phases that must complete before the next begins.

What is the difference between agile and waterfall change management?

Waterfall change management completes each phase , planning, communication, training, embedding , in sequence before moving to the next. Agile or iterative change management runs these activities in parallel cycles, typically four to six weeks long, with a retrospective at the end of each cycle to assess what is working and adjust the next cycle’s plan. The iterative model handles environmental change better and tends to produce better adoption outcomes.

Why do change management processes fail?

The most common failure modes are: late involvement of change practitioners in programme design, treating adoption as a final phase rather than an ongoing state, measuring activity completion rather than behaviour change, and failing to manage cumulative change load across the employee population. Organisations that run change management as a project-level add-on rather than a portfolio-level discipline are particularly vulnerable.

How long should a change management process take?

Duration depends on the scale and complexity of the change. A compliance-level change might require a process of two to three months. A major transformation that requires genuine behaviour change and cultural shift may require sustained change management activity over two to three years. The mistake is applying a fixed time horizon to a change before assessing what level of change it actually requires.

How do you measure a change management process?

Effective measurement combines leading indicators , stakeholder readiness assessments, manager confidence surveys, early adoption rates , with lagging indicators , business performance metrics, sustained usage data, quality outcomes. The key shift from traditional measurement is tracking what people are actually doing differently, not what change management activities have been completed.

References

• Gartner. (2024). Gartner Says Finance Leaders Should Factor Change Fatigue into Project Planning. https://www.gartner.com/en/newsroom/press-releases/2024-02-27-gartner-says-finance-leaders-should-factor-change-fatigue-into-project-planning
• McKinsey & Company. (2024). The journey to an agile organisation. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-journey-to-an-agile-organization
• McKinsey & Company. (2024). Change is changing: How to meet the challenge of radical reinvention. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/change-is-changing-how-to-meet-the-challenge-of-radical-reinvention
• Prosci. (2024). Best Practices in Change Management. https://www.prosci.com/blog/change-management-best-practices
• Gartner. (2023). Gartner Says HR Leaders can Reduce Employee Fatigue with Proactive Change Management. https://www.gartner.com/en/newsroom/topics/human-resources/2023-09-12-gartner-says-hr-leaders-can-reduce-employee-fatigue-with-proactive-change-management