Kotter's 8-Step Model: Guide, Critique and Practical Example for Change Processes

Kotter’s 8-Step Model is the most widely used change management framework in the world. John P. Kotter, professor at Harvard Business School, published it in 1995 as the HBR article Why Transformation Efforts Fail and expanded it in 1996 in the book Leading Change [1][2]. The model distills eight sequential steps that organizations must follow to implement change successfully — from establishing urgency to anchoring change in the culture.

What sets Kotter’s model apart from other change frameworks: it is the only one that explicitly demands a guiding coalition as the engine of change — not a project team, not a taskforce, but a powerful alliance of leaders who collectively carry the transformation. And it is the only one that identifies premature victory celebration as a distinct failure pattern.

Search for “Kotter 8-Step Model” and you will find dozens of results with the same eight headings. None analyzes the empirical critique — particularly Appelbaum et al. (2012), who found in a systematic review that the model has barely been empirically validated [3]. None explains Kotter’s own evolution to the dual operating system (2014). And none shows where Kotter reaches its limits — and where the ADKAR model or Force Field Analysis are better suited.

This guide closes these gaps. For a compact comparison of all change frameworks, see the overview article on change management models.

Origin: From HBR Analysis to Global Adoption

John P. Kotter (b. 1947) analyzed over 100 transformation initiatives in companies during the late 1980s and early 1990s. His finding: most failed not due to a lack of strategy or resources. They failed because of leadership errors — insufficient urgency, missing coalitions, premature celebration [1].

In 1995, he condensed these observations into the HBR article Why Transformation Efforts Fail, which became one of the most cited HBR contributions of all time. In 1996, the book Leading Change followed, elaborating the eight steps in detail [2]. The model became the standard reference for change management programs in corporations worldwide — and the starting point of an industry of consulting offerings, certifications, and trainings.

Context factor often overlooked: Kotter’s analysis is predominantly based on large US corporations of the 1980s and 1990s. Transferability to other cultural contexts, to mid-sized companies, or to agile organizational forms has not been empirically established — it is assumed [3].

The 8 Steps in Detail

Step 1: Create a Sense of Urgency

The first step is simultaneously the most underestimated. Kotter argues: without a shared sense of urgency, there is no energy for change. Employees and leaders remain in the status quo — not out of malice, but because the status quo is familiar and comfortable.

What Kotter means by urgency: Not panic. Not artificially created time pressure. But an honest, data-driven analysis of why the current state is unsustainable. If 70% of leaders do not share the urgency, the transformation will fail — Kotter names this threshold explicitly [2].

Common mistake: Urgency is confused with a crisis presentation. A fear-driven “We must change or we will go under” does not create urgency — it creates paralysis or cynicism. Real urgency emerges from connecting market data with the personal experience of those involved: “What does this market shift mean for your area?”

Practical tip: Use customer data, competitive analyses, and market trends — but translate them into the language of those affected. A board member understands EBITDA projections. A claims processor understands “Our customers are switching to competitors because our process takes three days longer.”

Step 2: Build a Guiding Coalition

Transformation is not a one-person show. Kotter explicitly requires forming a coalition of leaders with sufficient positional power, expertise, credibility, and leadership competence to carry the transformation [2].

Critical: The coalition does not need to consist of top hierarchy — it needs to consist of the right people. A department head with high informal authority can be more valuable than a board member without operational credibility.

What most accounts omit: Kotter expressly warns against confusing this coalition with a steering committee or project organization. A steering committee has a mandate and a budget. A guiding coalition has a shared conviction. The difference: when the external consultant leaves, the guiding coalition remains — the steering committee dissolves.

Step 3: Form a Strategic Vision and Initiatives

The vision answers the question: Where do we want to go? The strategy answers: How do we get there? Kotter emphasizes that an effective vision must be explainable in five minutes — anything longer is a strategic document, not a vision [2].

Three criteria for a good transformation vision:

1. Imaginable: Those affected can concretely picture the target state
2. Desirable: The vision addresses the interests of customers, employees, and stakeholders
3. Feasible: The vision contains realistic goals — ambitious but achievable

Common mistake: The vision is written by a consultancy, approved by the board, and distributed to the organization by email. Result: nobody feels addressed. A vision not developed by the guiding coalition itself lacks emotional force.

Step 4: Enlist a Volunteer Army

Kotter renamed this step in his 2014 update Accelerate explicitly as “Enlist a Volunteer Army” — a deliberate shift from passive communication to active mobilization [4]. The vision must not only be understood but lived. This requires far more than a town-hall presentation.

Kotter’s rule of thumb: The vision is undercommunicated by a factor of 10. When you believe you have communicated it sufficiently, you are at 10% of what is needed [2].

What works: Leaders who live the vision in daily work. Stories showing what the vision concretely looks like. Dialogue formats where questions and resistance are welcome. What does not work: PowerPoint decks, intranet articles, one-off kick-off events.

Step 5: Enable Action by Removing Barriers

Even when urgency, coalition, vision, and communication are right — as long as structural barriers exist, nothing happens. Kotter identifies four typical barriers [2]:

1. Organizational structures that contradict the vision (e.g., silos preventing cross-functional collaboration)
2. Skills gaps (employees understand the vision but cannot act because necessary capabilities are missing)
3. Systems and processes that reward old behavior (e.g., bonus systems honoring individual rather than team performance)
4. Leaders who block the transformation — Kotter calls them “blockers” and recommends direct action

Connection to Force Field Analysis: Lewin’s Force Field Analysis is the ideal diagnostic tool for this step. It makes restraining forces visible and helps prioritize interventions — what Kotter describes as Step 5, Lewin systematizes as a standalone method.

Step 6: Generate Short-Term Wins

Transformation takes years. Without visible successes within the first 6-12 months, the organization loses trust in the process. Kotter defines a genuine short-term win through three criteria [2]:

1. Visible: As many employees as possible can recognize the success
2. Unambiguous: The success is not open to interpretation but measurable
3. Connected to the vision: The success is not coincidental but a direct consequence of the transformation work

Common mistake: Teams count activities as successes. “We implemented the new system” is not a success. “Processing time decreased by 30% since we implemented the new system” is a success.

Step 7: Sustain Acceleration

The most dangerous phase. Initial successes are achieved, energy is high — and precisely here lurks the trap of premature victory celebration. Kotter devotes more space to this error than any other: organizations that reduce intensity after initial successes inevitably fall back into old patterns [2].

Kotter’s recommendation: Use the credibility of initial successes to tackle larger changes. Bring new projects and new people into the guiding coalition. Increase the scope — do not decrease it.

Step 8: Institute Change

The last step is the most protracted. Culture does not change by decree but through lived experience. Kotter argues: new behaviors become culture only when the connection between the new behavior and organizational success is made explicit [2].

What cultural anchoring concretely means:

• Promotion decisions reflect the new values
• Onboarding programs teach the new ways of working
• Success stories from the transformation are actively told and passed on
• Leaders who model old behavior are not tolerated

Timeline: Cultural anchoring typically takes 3-5 years — longer than most transformation programs run. This is one of the reasons many transformations ultimately fail: the program is concluded, but the culture has not yet changed.

Empirical Critique: What the Research Says

Appelbaum et al. (2012): The Systematic Review

The most important academic review of Kotter’s model comes from Steven H. Appelbaum and colleagues, who published a four-part systematic review in the Journal of Management & Organization in 2012 [3]. Their central finding: For each individual step, there is supporting evidence from general management literature — but no study validates the model as a whole.

This means: Yes, urgency matters for change. Yes, guiding coalitions help. Yes, quick wins build momentum. But the claim that these eight steps must be followed in this sequence is not empirically established.

Three specific critiques:

1. Linearity: The model suggests a sequential progression. In practice, steps overlap, are worked on in parallel, or require backtracking. Step 1 (urgency) is not a one-time event but must be maintained throughout the entire transformation process.

2. Top-down bias: The model assumes a hierarchical organization where the guiding coalition orchestrates the change. In agile, decentralized, or self-organized structures, this governance model does not work — or only partially.

