What Are the 4 Stages of Change?

The 4 stages of organizational change are: preparation (diagnosis and creating urgency), planning (defining the vision and roadmap), implementation (deployment and on-the-ground change management), and consolidation (embedding new practices into culture). These stages apply to any transformation project, whether an AI deployment or an HR restructuring.

This is not classroom theory. It’s what I observe in the projects I lead, from Casablanca to Brussels. Organizations that fail don’t fail at technology. They fail at the stages.

Stage 1: Preparation

Before changing anything, you need to answer one simple question: why now?

Kotter, in his 8-step model, places creating a sense of urgency first. Not by accident. Without perceived urgency, teams wait. They watch. They resist passively.

In practical terms: the CHRO or CEO must conduct an honest diagnosis. What are the performance gaps? What external pressures are bearing down on the operating model? In Morocco, companies integrating AI into their processes often do so under competitive pressure, not strategic conviction. That’s a warning sign.

Preparation also means identifying key stakeholders. Who will block? Who will champion the change? These two questions are worth more than any communication plan.

Lewin calls this phase “unfreezing.” The idea: before reshaping the ice, you have to melt it. In other words, destabilize existing certainties before installing new practices.

Stage 2: Planning

Once urgency is established, you need a clear direction. Not an 80-page document. A vision that every manager can explain in two sentences.

This is where many organizations lose time. They confuse planning with bureaucracy. They produce deliverables instead of making decisions.

The roadmap must answer three questions: Where are we going? Who does what? How do we measure progress?

On that last point, tracking indicators must be defined before deployment, not after. A change management project without a steering dashboard has no real accountability.

I’ve built a 6-dimension diagnostic framework to assess an organization’s change readiness, particularly for AI integration projects. Download the AI Board Pack 2026 to access the full framework.

Stage 3: Implementation

This is where everything is decided. And where most projects go off the rails.

Why? Because implementation exposes the gaps between what was planned and what is real. Resistance becomes visible. Middle managers, often forgotten during planning, become the real friction point.

In the projects I accompany, the rule is simple: change is won at the N-1 and N-2 level, not at the executive committee. Frontline managers make or break team buy-in.

Lewin calls this phase “movement.” Kotter talks about “generating quick wins.” Both are right. You need to move forward, but you also need to show intermediate results to maintain momentum.

A concrete example: a Moroccan company deploying an automation tool on its administrative processes cannot wait 12 months to show a result. It must identify a pilot use case, succeed within 6 to 8 weeks, and communicate it internally. That’s what creates momentum.

On this topic, my analysis on the best AI for a business provides concrete benchmarks for choosing the right tools based on context.

Stage 4: Consolidation

Change is not complete when the project is delivered. It’s complete when new practices have become the norm.

This is the phase organizations most often rush through. The project is “closed,” project teams are disbanded, and six months later, old habits have returned.

Lewin calls this “refreezing.” The idea: new practices must be crystallized into processes, performance evaluations, and management culture.

In practice, this means: embedding new behaviors into annual review criteria. Training new hires on new practices from day one. And above all, publicly recognizing those who championed the change.

Without this stage, all the work from the first three phases evaporates.

If you’re a CHRO or CEO looking to structure your change management approach, particularly in an AI integration context, request a free diagnostic. We’ll assess where your organization stands together.

What the Models Don’t Say

Kotter and Lewin are useful references. But they were designed for Western, stable organizations with mature HR structures.

In the Moroccan and Belgian companies I observe, reality is more complex. Resources are often limited. Middle managers are undertrained in change management. And the pressure of day-to-day operations crushes transformation projects.

This isn’t a criticism. It’s context. And that context requires a more pragmatic, more sequenced approach, with short milestones and fast decisions.

As I explained in my analysis on AI training, building team skills is inseparable from change management. You cannot deploy new tools without preparing the people who will use them.

The 4 stages are not a recipe. They are reference points. The difference between an organization that succeeds at change and one that fails is rarely the quality of the plan. It’s the quality of execution, week after week.

FAQ

What is the difference between the 4 stages of change and Kotter’s model?

Kotter’s model details 8 specific steps. The 4 stages presented here are an operational synthesis that groups these 8 steps into 4 actionable phases: preparation, planning, implementation, consolidation. Both approaches are compatible.

How long does each stage of change take?

There is no standard duration. A change management project for a tool deployment can take 3 to 6 months. A deep cultural transformation can take 2 to 3 years. What matters is not skipping stages, especially consolidation.

Why do most change projects fail?

The most common causes are: insufficient urgency during preparation, middle managers not involved during implementation, and rushed consolidation that allows old habits to return. Technology is rarely the problem.

How do you get teams involved in change management?

By involving them early in the diagnosis, not just in execution. Teams that understand why change is necessary resist less. Those who are simply told about the change without explanation resist systematically. Communication must precede deployment, not merely accompany it.