Loading content
Kotter’s 8-step model is a structured framework for managing organizational change. It outlines eight sequential actions from creating urgency to anchoring new practices, aimed at minimizing resistance and ensuring durable transformation. It functions as a practical roadmap for change initiatives at team and enterprise levels.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Kotter's 8-Step Change Model is a leadership framework for larger organizational change. It describes urgency, a guiding coalition, vision, mobilization, enablement, short-term wins, consolidation, and anchoring.
John P. Kotter introduced the model in his 1995 Harvard Business Review article “Leading Change: Why Transformation Efforts Fail” and later developed it at Kotter Inc. It distills observations from change programs into eight recurring leadership tasks.
Read the eight steps as a staircase with feedback: first build shared urgency and a credible leadership group. Communicate a vision, remove obstacles, use early wins to build credibility, and finally anchor new ways of working in structures and culture.
Shared understanding of why change matters mobilizes attention and readiness to act.
Influential participants combine legitimacy, decision power, and energy for change.
New behaviors become durable through results, structures, and succession practices.
The model helps review change initiatives against leadership tasks and common gaps. Its steps are a heuristic rather than a universal sequence; rigid use can weaken learning, participation, and local adaptation.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.