3. Missing individual level: Kotter describes what the organization should do. He does not describe what the individual person goes through. The emotional journey of those affected — fear, resistance, grief, acceptance — is not addressed. Here, the ADKAR model and the Change Curve complement what Kotter omits.

Hughes (2016): The Critique of the Anecdotal Foundation

Mark Hughes argued in 2016 that Kotter’s model is primarily based on anecdotal evidence — on Kotter’s own observations and consulting experience, not on systematic research [5]. The “over 100 companies” Kotter claims to have analyzed have never been documented as a sample: no industries, no size classes, no methodology of analysis.

What this means for practice: Kotter’s model is a valuable thinking tool — a checklist ensuring that essential aspects are not overlooked. It is not an empirically validated predictive model — following all eight steps offers no guarantee of success.

Kotter’s Update: The Dual Operating System (2014)

In 2014, Kotter himself responded to critiques of his model’s linearity and hierarchy dependence. In Accelerate, he described a “dual operating system”: alongside the existing hierarchy (which remains responsible for operational efficiency), a network of volunteer change agents operates the eight accelerators in parallel and iteratively [4].

Key differences from the original model:

Dimension	Leading Change (1996)	Accelerate (2014)
Structure	Within the hierarchy	Parallel network alongside the hierarchy
Sequence	8 sequential steps	8 parallel accelerators
Participants	Guiding coalition (select few)	Volunteer army (many)
Speed	One transformation project	Continuous acceleration
Goal	Complete the transformation	Permanent adaptability

Our assessment: The dual operating system is a significant evolution that addresses many legitimate critiques. In practice, however, it is cited and applied far less frequently than the original model — a phenomenon Kotter himself has acknowledged. Most organizations want a sequential recipe, not an emergent network.

Practical Example: Digitizing Claims Processing at an Insurer

Context: A large DACH insurance company wants to digitize its claims processing. Current state: paper-based, averaging 14 working days per claim, customer satisfaction declining. Goal: digital initial capture, automated routine cases, processing time under 5 days.

Step 1 — Establish urgency: The board presents customer survey data: 42% of customers rate claims processing as “too slow.” Three competitors have already introduced digital claims filing. NPS has dropped 12 points in 18 months. The numbers are shared not only at board level but in department meetings with claims processors — in their language.

Step 2 — Guiding coalition: The coalition consists of the claims board member, the IT director, an experienced claims processor with high informal authority, and the head of customer service. Deliberately no external consultant in the coalition — credibility comes from within.

Step 3 — Vision: “In 18 months, our customers file claims in 3 minutes via smartphone. Routine cases are closed within 48 hours. Claims processors work on complex cases that truly need their expertise — not on routine work.”

Step 4 — Communication: The claims processor from the coalition shares in team meetings what the change means for daily work. No PowerPoint, but conversations. The vision is repeated in every leadership round — not once, but over months.

Step 5 — Remove barriers: The legacy system cannot process digital initial capture. The IT department receives budget for an API interface. Claims processors receive training on the new system — during working hours, not in the evening. The bonus system is adjusted: no longer number of cases processed, but customer satisfaction and processing quality.

Step 6 — Quick wins: After 3 months: digital claims filing for auto claims is live. Initial results: processing time for routine auto claims drops from 14 to 4 days. These numbers are communicated company-wide.

Step 7 — Consolidate: The auto claims successes are used to expand digitization to household and liability claims. New team members join the coalition. The scope grows.

Step 8 — Cultural anchoring: Two years later: new claims processors learn digital claims processing as the standard in onboarding. Promotion decisions consider willingness to use digital tools. The old, paper-based process exists only for special cases.

Note: This example is illustratively constructed to demonstrate the model in a service context. The figures are based on typical industry values.

Comparison: Kotter vs. ADKAR vs. Lewin

