keymodels
Menu
SearchStart free
All comparisons

Compare

Change management: Kotter’s eight-step model vs 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
Organisational behaviour

Change management: Kotter’s eight-step model

Many executives struggle to implement change in their organisations, and the larger the firm, the bigger the challenge.

Kind
Framework / model
Complexity
Intermediate
Horizon
Strategic
Read article
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.

Kind
Process / method
Complexity
Accessible
Horizon
Operational
Read article

Choice logic

Use this when.

Change management: Kotter’s eight-step model

Use it to lead a significant organisational change, such as a new structure, technology platform or customer service model.

Eight phases of change (Kotter)

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.

Extracted signals

Strengths, limits, and pitfalls.

Change management: Kotter’s eight-step model

  • Make the change visible and emotionally meaningful as well as rational. Let people see a concrete problem resolved, feel the improvement and practise the specific behaviours that the new state requires.
  • Before starting, define the outcome, evidence of adoption, affected groups and constraints. Use the eight steps as a causal sequence rather than a rigid calendar: later work can begin before an earlier stage is “finished,” but skipping the underlying condition creates fragility. Adapt tactics to feedback while preserving the logic.

Watch for

  • Do not assume that senior leaders possess the right destination or sufficient commitment. The original model is strongest for sponsored, top down transformation; where those conditions fail, leadership renewal or a genuinely bottom up change process may be necessary.

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.

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.

Change management: Kotter’s eight-step modelOrganisational behaviourRead articleEight phases of change (Kotter)Organisational behaviourRead article

Application bridge

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 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 Impact AnalysisImpact Analysis Purpose. Use this analysis to explain the programme-wide consequences of a proposed change and provide the evidence for its decision. It supports the change management plan and change log by connecting the request to benefits, components, objectives, dependencies and controlled baselines. Application. A decision may approve, defer, modify or reject the request, or return it for add