What Are the 4 Steps of Change Management?

Change management follows four sequential phases: diagnose and prepare the ground, mobilize stakeholders, deploy the change in a structured way, then embed new practices for the long term. These four steps apply whether you are integrating a new tool, restructuring an organization, or absorbing an acquisition. The sequence does not change. What changes is the intensity of each phase depending on your context.

What I observe with my clients: most projects that fail do not fail on the technology. They fail because nobody truly worked through these four steps in order.

Step 1: Diagnose Before Acting

Before announcing anything, you need to understand what you are actually changing.

Not just the process on paper. The way people work today, the informal habits, the latent resistance. A CHRO who launches an HR process redesign without mapping the real practices of their frontline managers is heading straight for a wall.

Kurt Lewin’s model, developed in the 1940s and still relevant, calls this phase “unfreezing.” You create the conditions for people to accept letting go of what they do today. It starts with an honest diagnosis: what is blocking, what is working, who are the informal influencers in the organization?

Concrete tools for this step: individual interviews with key managers, mapping of current processes, identification of potential resistance. Not an online survey sent to 200 people. Real conversations.

Step 2: Mobilize Stakeholders

Once the diagnosis is done, you have a choice. Either you communicate the change. Or you co-build it.

Communication alone never suffices. People do not adopt what is imposed on them. They adopt what they contributed to. This is true in Casablanca as much as in Brussels.

John Kotter, in his eight-step model, insists on building a guiding coalition from the start. Not a project committee. A coalition of people who believe in the change and who have real influence in the organization, formal or informal.

In the projects I accompany, this step is systematically underestimated. Two weeks are spent preparing slides and three days identifying the real change agents. It should be the other way around.

The question to ask each key stakeholder: “What will this change actually change for you, concretely?” If you do not have a precise answer for each profile, you are not ready to deploy.

This is also the step where you build your communication plan. A plan that includes feedback loops, spaces for teams to express their doubts, and prepared responses to the most predictable objections. Not a one-way broadcast with no return.

I have built a methodological framework to structure exactly this mobilization phase in complex change management projects. Download the AI Board Pack 2026 if you are leading a transformation that involves artificial intelligence tools.

Step 3: Deploy in a Structured Way

Deployment is where everyone wants to go directly. And it is where most projects unravel.

Two principles to hold absolutely.

First principle: pilot before scaling. Choose one unit, one team, one site. Deploy there. Observe what actually happens. Adjust. Then extend. Scaling without a pilot is the fastest way to create massive resistance.

Second principle: train managers before teams. The frontline manager is the primary vector of adoption or rejection. If your team leader has not understood the change, does not believe in it, or cannot answer their team’s questions, you have a problem that internal communication alone will not solve.

Skill-building must be targeted. Short modules, adapted to roles, with concrete use cases drawn from the teams’ daily work. As I explained in my analysis on using AI in business, the same logic applies to any new tool deployment: training must match the real work context.

Track the indicators that matter during deployment. Not the training participation rate. The actual usage rate of the new tool or process two weeks after training. That is what tells you whether the change is taking hold.

Step 4: Embed for the Long Term

Lewin called this phase “refreezing.” You solidify the new practices so they become the norm.

This is the step organizations most often rush through. The project is declared finished, the project team is disbanded, and six months later people have reverted to their old habits.

Embedding change means three concrete things.

First, integrate new practices into manager evaluation processes. If you have changed how annual reviews are conducted and managers are not evaluated on their adoption of the new process, they will revert to the old one. What is not measured is not done.

Second, celebrate intermediate wins. Kotter makes this a central point of his model. Not for hollow internal communication. To show teams that the change is producing tangible results. This reinforces the project’s legitimacy and reduces residual resistance.

Third, name accountability owners for sustainability. Not a project manager. Operational owners who are responsible for maintaining new practices within their scope. Responsibility and accountability must be clear and named.

Moroccan organizations that succeed in their transformations all share one thing: they treat the embedding phase with as much seriousness as the deployment. It is not the end of the project. It is the beginning of the new normal.

Recent market signals from Morocco are worth noting. Le Matin.ma recently headlined on the risk of Moroccan companies remaining in a logic of simple AI consumption. If that diagnosis holds, it is precisely the symptom of a missed step 4: a tool is adopted, practices do not change.

Pitfalls to Avoid

Three mistakes I see come back systematically.

Skipping step 1 because you are in a hurry. The diagnosis takes time. It saves much more time afterward.

Confusing communication with mobilization. Sending an email from senior leadership is not change management. It is information. Mobilization is fieldwork.

Declaring victory too early. A change is embedded only when new practices survive the departure of the people who championed them. Not before.

If you are leading a transformation involving artificial intelligence tools, change management stakes are amplified. Teams have specific concerns about jobs and skills. Le360 recently noted that AI is transforming the missions of young graduates, not their jobs. That kind of nuance deserves a structured response in your mobilization plan, not generic reassuring communication. You will find complementary insights in my article on the 4 types of artificial intelligence, which helps demystify what AI actually changes in different roles.

If you are a CHRO or CEO and want to structure your change management approach, request a free diagnostic. We look together at where you stand and what is blocking.

FAQ

What is the difference between Lewin’s model and Kotter’s?

Lewin proposes three phases: unfreeze, change, refreeze. It is a simple and powerful conceptual framework. Kotter details eight operational steps within that framework. Both are compatible. Lewin gives you the logic, Kotter gives you the action plan.

How long does change management take?

It depends on the scope of the change and the size of the organization. A process change for a team of 20 people can be managed in two to three months. A deep organizational transformation across several hundred people often requires twelve to eighteen months, including the embedding phase.

How do you measure the success of change management?

Not with post-training satisfaction rates. With the actual adoption rate of new practices at three months, six months, and one year. And with the business indicators that motivated the change in the first place: productivity, quality, timelines, staff turnover.

Do you need an external firm to manage change?

Not necessarily. What you need is a clear method, identified internal change agents, and senior leadership that is visibly committed. External support brings methodology and an outside perspective on resistance. It does not replace internal commitment.