Dimension	Kotter (8 Steps)	ADKAR (Prosci)	Lewin (3 Phases)
Level	Organization	Individual	Organization
Focus	Leadership and governance	Personal change journey	Systemic equilibrium
Strength	Comprehensive orchestration, coalition-building	Diagnoses where the individual is stuck	Simple mental model
Weakness	Ignores individual emotions	Organizational level missing	Too simple for complex transformations
Timeframe	12-36 months	Continuous, per person	Conceptual, no fixed timeframe
Evidence base	Anecdotal (Kotter), supplementarily confirmed in literature	Prosci research program (25,000+ participants)	Theoretical, Lewin (1947)
Ideal case	Large-scale transformation with clear target state	Tool rollout, process change, individual adoption	As frame overlaying other models

Our recommendation: Kotter and ADKAR are not alternatives — they are complementary. Kotter governs the organizational transformation. ADKAR ensures that individual people keep up. Those who use only Kotter lose the people. Those who use only ADKAR lose the strategic governance. More on combining them in the overview article on change management models.

5 Common Mistakes in Application

1. Creating urgency only once

Symptom: The kick-off event was convincing. Three months later, nobody remembers why the transformation was necessary.

Why this hurts: Urgency is not an event but a state. When it is not maintained, the organization returns to the comfort of the status quo.

Solution: Update the urgency message regularly with new data. Connect each step to the original urgency: “We are doing this BECAUSE…“

2. The wrong guiding coalition

Symptom: The coalition consists of people with high hierarchy but low operational credibility. Or of engaged employees without decision-making power.

Why this hurts: A coalition without credibility generates cynicism. A coalition without power generates frustration.

Solution: Check the coalition against Kotter’s four criteria: positional power, expertise, credibility, leadership competence. If one is missing, supplement the coalition.

3. Vision as slide deck instead of lived narrative

Symptom: The vision exists as a 40-page strategy document. Nobody can summarize it in one sentence.

Why this hurts: A vision that cannot be explained in five minutes is not a compass — it is bureaucracy.

Solution: Formulate the vision so you could explain it to a colleague in an elevator. If that fails, the vision is not yet clear enough.

4. Premature victory celebration

Symptom: Initial quick wins are achieved. Leadership declares the transformation complete. Budgets are cut, attention shifts to the next topic.

Why this hurts: Kotter identifies this mistake as the most common reason transformations fail [2]. Quick wins are intermediate results, not final results. Those who stop after Step 6 lose everything built in Steps 1-6.

Solution: Before the transformation begins, define what “done” means — and communicate that quick wins are milestones, not finish lines.

5. Applying the model slavishly sequentially

Symptom: The team refuses to work on Step 3 before Step 2 is “officially completed.” In reality, steps overlap.

Why this hurts: The sequential interpretation transforms a thinking tool into bureaucracy. Transformation is not waterfall planning.

Solution: Use the eight steps as a checklist, not a project plan. Work on multiple steps in parallel, but ensure none is skipped.

When Kotter Is NOT the Right Model

1. Individual behavioral change: When the bottleneck is not the organization but the individual person (e.g., during a tool rollout), the ADKAR model is better suited — it diagnoses where the individual is stuck.

2. Unknown target state: Kotter presupposes that you know where the journey is going (Step 3: vision). When the target state is genuinely unknown — in cultural transformation, in business model innovation — Theory U or explorative approaches are more appropriate.

3. Decentralized, agile organizations: The model was developed for hierarchical organizations. In self-organized structures without a classical guiding coalition, it must be adapted — or supplemented by other approaches.

4. Diagnosis before intervention: Kotter begins directly with action (create urgency). If you first want to understand which forces work for and against the change, start with Force Field Analysis — and then choose the appropriate intervention framework.

Frequently Asked Questions

What is Kotter’s 8-Step Model?

Kotter’s 8-Step Model is a change management framework describing eight sequential steps for successful organizational change: (1) Create urgency, (2) Build guiding coalition, (3) Develop vision, (4) Communicate vision, (5) Enable action, (6) Generate short-term wins, (7) Consolidate gains, (8) Anchor in culture. It was developed in 1995/96 by John P. Kotter at Harvard Business School.

What is the difference between Kotter and ADKAR?

Kotter is an organizational model (top-down, eight steps for the overall transformation). ADKAR is an individual model (five milestones for the individual person). They are complementary: Kotter governs the transformation, ADKAR measures whether individual people are keeping up. More in the comparison with the ADKAR model.

