Kotter

Kotter's 8-Step Change Model

Why 70% of Change Efforts Fail — 8 Common Errors

John Kotter's research at Harvard Business School identified that 70% of organizational change initiatives fail. The root causes trace to eight predictable errors:

| # | Error (실패 원인) | Consequence | |---|---|---| | 1 | Allowing too much complacency (현상 안주 허용) | No one feels the need to change | | 2 | Failing to create a powerful guiding coalition (추진력 있는 연합 부재) | Change has no political or organizational muscle | | 3 | Underestimating the power of vision (비전의 힘 과소평가) | Direction unclear, people confused or resistant | | 4 | Under-communicating the vision (비전 소통 부족) | Even a good vision dies if people don't hear it repeatedly | | 5 | Permitting obstacles to block the vision (장애물 방치) | Structural, systemic, or human barriers kill momentum | | 6 | Failing to create short-term wins (단기 성과 미창출) | People lose faith — "this isn't working" | | 7 | Declaring victory too soon (너무 이른 승리 선언) | Regression to old habits; change doesn't stick | | 8 | Neglecting to anchor in culture (문화 정착 실패) | New behaviors evaporate when pressure is off |

> Key insight: These errors are sequential. Skipping early steps or rushing later ones produces the same result — failure.

---

The 8 Steps — Overview

  ┌─────────────────────────────────────────────────────┐
  │          KOTTER'S 8-STEP CHANGE MODEL               │
  │                                                     │
  │  Step 8 ──▶ 🏛️  Institute Change (변화의 제도화)     │
  │       ▲                                             │
  │  Step 7 ──▶ 🚀 Sustain Acceleration (가속화 유지)    │
  │       ▲                                             │
  │  Step 6 ──▶ 🏆 Generate Short-term Wins (단기 성과)  │
  │       ▲                                             │
  │  Step 5 ──▶ 🔓 Enable Action (장애물 제거)           │
  │       ▲                                             │
  │  Step 4 ──▶ 🙋 Enlist Volunteer Army (자발적 참여)   │
  │       ▲                                             │
  │  Step 3 ──▶ 🔭 Form Strategic Vision (비전 수립)     │
  │       ▲                                             │
  │  Step 2 ──▶ 🤝 Build Guiding Coalition (추진팀 구성) │
  │       ▲                                             │
  │  Step 1 ──▶ 🔥 Create Urgency (위기감 조성)          │
  └─────────────────────────────────────────────────────┘

  ◀── CREATE CLIMATE ──▶◀── ENGAGE & ENABLE ──▶◀── IMPLEMENT & SUSTAIN ──▶
       (Steps 1-3)            (Steps 4-5)            (Steps 6-8)

---

Step-by-Step Deep Dive

🔥 Step 1: Create Urgency (위기감 조성)

What to do:

• Examine market and competitive realities for threats and opportunities
• Identify and discuss crises, potential crises, or major opportunities
• Make the status quo more dangerous than the unknown
• Aim for 75%+ of leadership genuinely convinced change is necessary

Pitfalls:

• Paralysis from fear vs. productive urgency — urgency is NOT anxiety
• Over-relying on data alone; stories and experiences create visceral urgency
• Confusing false urgency (busy, frantic activity) with true urgency (focused determination)

Success indicators:

• People voluntarily start conversations about the need to change
• Meetings shift from "should we change?" to "how do we change?"
• Complacency-reinforcing behaviors (e.g., denying problems) decrease visibly

Diagnostic questions:

• What happens if we do nothing for 12 months?
• Can we quantify the cost of the status quo?
• Who are the most complacent stakeholders and what would convince them?
• Is our urgency based on fear (fragile) or opportunity (durable)?

---

🤝 Step 2: Build Guiding Coalition (변화추진팀 구성)

What to do:

• Assemble a group with enough power, expertise, credibility, and leadership to drive change
• Include people from different levels and departments — not just the C-suite
• Build trust within the coalition through off-site events, honest dialogue, and shared purpose
• Ensure the coalition operates outside the normal hierarchy

Pitfalls:

• Excluding key influencers (especially informal leaders)
• Coalition too homogeneous — lacks diverse perspectives
• Relying on authority alone instead of trust and shared commitment
• CEO tries to lead alone without a real coalition

Success indicators:

• Coalition members actively champion the change in their own areas
• The group can make decisions and act without constant executive approval
• Skeptics and resisters are engaged, not excluded
• Coalition has emotional commitment, not just intellectual agreement

Diagnostic questions:

• Does our coalition include people others trust and follow?
• Are all critical functions and levels represented?
• Can this group drive change even if the CEO is unavailable for a week?
• Is anyone on the coalition there out of obligation rather than conviction?

---

🔭 Step 3: Form Strategic Vision (전략적 비전 수립)

What to do:

• Create a clear, compelling vision of the future state
• Develop strategies to achieve that vision
• The vision must be: imaginable, desirable, feasible, focused, flexible, communicable
• Test: can you explain the vision in 5 minutes and get understanding AND interest?

Pitfalls:

• Vision too vague ("be the best") or too complex (50-page document)
• Confusing a vision with a plan — vision is the destination, strategy is the route
• Vision created by consultants, not owned by the coalition
• Vision doesn't connect emotionally; only appeals to logic

Success indicators:

• Anyone in the organization can articulate the vision in their own words
• People can see how their daily work connects to the vision
• The vision creates genuine excitement, not just compliance
• Strategies are clear enough to guide decision-making at all levels

Diagnostic questions:

• Can we state the vision in under 60 seconds?
• Does the vision answer "why should I care?" for frontline employees?
• Is the vision aspirational enough to inspire but realistic enough to believe?
• Does everyone on the guiding coalition describe the same vision?

---

🙋 Step 4: Enlist Volunteer Army (자발적 참여 유도)

What to do:

• Communicate the vision relentlessly — 10x more than you think necessary
• Use every channel: meetings, memos, hallway conversations, town halls
• Lead by example — leadership behavior must embody the vision
• Address concerns and anxiety honestly; two-way communication, not broadcast
• The goal is a large-scale, voluntary movement — not a mandate

Pitfalls:

• Under-communicating by a factor of 10 (or 100)
• Saying one thing but doing another — kills credibility instantly
• Relying on a single announcement or email
• Ignoring or dismissing questions and pushback

Success indicators:

• People explain the change vision to their peers (viral spread)
• Voluntary advocates emerge at every level
• Resistance is acknowledged and addressed, not suppressed
• Leadership walk-the-talk is visible and consistent

Diagnostic questions:

• How many times has each employee heard the vision this month?
• Are leaders modeling the change in their own behavior?
• What are the top 3 concerns employees have? Are we addressing them?
• Is participation in change activities voluntary or coerced?

---

🔓 Step 5: Enable Action by Removing Barriers (장애물 제거)

What to do:

• Remove structural barriers: org charts, job descriptions, compensation systems
• Address misaligned systems: performance reviews, information systems
• Confront managers who undermine the change — the biggest barrier is often people
• Provide training and resources needed to act on the vision
• Empower broad-based action — let people experiment and take risks

Pitfalls:

• Trying to remove every barrier at once instead of prioritizing
• Ignoring the "boss barrier" — a powerful resistor who blocks their whole area
• Changing structures without changing people's skills
• Risk-averse culture punishes experiments and mistakes

Success indicators:

• People feel empowered to try new approaches without asking permission
• Structural and systemic obstacles are visibly being removed
• Change resisters are either converted or moved to non-blocking roles
• Training and resources are available and used

Diagnostic questions:

• What are the top 3 structural barriers slowing the change?
• Which individuals are actively or passively blocking progress?
• Do our compensation and promotion systems reward the new behaviors?
• Are people afraid to experiment? If so, why?

---

🏆 Step 6: Generate Short-term Wins (단기 성과 창출)

What to do:

• Plan for visible, unambiguous performance improvements within 6-18 months
• Create those wins — don't just hope for them; engineer them deliberately
• Recognize and reward people who made the wins possible
• Use wins to validate the vision and strategies
• Build momentum and undermine cynics

Pitfalls:

• Leaving short-term wins to chance
• Wins that are ambiguous — skeptics can explain them away
• Not connecting wins to the change effort explicitly
• Too few wins or wins that only leadership sees

Success indicators:

• Multiple, visible, clearly change-related wins within 6-18 months
• Cynics and fence-sitters start joining the effort
• The wins prove the vision is achievable and worth the effort
• Each win builds confidence for the next, bigger challenge

Diagnostic questions:

• What wins can we achieve in the next 90 days?
• Are the wins visible to the broader organization or just to leadership?
• Can skeptics attribute these wins to something other than the change effort?
• Are we celebrating wins and the people behind them?

---

🚀 Step 7: Sustain Acceleration (가속화 유지)

What to do:

• Use credibility from early wins to tackle bigger, harder changes
• Don't let up — keep the urgency high even after early wins
• Launch new change projects, bring in additional people, expand scope
• Senior leadership stays focused on clarity and momentum
• Continuously identify and remove barriers as they emerge

Pitfalls:

• Declaring victory after the first wins (the #1 mistake at this stage)
• Letting urgency drop as "change fatigue" sets in
• Failing to tackle the deeper, systemic issues that require more effort
• Over-relying on the original coalition without bringing in new energy

Success indicators:

• More and harder changes are being tackled, not fewer
• Urgency remains high; the organization hasn't relaxed
• New leaders emerge to drive change in additional areas
• Interdependencies between change projects are managed

Diagnostic questions:

• Have we started the harder, deeper changes or are we resting on early wins?
• Is urgency still high or is the organization becoming complacent again?
• Are we bringing new people into the change effort?
• What systemic issues remain untouched?

---

🏛️ Step 8: Institute Change (변화의 제도화)

What to do:

• Articulate the connection between new behaviors and organizational success
• Embed changes into: hiring, onboarding, promotion, performance systems
• Ensure leadership succession reinforces the change
• Create new cultural norms and shared values
• The change is "done" only when it's "how we do things here"

Pitfalls:

• Assuming culture changes automatically after behavior changes
• Neglecting to update HR systems, processes, and rituals
• Leadership succession puts someone in charge who doesn't embody the change
• Removing the supporting infrastructure too soon

Success indicators:

• New employees learn the new way as "normal" — they never knew the old way
• The change persists without the original champion pushing it
• Promotion and hiring criteria reflect the new culture
• People can't imagine going back to the old way

Diagnostic questions:

• Would this change survive if the CEO left tomorrow?
• Do our hiring and onboarding processes reflect the new culture?
• Can a new employee learn our changed way without anyone explaining the history?
• Have we updated performance reviews, rituals, and symbols?

---

Kotter's Accelerate (2014 Update): Dual Operating System

In his 2014 book Accelerate, Kotter evolved the model to address the speed of modern change:

  ┌──────────────────────────────────────────────────────────┐
  │              DUAL OPERATING SYSTEM                       │
  │                                                          │
  │   HIERARCHY (관리 체계)          NETWORK (혁신 네트워크)    │
  │   ┌──────────────┐            ┌──────────────┐          │
  │   │  Reliability  │    ◀══▶   │  Agility      │          │
  │   │  Efficiency   │           │  Speed        │          │
  │   │  Optimization │           │  Innovation   │          │
  │   │  Structure    │           │  Opportunity  │          │
  │   └──────────────┘            └──────────────┘          │
  │                                                          │
  │   Runs the business             Changes the business     │
  │   (일상 운영)                    (변화 추진)               │
  │                                                          │
  │   Key: Both systems work TOGETHER, not in opposition     │
  └──────────────────────────────────────────────────────────┘

5 Principles of the Accelerate model:

1. Many change agents, not just the usual few — the network draws volunteers from across the hierarchy
2. A want-to, not a have-to mentality — people join voluntarily because they see the opportunity
3. Head AND heart, not just head — urgency plus emotional commitment
4. Much more leadership, not just more management — the network side is leadership-driven
5. Two systems, one organization — the hierarchy and network are inseparable, not a replacement

When to use the Dual Operating System:

• Change is continuous, not a one-time event
• The environment shifts faster than the hierarchy can adapt
• You need innovation AND operational excellence simultaneously
• Traditional project management approaches are too slow

---

Comparison with Other Change Models

Kotter vs. Lewin vs. ADKAR

| Dimension | Kotter (8 Steps) | Lewin (3 Stages) | ADKAR (Prosci) | |---|---|---|---| | Focus | Leadership-driven transformation | Force-field dynamics | Individual change journey | | Unit of change | Organization | Group/System | Individual person | | Phases | 8 sequential steps | Unfreeze → Change → Refreeze | Awareness → Desire → Knowledge → Ability → Reinforcement | | Strengths | Actionable, addresses politics, urgency focus | Simple, intuitive, reveals barriers | Measurable per-person progress, gap analysis | | Weaknesses | Linear assumption, less individual focus | Oversimplified, "refreeze" feels rigid | Doesn't address power, politics, coalition | | Best for | Large-scale org transformation | Understanding resistance | Training rollouts, tech adoption | | Typical duration | 12-36 months | Varies | 3-18 months per initiative | | Korean summary | 리더십 중심 대규모 변혁 | 힘의 균형 분석 | 개인별 변화 여정 |

When to Use Which

• Use Kotter when: The change is strategic, large-scale, requires coalition-building, involves culture shift
• Use Lewin when: You need to analyze forces for/against change, understand resistance, simple framing for teams
• Use ADKAR when: You need to track individual adoption, the change is more tactical (new system, new process), or you need to identify exactly where individuals are stuck
• Combine them: Kotter for overall strategy + ADKAR for individual tracking = powerful combination

---

Change Readiness Assessment Checklist

Rate each item 1 (strongly disagree) to 5 (strongly agree):

📋 Urgency & Need (위기감과 필요성)

• [ ] There is a widely shared understanding of why change is needed
• [ ] The cost of NOT changing is clear and quantified
• [ ] Leaders talk about the need for change regularly and authentically
• [ ] External pressures (market, competition, regulation) reinforce the urgency

📋 Leadership & Coalition (리더십과 추진팀)

• [ ] A credi

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: ironyjk
• Source: ironyjk/strategy-frameworks
• License: MIT

Install and usage instructions live in the source repository linked above.