Kotter’s 8-Step Change Model
Kotter's 8-Step Change Model
What is Kotter’s 8-Step Change Model?
- Urgency → Coalition → Vision → Communication → Empowerment → Short-term wins → Consolidation → Anchoring
- Core claim: skipping steps leads to failure
- Short-term wins within 6–18 months keep momentum alive
What this framework actually changes is the timetable of the team driving the change. Most transformation projects fill the days after kickoff with system go-live dates, training schedules, and deliverable lists, but Kotter forces four slots in front of them: urgency, coalition, vision, and communication. The first four steps are work that makes room in advance for people to change their minds, steps 5–7 are the execution phase where actual ways of working are rebuilt, and step 8 is the anchoring work that keeps the organization from sliding back to old habits even when the people in charge change. The cost of a skipped step is billed late in the project.
Kotter was quite specific about his benchmarks. Urgency must reach the point where about 75% of executives and managers believe that 'staying put is riskier than changing,' and short-term wins must be visible within 6–18 months of launch. In his 2014 book Accelerate, however, he revised the 8 steps himself: not a sequential staircase but eight accelerators running at the same time, with the existing hierarchy and a network of volunteers working in parallel as a dual operating system. Kotter addresses the sequence for the organization, while ADKAR addresses the readiness of the individual, so the two models are not competitors; they work at different levels.
The most common point of failure in practice is reading step 1 as fear-mongering. A vague warning that 'the company is in trouble if this continues' builds no capacity to execute and only increases job searches among key talent. Staffing the coalition with people who happen to have spare time is the same failure: a plan made by a team with neither authority nor credibility is quietly rejected by the line organization. Another common move is swapping short-term wins for 'easy tasks.' If you automate a task nobody minded and put it in the progress report, the real bottleneck goes untouched while momentum drains away. If the 8 steps become just the table of contents of a kickoff deck, six months later you are left with a system that is live and that nobody uses.
Yeonmi SongSpecialist instructor and coach in relationship management, resilience, and self-leadership
John KimInstructor John Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”John P. Kotter, a professor at Harvard Business School, presented it in his 1995 Harvard Business Review article “Leading Change: Why Transformation Efforts Fail” and expanded it in his 1996 book Leading Change.
Consider a hypothetical case. Company A, an auto-parts manufacturer with 740 employees and annual revenue of KRW 230 (≈ US$1) billion, introduced an AI scheduler for production planning at its 3 plants, but six months after launch on-site usage stayed at 18%. Planners kept running their own Excel sheets, and 'the system doesn't know our line' came up in every meeting. The corporate planning office redrew a 12-month relaunch plan with Kotter's 8 steps as its backbone.
- It started when the CEO put up, in an executive meeting, the original email from a key customer's purchasing team asking for 'delivery-date replies within 8 hours instead of 48,' and said, "At this rate, we'll be off next year's bidder list."
- Instead of people with spare time, the coalition included the three busiest planning managers from across the plants. The head of production put it on record in the meeting minutes: "We will free up 30% of these three people's regular workload," making the secondment official.
- The team boiled the vision down to one sentence, 'delivery-date replies within 8 hours,' and repeated it across different channels for three months: factory morning meetings, the internal bulletin board, and one-on-one talks with team leaders. They did not stop at a single company-wide announcement.
- The team chose rush-order rescheduling, the overtime-inducing task the floor hated most, as its first project. In five months, handling time per order fell from 4 hours to 25 minutes, and Manager Kim, who was most affected by the task, presented the case study personally.
- After 12 months, scheduler usage rose from 18% to 86%, and the average time to confirm delivery dates with customers fell from 41 hours to 9. The new process was written into the planner job description and new-hire onboarding, and the parallel Excel operation was retired.