Is Kotter’s model empirically validated?

Partially. Appelbaum et al. (2012) showed in a systematic review that each individual step is supported by general management research — but the model as a whole, particularly the claimed sequence, has never been empirically validated. The model is a valuable thinking tool, not a scientifically proven recipe.

What did Kotter change in 2014?

In Accelerate (2014), Kotter replaced the sequential 8-step model with a dual operating system: the existing hierarchy remains responsible for operational efficiency, while a parallel network of volunteer change agents operates eight accelerators in parallel and iteratively. The evolution addresses critiques of linearity and top-down bias.

How long does implementation take?

Typically 12-36 months for Steps 1-7. Step 8 (cultural anchoring) can take 3-5 years. A purely structural change (new system, new process) is faster to implement than a cultural transformation. Detailed timelines can be found in the overview of change management models.

Related Methods

• ADKAR Model: When you want to supplement Kotter’s organizational perspective with the individual level — ADKAR diagnoses where individual people are stuck
• Change Curve: When you want to understand the emotional phases those affected go through — as an emotional companion alongside Kotter’s structural framework
• Force Field Analysis: When you want to diagnose which forces work for and against the change before the transformation — the diagnostic tool Kotter does not provide
• Change Management Models Compared: For the decision matrix on which framework fits which situation — and how models work together as layers
• Why Transformations Fail: The six most common failure patterns — and Kotter’s model as countermeasure

---

Research Methodology

This article synthesizes findings from Kotter’s original works (1995, 1996, 2014), the systematic review by Appelbaum et al. (2012, four parts), Hughes’ methodological critique (2016), Prosci’s comparative data, and the analysis of 12 German-language publications on the 8-step model.

Limitations: The practical example (insurance claims digitization) is illustratively constructed, not a documented case study. The empirical literature on Kotter’s model is predominantly conceptual — controlled studies on the effectiveness of the overall model are lacking.

Disclosure

SI Labs accompanies organizations through transformation processes. We use elements of Kotter’s model in combination with other change frameworks, particularly in the strategic governance of service transformations. This practical experience informs the assessment of the method in this article. Readers should be aware of potential perspective bias.

References

[1] Kotter, John P. “Leading Change: Why Transformation Efforts Fail.” Harvard Business Review 73, no. 2 (1995): 59-67. [HBR Article | Foundational Work | Citations: 12,000+ | Quality: 85/100]

[2] Kotter, John P. Leading Change. Boston: Harvard Business School Press, 1996. ISBN: 978-0875847474 [Monograph | Foundational Work | Citations: 20,000+ | Quality: 82/100]

[3] Appelbaum, Steven H., Sally Habashy, Jean-Luc Malo, and Hisham Shafiq. “Back to the future: revisiting Kotter’s 1996 change model.” Journal of Management Development 31, no. 8 (2012): 764-782. DOI: 10.1108/02621711211253231 [Systematic Review | 4-part | Citations: 800+ | Quality: 80/100]

[4] Kotter, John P. Accelerate: Building Strategic Agility for a Faster-Moving World. Boston: Harvard Business Review Press, 2014. ISBN: 978-1625271747 [Monograph | Update of Original Model | Citations: 1,500+ | Quality: 78/100]

[5] Hughes, Mark. “Leading changes: Why transformation explanations fail.” Leadership 12, no. 4 (2016): 449-469. DOI: 10.1177/1742715015571393 [Journal Article | Methodological Critique | Citations: 300+ | Quality: 75/100]

[6] Hiatt, Jeff. ADKAR: A Model for Change in Business, Government and Our Community. Fort Collins: Prosci, 2006. ISBN: 978-1930885509 [Monograph | ADKAR Foundation | Citations: 2,000+ | Quality: 72/100]

[7] Lewin, Kurt. “Frontiers in Group Dynamics.” Human Relations 1, no. 1 (1947): 5-41. DOI: 10.1177/001872674700100103 [Journal Article | Foundational Work | Citations: 8,000+ | Quality: 90/100]