What makes Kotter's 8-Step Change Model notable?

1.2K downloads. Trust evidence available

How should Kotter's 8-Step Change Model be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Kotter's 8-Step Change Model

Activate when: user says 'our change initiative is stalling', 'people aren't adopting the new way', 'we launched the transformation but nothing changed', 'ho... Skill: Kotter's 8-Step Change Model Owner: deciqai Summary: Activate when: user says 'our change initiative is stalling', 'people aren't adopting the new way', 'we launched the transformation but nothing changed', 'ho... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:04:13.055Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/kotter-change.json) v1.0.4 | 2026-07-09T11:18

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.0.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.5release · observed Jul 16, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:kotter-change

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/snapshot"

Documentation

CLAWHUB

111,574 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: kotter-change
description: "Activate when: user says 'our change initiative is stalling', 'people aren't adopting the new way', 'we launched the transformation but nothing changed', 'how do we overcome resistance to change', 'why do transformation efforts fail', or asks how to sequence or diagnose a planned organizational change.
Do NOT activate when: the change is a small process improvement in a stable team (use PDCA instead), or the situation is a crisis requiring immediate command-and-control response. More: deciqai.com/c/kotter-change"
---

# Kotter's 8-Step Change Model

## Overview

John Kotter built this model from studying one hundred corporate transformations — most failed. Core finding: failures stem from eight predictable leadership errors, each defeated by one of the eight steps. Skipping steps creates only the illusion of speed. The 2014 *Accelerate* update introduced a Dual Operating System for parallel execution in high-velocity environments.

Composes with: `okr-goal-setting` inside Steps 3 and 6; `feedback-loops` throughout Steps 6–7; `situational-leadership` for individual-level management at each step.

## When to Use

- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing
- Transformation is stalling — diagnose which step was skipped
- Resistance is significant and needs a structured approach
- Someone says "nobody's buying in", "we went back to old ways", "the rollout failed"
- AI adoption is stalling — copilots/AI tools bought but under-used, pilots not scaling, ROI on AI capex unclear, or middle managers quietly resisting AI-native ways of working against AI-native competition

**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** user has a specific transformation → run The Process directly.
- **Coach mode:** user is unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.
2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.
3. Elicit the real situation: what is changing, what org, what is the current resistance level?
> **[WAIT — do not advance until user responds]**
4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.
> **[WAIT — do not advance until user responds]**
5. Close by naming which failure mode is highest-risk and which step defeats it.
> **[WAIT — do not advance until user responds]**

## The Process

**Pre-diagnostic — score eight failure modes (1–5):**

| Failure mode | Risk |
|---|---|
| Complacency / no urgency felt | /5 |
| Weak coalition — key influencers uncommitted | /5 |
| Abse

_meta.json

{
  "ownerId": "kn754b8sk22s8c6gjxt02bftbn88q7ye",
  "slug": "kotter-change",
  "version": "1.0.5",
  "publishedAt": 1784225053055
}

references/sources.md

# Sources — kotter-change

> *Primary sources for the [kotter-change](../SKILL.md) skill.*

- Kotter, J.P. (1995). "Leading Change: Why Transformation Efforts Fail." *Harvard Business Review*, 73(2), 59-67. One of HBR's most widely reprinted articles; the foundational diagnosis of the eight failure modes. https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2
- Kotter, J.P. (1996). *Leading Change.* Harvard Business School Press. The book-length treatment; contains the urgency quote and the full eight-step framework with detailed case studies. ISBN 978-0875847474.
- Kotter, J.P. (2014). *Accelerate: Building Strategic Agility for a Faster-Moving World.* Harvard Business Review Press. The Dual Operating System update; makes the eight steps compatible with agile organizational structures. ISBN 978-1625271747.
- Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness. The primary-source account of the IBM transformation — a documented case of Kotter's eight steps in sequential practice. ISBN 978-0060523800.
- Kotter, J.P. & Cohen, D.S. (2002). *The Heart of Change.* Harvard Business School Press. Contains primary case material from eight-step implementations across industries; the companion to *Leading Change* with practitioner detail. ISBN 978-1578512546.

**Contemporary context (2024–2026 enterprise AI adoption):**
- McKinsey & Company. *The State of AI* (annual global survey; 2024 and 2025 editions). Widely cited industry source documenting that generative-AI adoption rose sharply while measurable enterprise-wide bottom-line impact lagged, with organizational barriers cited as a leading obstacle to scaling. https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai
- MIT Sloan Management Review / Boston Consulting Group, ongoing "AI and the workforce" research (2024–2025). Reporting on the persistent gap between AI tool deployment and realized value, emphasizing change-management, workflow-redesign, and middle-management adoption as the binding constraints rather than model capability. https://sloanreview.mit.edu/

**What is not cited and why:** Claims that "70% of change initiatives fail" are frequently attributed to Kotter but appear in popularized summaries, not in Kotter's primary research documents. The claim is plausible given the patterns Kotter documented, but the specific percentage is not sourced in his primary works. This skill does not cite that statistic. The IBM transformation numbers are sourced to Gerstner's memoir (primary source), not to secondary accounts.

examples/enterprise-ai-adoption-2024-2026.md

