The core idea
Kotter’s approach addresses urgency, a guiding coalition, vision, broad participation, removing barriers, short-term wins, sustained momentum and embedding change. The later accelerators are presented as more iterative than the original linear sequence. Our six-part sketch groups those ideas for readability; it is an editorial overview, not a reproduction of the official eight-step diagram.
Source and attribution [1]Using it in practice
Define the problem in terms employees can verify. Invite people with operational credibility into the change group, including those who see risks. Separate communication from participation: a well-written announcement does not give someone time or authority to work differently. Choose early results that matter to users and publish what did not work as well as what did. Align resources and incentives before declaring the change embedded.
An example, not a reported case
Worked example · illustrative
A company introduces a new performance conversation process. Managers and employees co-design a short pilot, identify confusing questions and remove duplicate forms. An early win is a clearer development decision, not merely a high form-completion rate. The project team monitors time spent and perceived usefulness, then adjusts training and workload before expanding. Senior leaders use the same process so the new expectations are credible.
What to watch for
Urgency should not become manufactured fear. Organisational changes may involve legal consultation duties that a management framework cannot replace.
Create a case for change that can be questioned
Explain the problem with evidence and show the consequences of leaving it unresolved. Avoid manufacturing urgency through fear or presenting the preferred solution as the only possible answer. Invite people close to the work to challenge assumptions. In an illustrative scheduling change, the case might concern late notice, uncovered shifts and payroll corrections. A credible change story connects the operational problem with employee experience and admits what is not yet known.
Build participation beyond senior sponsorship
Identify people with formal authority, operational knowledge and informal credibility. Include those who will carry out the change and those likely to notice unintended effects. Clarify what they can influence and what constraints are fixed. A coalition that agrees in meetings but cannot remove workload or system barriers may achieve little. Ask what decisions the group can actually make and how unresolved issues will reach someone with authority.
Design an early result that tests the change
A useful early win demonstrates the intended behaviour or outcome, not just launch activity. For a new scheduling process, a pilot might show more reliable advance notice without an increase in uncovered shifts. Agree the measurement and comparison before the pilot begins. Include negative feedback and exceptions. Do not choose a uniquely easy site and present its result as proof that the same approach will work everywhere.
Make the new practice sustainable
After initial adoption, examine incentives, training, systems and manager routines. If the old process remains easier or better rewarded, people may reasonably return to it. Assign ownership for maintenance and for revising the approach as conditions change. Kotter's framework is a guide to mobilisation, not a guarantee or a rigid sequence for every setting. In urgent or evolving work, steps may overlap; preserve the underlying questions rather than treating the model as a ceremonial checklist.
Build a coalition with knowledge and credibility
Include people who understand the affected work and can identify practical barriers, not only senior sponsors. Explain the case for change with evidence and acknowledge what is uncertain or contested. Manufactured urgency can damage trust and suppress useful challenge. Ask what will make employees believe the new direction is real: a changed decision, resource commitment or removed obstacle may matter more than a launch event.
Use early results to learn, not only to persuade
Choose a limited change that tests an important assumption and produces evidence people can examine. If a new handover improves quality but increases workload, report both. Adapt before scaling and explain what was learned. Aylott’s employment-relations perspective reminds managers that involvement and legitimate disagreement remain important during change. The steps can organise attention, but real change may loop back, proceed unevenly or need a different sequence; do not declare resistance simply because experience fails to follow the diagram.
Take it into your next conversation
Three useful questions.
- Who has credibility with the people affected?
- What practical barrier remains?
- What would show the change works after the project team leaves?
Go to the evidence
Sources & attribution
[1] Kotter. The 8 Steps for Leading Change and their evolution into accelerators. ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.
Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach