Organisational behaviour
Eight phases of change (Kotter)
Kotters’s eight phases of change is a systematic approach to achieving successful, sustainable change by breaking down the change process into eight phases.
Read article
keymodelsAll comparisons
Compare
Eight phases of change (Kotter) vs The eight phases of change (Kotter)
The corpus marks this as a duplicate or close editorial overlap. Use the comparison to preserve provenance and decide which public article treatment is the better starting point.
Close overlapchangeOperationsOperations
Strategy
The eight phases of change (Kotter)
This is not a book on strategy implementation, let alone on the complexities of change management, but it is an inescapable fact that strategy.
Read articleChoice logic
Use this when.
Use the framework when change requires coordinated leadership across a substantial organisation. Kotter distinguishes management—keeping complex operations reliable—from leadership—defining a future, aligning people and generating commitment. The model helps leaders organise that mobilisation without mistaking a new structure or system for completed change.
During strategy formulation, anticipate the change programme that implementation will require rather than treating execution as a later concern.
Extracted signals
Strengths, limits, and pitfalls.
Eight phases of change (Kotter)
- Build urgency from shared evidence and a credible opportunity, then maintain it with visible progress. Fear without agency exhausts people; urgency should clarify why action matters and what people can do now.
- Create urgency. Replace complacency with credible evidence that the status quo carries material risk or that a time limited opportunity exists. Avoid manufacturing panic.
- Build the guiding coalition. Assemble people with authority, expertise, credibility, relationships and commitment. Develop enough trust to resolve difficult trade offs.
Watch for
- Do not treat the phases as a communications campaign or declare completion after early wins. Structural barriers, incentives and cultural reinforcement determine whether new behaviour survives once leadership attention moves elsewhere.
The eight phases of change (Kotter)
- Build urgency, coalition and vision before launching a broad programme, then use visible wins to deepen—not declare victory over—the change.
- Treat the phases as a connected logic rather than a rigid waterfall. Diagnose where the organisation is weak, then build enough urgency, sponsorship and clarity before demanding widespread behaviour change. Reinforce communication with decisions, resources and examples; claims that conflict with incentives will not create buy in.
- Use complementary lenses where appropriate. Lewin’s unfreeze–change–refreeze model emphasises readiness and stabilisation, while the Kübler Ross change curve is often adapted to discuss emotional reactions—though it should not be treated as a predictable sequence for every employee.
Watch for
- No change situation follows a generic sequence perfectly. Adapt the model to context without removing its essential implementation logic.
Read next
Open the full model articles.
Each comparison links back to the full articles so you can inspect examples, steps, caveats, and related templates before choosing.
Application bridge
Related templates.
Component Transition RequestComponent Transition Request Purpose. Use this request to obtain formal approval to close a programme component and transfer its deliverables, knowledge, responsibilities and benefits to operations, customers or users. It demonstrates that the component has sufficiently satisfied its business case, completed its required deliverables and milestones, and is ready for its final lifecycle transition.Program MandateProgram Mandate Purpose. Use the mandate to state why an approved programme belongs in the organization's portfolio and to carry its strategic intent into formal initiation. It summarizes the vision, objectives, benefits, boundaries, resources, exposure and governance expected before detailed definition begins. Application. The sponsor normally prepares the mandate after the business case, with inProgram Risk Management PlanProgram Risk Management Plan Purpose. Use this plan to define how the programme will identify, analyse, respond to, monitor and communicate uncertainty. Risks may create positive or negative effects, arise externally or within components, and combine across projects, operations and benefits in ways that require programme-level action. Application. Tailor the depth and visibility of risk managementChange Management PlanChange Management Plan Purpose. Use this plan to define how programme changes are proposed, assessed, decided, implemented, verified and communicated. It coordinates change across components and evaluates consequences for programme outcomes, benefits and other affected programmes rather than treating each request in isolation. Application. Develop the plan early, make it available to stakeholders