What Are the 7 Key Steps of Change Management?
The 7 key steps of change management are: create urgency, build a guiding coalition, develop a clear vision, communicate relentlessly, remove obstacles, generate quick wins, and anchor change in culture. This framework, drawn from the Kotter model, applies equally to an AI project or an organizational restructuring.
But knowing the steps is not enough. What causes most transformation projects to fail is not the technology. It is the human element that gets forgotten along the way.
Step 1: Create a Sense of Urgency
Not manufactured panic. Real, documented, shared urgency.
When Maroc Cloud deploys Gemini Enterprise for its enterprise clients, the question is not “will AI change our business?” It is “how fast, and are we ready?” A leader who fails to create this sense of urgency in their team lets change happen to them rather than driving it.
In practice: show your sector data. Show what competitors are doing. Ask the question out loud: “What happens if we don’t move in the next 18 months?”
Step 2: Build a Guiding Coalition
Change is not decreed from the CEO’s office. It is built with credible relays at every level of the organization.
This coalition is not another committee. It is a group of people with real influence, not just a title. A respected frontline manager is often worth more than a distant director in this role.
Step 3: Define a Clear Vision and Strategy
If you cannot explain your transformation in two sentences to a frontline employee, you have not fully understood it yourself.
The vision must answer three simple questions: where are we going, why now, and what does this change for each person? AI projects that fail in organizations most often fail here. A tool gets deployed without explaining what it replaces, what it improves, and what teams need to do differently. I have built a 6-dimension diagnostic framework to evaluate exactly this in transformation projects. Download the AI Board Pack 2026.
Step 4: Communicate the Vision Relentlessly
A single all-hands announcement is not enough. Change communication is daily, repetitive, and deliberately redundant work.
Kotter describes a factor of 10: organizations under-communicate their vision by a factor of 10 compared to what is actually needed. What I observe with my clients is that teams hear the message once, then return to their habits. The middle manager’s role is to repeat, illustrate, and connect every operational decision to the broader vision.
This is especially true in AI integration projects. As I explained in my analysis of AI’s impact on human resources management, employees do not fear the technology itself. They fear not understanding what is expected of them.
Step 5: Remove Structural Obstacles
This is where things get concrete. Obstacles are rarely people of bad faith. They are outdated processes, evaluation systems that reward old behaviors, and silos that block information flow.
A direct example: you deploy a conversational agent for your customer service. But your advisors are evaluated on call volume, not resolution quality. Result: they work around the tool. Not out of resistance. Out of logic.
Removing obstacles means aligning incentives with the desired direction.
Step 6: Generate Quick, Visible Wins
Long transformations lose momentum. Teams need to see concrete results before they believe the change is real.
Quick wins are not announcements. They are measurable results, achieved within the first 90 days, that prove leadership is serious and that the new way of working actually works. Choose simple use cases with high visible impact, and communicate them without false modesty.
In Morocco, recent signals are clear: AI is transforming the tasks of young graduates before transforming their jobs. This is a strategic window to show quick gains without triggering massive resistance. As I analyzed in my article on which jobs will survive AI, the organizations that win are those that show concrete results early.
Step 7: Anchor Change in Culture
This is the step most organizations skip. The deployment gets celebrated, everyone moves on, and six months later the old habits are back.
Anchoring change means modifying what you recruit for, what you evaluate, what you reward, and what success stories you tell internally. Culture does not change by decree. It changes when new behaviors become the expected norm, not the applauded exception.
If you are a CHRO or CEO and want to structure your change management approach for an AI or organizational project, request a free diagnostic.
What This Means Concretely for a Leader
These 7 steps are not a checklist. They are sequential and interdependent. Skipping step 2 to jump to step 5 produces resistance you will not have anticipated.
The Kotter model was designed for complex organizational transformations. It applies equally to an HR process redesign and to an enterprise-scale AI deployment. What changes with AI is the speed at which steps 1 and 2 must be completed. The market does not wait.
For more on building team capabilities in this context, read my practical guide on AI training in Morocco.
FAQ
What is the difference between change management and project management?
Project management drives deliverables: timelines, budget, scope. Change management drives people: adoption, resistance, behaviors. A project can be delivered on time and still fail if teams do not use it. Both disciplines are complementary, not interchangeable.
How long does a change management process take?
There is no standard duration. A limited process change can be managed in a few weeks. A deep organizational transformation takes 18 to 36 months. What remains constant: steps 1 through 4 must be solid before moving to execution, otherwise you are building on sand.
Can these 7 steps be applied to an AI integration project?
Yes, and it is essential. AI projects rarely fail for technical reasons. They fail because teams did not understand why, because middle managers were not brought on board, and because no quick results were shown. The 7 steps apply in full.
What is the CHRO’s role in change management?
Central. The CHRO is often the guarantor of coherence between the announced vision and the actual HR systems: evaluation, recruitment, training, compensation. If these systems are not aligned with the desired change, employees will trust the systems, not the speeches.