# Method in Action: Driving Enterprise AI Adoption (2024–2026)

> *Example for the [kotter-change](../SKILL.md) skill.*

By 2024–2026, most large enterprises had bought AI tools — copilots, assistants, internal chatbots, and workflow automation — but adoption frequently stalled at the pilot stage. A widely reported pattern emerged: seat licenses were paid for but lightly used, pilots proliferated without scaling into production, and returns on heavy AI capital spending were hard to demonstrate. A recurring, under-named cause was quiet resistance from middle managers, whose roles, headcount justifications, and control over process were most directly threatened by AI-native ways of working. This example walks a generic large-enterprise AI transformation through Kotter's eight steps.

**Pre-diagnostic (highest-risk failure modes for AI transformations):**
- *Complacency / no urgency* — often HIGH: "we already bought licenses, we're doing AI."
- *Obstacles not removed* — often HIGH (this is the Digital/AI pack's flagged step): legacy metrics, security review, procurement, and data-access rules block new ways of working.
- *No short-term wins* — often HIGH: pilots are measured on activity, not business outcomes.

**Step 1 (urgency):** Announcing "we're an AI company now" at a town hall does not create urgency. Urgency here comes from sustained external evidence: AI-native competitors shipping faster with smaller teams, and the concrete cost of inaction. The gate — 75%+ of leadership genuinely believing the status quo is dangerous — is failed when leaders treat AI as an IT procurement line rather than a competitive threat. Monthly reviews of competitor velocity and internal usage data sustain urgency far better than a single kickoff.

**Step 2 (guiding coalition):** The most common failure is staffing the coalition entirely with the CIO's office and a few executives. That coalition cannot move the middle of the organization — precisely where resistance lives. The fix per the model: recruit 2–3 informal influencers who are *not* VPs — a respected senior engineer, a trusted operations lead, a long-tenured frontline manager who has genuinely adopted the tools. Their credibility reaches the resistant middle-management layer that a top-down coalition cannot.

**Step 3 (vision):** "Become an AI-first enterprise" fails the 30-second front-line test — it is a slogan, not something a frontline worker can act on. A workable vision is concrete and imaginable: e.g., "every customer request gets a first draft answer in minutes, and our people spend their time on judgment, not retrieval." Crucially, an adoption vision must address the middle-manager fear directly — reframing AI as augmenting the manager's team output rather than as a headcount-reduction program, or resistance hardens.

**Step 4 (communicate):** Leaders typically under-communicate an AI shift by roughly an order of magnitude, and silence is read as a threat — especially by managers wondering whether

examples/ibm-turnaround-lou-gerstner-1993-1996.md

# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)

> *Example for the [kotter-change](../SKILL.md) skill.*

In 1993, IBM reported a net loss of $8 billion — the largest in US corporate history at the time. The company had missed the shift from mainframes to distributed computing. Multiple analysts recommended breaking IBM into separate units. Lou Gerstner was appointed CEO from outside the technology industry — the first outsider in IBM's history.

Kotter's eight steps applied to Gerstner's turnaround:

**Step 1 (urgency):** Gerstner refused to publish a five-year strategic plan for the first six months — famously saying "the last thing IBM needs right now is a vision." Instead he forced the organization to absorb the real financial numbers: 35,000 layoffs in 1993, public acknowledgment of the full loss, and direct customer communication. The urgency was built from *evidence*, not rhetoric.

**Step 2 (coalition):** Gerstner brought in an outsider CFO and CMO, deliberately breaking IBM's "only-from-within" promotion tradition. The new coalition had market credibility that internal promotees lacked; its presence forced the organization to accept that the old rules had changed.

**Steps 3 and 4 (vision and communication):** By late 1993, Gerstner established "IBM will not be broken up; IBM will pivot to services" as the vision. He communicated it through extensive external appearances (analysts, customers, media) and internal road shows personally covering over 100,000 employees.

**Step 5 (remove obstacles):** The main structural obstacles were IBM's internal silos — business units acting as independent competitors. Gerstner imposed cross-unit integration and eliminated unit-level profit measures that incentivized internal competition. This was organizationally painful and required several senior departures.

**Step 6 (short-term wins):** IBM returned to profit in 1994 — one year after Gerstner's arrival. IBM Global Services (then a new unit) was cited as a specific win: from near-zero to $30B in revenue by 1999, demonstrating that the services pivot was real.

**Step 7 (consolidate):** Rather than celebrating the 1994 return to profit as completion, Gerstner used it to accelerate the services buildout, acquire Lotus (1995) and Tivoli (1996), and push deeper organizational integration.

**Step 8 (culture):** Gerstner's memoirs (*Who Says Elephants Can't Dance?*, 2002) document the most difficult step: changing IBM's "we are never wrong and never in trouble" cultural assumption. This required five years of sustained demonstration that the new behaviors produced better results, plus systematic changes to promotion criteria (results over tenure) and hiring (market-facing skills prized).

**Results:** IBM's market capitalization recovered from approximately $30B in 1993 to approximately $160B at Gerstner's departure in 2002. IBM Global Services became the world's largest IT services firm.

Primary source: Gerstner, L.V. (2002). *Who S

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.