{"id":"d8da6341-8805-442b-b61f-e2fe786254a3","entityType":"agent","slug":"clawhub-deciqai-kotter-change","name":"Kotter's 8-Step Change Model","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-kotter-change","canonicalPath":"/agent/clawhub-deciqai-kotter-change","generatedAt":"2026-10-11T07:41:49.983Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T04:34:54.825Z","emptyReason":null},"description":"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","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:kotter-change","sourceUrl":"https://clawhub.ai/deciqai/kotter-change","homepage":"https://clawhub.ai/deciqai/skills/kotter-change","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/kotter-change","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/kotter-change","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: user says 'our change initiative is stalling', 'people aren't adopting the new way', 'we launched the transformation but nothing changed', 'ho..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:34:54.825Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:34:54.825Z","emptyReason":null},"stars":null,"forks":null,"downloads":1158,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:34:54.757Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T04:34:54.825Z","lastCrawledAt":"2026-10-11T04:34:54.757Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T04:34:54.757Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T18:04:13.055Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/kotter-change.json)","fileCount":6,"zipByteSize":12588},{"version":"1.0.4","createdAt":"2026-07-09T11:18:37.700Z","changelog":"Refresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)","fileCount":6,"zipByteSize":12266},{"version":"1.0.3","createdAt":"2026-07-08T11:07:07.536Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":8397},{"version":"1.0.2","createdAt":"2026-07-08T00:51:54.652Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":8358},{"version":"1.0.1","createdAt":"2026-07-07T22:28:02.188Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8484},{"version":"1.0.0","createdAt":"2026-06-29T09:17:40.258Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8296}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:kotter-change","setupComplexity":"low","setupSteps":["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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:41:49.980Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-kotter-change/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T04:34:54.825Z","emptyReason":null},"readme":"Skill: Kotter's 8-Step Change Model\n\nOwner: deciqai\n\nSummary: Activate when: user says 'our change initiative is stalling', 'people aren't adopting the new way', 'we launched the transformation but nothing changed', 'ho...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T18:04:13.055Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/kotter-change.json)\n\nv1.0.4 | 2026-07-09T11:18:37.700Z | user\n\nRefresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)\n\nv1.0.3 | 2026-07-08T11:07:07.536Z | user\n\nFooter now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:51:54.652Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T22:28:02.188Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-06-29T09:17:40.258Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 12588 bytes\n\nFiles: examples/enterprise-ai-adoption-2024-2026.md (6679b), examples/ibm-turnaround-lou-gerstner-1993-1996.md (3091b), references/sources.md (2618b), skill-card.md (2513b), SKILL.md (8710b), _meta.json (132b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: kotter-change\ndescription: \"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.\n  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\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: `okr-goal-setting` inside Steps 3 and 6; `feedback-loops` throughout Steps 6–7; `situational-leadership` for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n- 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\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Absent or unclear vision | /5 |\n| Under-communication | /5 |\n| Obstacles not removed | /5 |\n| No short-term wins | /5 |\n| Premature victory declared | /5 |\n| Not anchored in culture | /5 |\n\nScores 4–5 require pre-treatment before the corresponding step.\n\n**Steps 1–8 (each has a gate):**\n1. **Urgency** — import external data; make cost of inaction concrete. Gate: 75%+ of leadership believes change is necessary.\n2. **Guiding coalition** — needs positional power + expertise + credibility + leadership; map on influence × stance 2×2. Gate: 2–3 informal influencers (non-VP).\n3. **Vision** — 30-second elevator test; six attributes: imaginable, desirable, feasible, focused, flexible, communicable. Gate: passes five-audience test.\n4. **Communicate** — embed vision in every forum, review, conversation. Gate: random sampling confirms employees can repeat vision accurately.\n5. **Remove obstacles** — eliminate structural, process, and personal blockers. Gate: 3 specific blockers identified and removed.\n6. **Short-term wins** — planned, unambiguous business outcomes in 12–24 months. Gate: one win defined and dated at launch.\n7. **Consolidate** — use win credibility to tackle larger obstacles; don't disband the change team. Stop-rule: wins must trace causally to new ways of working.\n8. **Anchor in culture** — four mechanisms: hiring, promotion, onboarding, KPI criteria. Gate: new hire 2 years later experiences new ways as default.\n\n**Output:** `# Change Readiness: <initiative> / Failure mode scores (table) / 8-Step Roadmap (one line per step) / Timeline (24-month milestones)`\n\n*→ Method in Action: [IBM's Turnaround under Lou Gerstner (1993–1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)*\n*→ 2026 lens: [Driving Enterprise AI Adoption (2024–2026)](examples/enterprise-ai-adoption-2024-2026.md)*\n\n## Change-Type Packs\n\n- **Digital/AI:** Step 5 most underinvested — legacy metrics, procurement, and security processes block new ways of working.\n- **Post-merger:** Step 2 highest-risk — coalition must span both entities; Step 6 wins must be jointly owned.\n- **Startup scaling (A–C):** Step 8 most skipped — informal culture breaks at 25→150 people; formal anchoring feels premature but is essential.\n\n## Applying It Well\n\n- Urgency requires sustained evidence exposure, not a one-time announcement; monthly data reviews maintain it longer than any kick-off.\n- Coalition fails by being homogeneous — informal influencers (respected ICs, long-tenured peers) outperform additional VPs.\n- Short-term wins must be defined, measured, and dated at launch — retrospective wins have reduced motivational power.\n- Communication almost always falls short — multiply planned volume by 10; silence is interpreted as reversal.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We announced at the all-hands — it's launched\" | Announcing does not create urgency. Until 75%+ of leadership believes status quo is dangerous, transformation has not started. |\n| [D] \"The guiding coalition is our executive committee\" | Executive committees lack informal credibility. A coalition without informal influencers cannot move the middle of the organization. |\n| [D] \"Our vision is to become the best-in-class provider\" | Not imaginable, not specific, not communicable in 30 seconds. A vision a front-line employee cannot state is a slogan. |\n| [D] \"We communicated at every town hall for three months\" | Likely 5–10% of the volume needed. Leaders underestimate the communication deficit by a factor of 10. |\n| [D] \"The pilot succeeded so rollout will follow naturally\" | Pilot = Step 6 win. Without Steps 7–8, the change team disperses and the org reverts. |\n| [D] \"Culture will follow the process changes\" | Culture follows demonstrated performance improvement with an explicit causal link — not process changes alone. |\n| [D] \"We'll generate quick wins as we go\" | Wins need a definition, measurement system, and celebration mechanism built in at launch. Unplanned wins are weaker. |\n| [D] \"People know it's a priority — no need to put it in reviews\" | Priorities not in performance criteria are cultural wishes, not institutional commitments. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- No pre-diagnostic; coalition is all formal reports to the sponsor; vision unknown to front-line employees 30 days after launch; no win defined or dated at launch; initiative declared complete after first win without Step 8 testing.\n\n## Verification\n\n- [ ] Pre-diagnostic completed (all eight failure modes scored); 75%+ of leadership verified as genuinely sensing urgency\n- [ ] Coalition includes 2+ informal influencers (non-VP); vision passes 30-second front-line test\n- [ ] 3 specific structural obstacles eliminated; 1 short-term win defined, dated, and in the roadmap at launch\n- [ ] Step 8 anchoring mechanisms named (hiring / promotion / onboarding / KPI); stop-rule applied to Step 7\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/kotter-change** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/kotter-change.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784225053055\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**Contemporary context (2024–2026 enterprise AI adoption):**\n- 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\n- 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/\n\n**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.\n\nFile v1.0.5:examples/enterprise-ai-adoption-2024-2026.md\n\n# Method in Action: Driving Enterprise AI Adoption (2024–2026)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nBy 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.\n\n**Pre-diagnostic (highest-risk failure modes for AI transformations):**\n- *Complacency / no urgency* — often HIGH: \"we already bought licenses, we're doing AI.\"\n- *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.\n- *No short-term wins* — often HIGH: pilots are measured on activity, not business outcomes.\n\n**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.\n\n**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.\n\n**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.\n\n**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 the initiative targets their jobs. The vision must be repeated in every forum, review, and one-on-one. The gate: random sampling confirms employees — including skeptical managers — can accurately restate what the change is *and is not*.\n\n**Step 5 (remove obstacles):** For AI this is the most underinvested step and the one where middle-manager resistance becomes structural rather than merely attitudinal. Blockers to identify and remove: data-access and security review processes that make AI tools unusable on real work; procurement cycles that stall integration; and — most importantly — performance metrics and incentives that reward the old way. If a manager is still measured on headcount managed or hours logged rather than outcomes delivered, they are structurally incentivized to resist. The gate requires three specific blockers removed, not a general \"we support AI\" statement.\n\n**Step 6 (short-term wins):** Pilots measured on \"number of users onboarded\" are activity, not wins. Define one unambiguous business outcome, dated at launch — e.g., a specific team cutting cycle time on a real workflow by a target percentage within two quarters, with the measurement system built in beforehand. The win should ideally be owned by a *previously skeptical* team, so its credibility travels to the resistant middle.\n\n**Step 7 (consolidate):** The classic AI-adoption error is declaring victory when a pilot succeeds. A successful pilot is a Step 6 win, not completion — disband the change team and the organization reverts to old workflows. Instead, use the win's credibility to attack the larger obstacles from Step 5 (the incentive and process changes), and hold the stop-rule: wins must trace causally to the new ways of working, not to a motivated pilot team's extra effort.\n\n**Step 8 (anchor in culture):** AI adoption becomes permanent only when it is embedded in the four mechanisms — hiring (AI-fluency in job criteria), promotion (rewarding managers who redesign work around AI, not those who protect legacy processes), onboarding (new joiners learn the AI-native workflow as the default), and KPIs (outcome metrics replace activity metrics). The test: a person who joins two years later experiences the AI-augmented way as simply \"how we work here.\" Until managers are promoted for it rather than despite it, the transformation remains a wish.\n\n**Why middle managers resist, in Kotter terms:** the resistance is not irrational. It concentrates at the exact points the model flags — Step 2 (they are the un-recruited middle), Step 5 (their incentives still reward the old way), and Step 8 (promotion criteria have not changed). Treating it as an attitude problem to be overcome with more town halls (Step 4 alone) is the predictable error; the model locates it as a coalition, obstacle, and anchoring problem.\n\n*Sources: Kotter, J.P. (1996). *Leading Change.* Harvard Business School Press (ISBN 978-0875847474) — the eight-step framework and the Digital/AI-relevant emphasis on urgency, coalition, obstacle removal, and cultural anchoring. Kotter, J.P. (1995). \"Leading Change: Why Transformation Efforts Fail.\" *Harvard Business Review*, 73(2). https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2 — the eight failure modes. The 2024–2026 enterprise-AI adoption pattern (pilots stalling, under-used licenses, difficulty demonstrating ROI on AI spending, and organizational rather than purely technical barriers) is drawn from widely reported industry surveys and reporting on generative-AI adoption in that period; specific figures are omitted here to avoid overstating any single source.*\n\nFile v1.0.5:examples/ibm-turnaround-lou-gerstner-1993-1996.md\n\n# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nGuides agents through Kotter's 8-Step Change Model to diagnose stalled organizational change and produce a change-readiness assessment, roadmap, and timeline.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, managers, and organizational-change practitioners use this skill to plan, diagnose, and sequence planned transformations such as digital adoption, cultural shifts, process redesigns, and merger integration.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill may influence organizational planning decisions without enough local context.\n\nMitigation: Treat recommendations as a structured framework for review with leaders, stakeholders, and organization-specific evidence before changing teams, incentives, or processes.\n\nRisk: The framework can be misapplied to small improvements, very small organizations, or urgent crises where the artifact says it is not a fit.\n\nMitigation: Check fit before using the roadmap; use a lighter improvement method for small process changes and direct crisis management for immediate response situations.\n\n## Reference(s):\n\n- [Primary sources](references/sources.md)\n- [IBM's Turnaround under Lou Gerstner (1993-1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)\n- [Driving Enterprise AI Adoption (2024-2026)](examples/enterprise-ai-adoption-2024-2026.md)\n- [Leading Change: Why Transformation Efforts Fail](https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2)\n- [The State of AI](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai)\n- [MIT Sloan Management Review](https://sloanreview.mit.edu/)\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/kotter-change)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown readiness report with a failure-mode scoring table, eight-step roadmap, and 24-month milestone timeline]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May pause for user input at explicit coach-mode wait gates.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 6 files, 12266 bytes\n\nFiles: examples/enterprise-ai-adoption-2024-2026.md (6679b), examples/ibm-turnaround-lou-gerstner-1993-1996.md (3091b), references/sources.md (2618b), skill-card.md (2112b), SKILL.md (8573b), _meta.json (132b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: kotter-change\ndescription: \"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.\n  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.\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: `okr-goal-setting` inside Steps 3 and 6; `feedback-loops` throughout Steps 6–7; `situational-leadership` for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n- 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\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Absent or unclear vision | /5 |\n| Under-communication | /5 |\n| Obstacles not removed | /5 |\n| No short-term wins | /5 |\n| Premature victory declared | /5 |\n| Not anchored in culture | /5 |\n\nScores 4–5 require pre-treatment before the corresponding step.\n\n**Steps 1–8 (each has a gate):**\n1. **Urgency** — import external data; make cost of inaction concrete. Gate: 75%+ of leadership believes change is necessary.\n2. **Guiding coalition** — needs positional power + expertise + credibility + leadership; map on influence × stance 2×2. Gate: 2–3 informal influencers (non-VP).\n3. **Vision** — 30-second elevator test; six attributes: imaginable, desirable, feasible, focused, flexible, communicable. Gate: passes five-audience test.\n4. **Communicate** — embed vision in every forum, review, conversation. Gate: random sampling confirms employees can repeat vision accurately.\n5. **Remove obstacles** — eliminate structural, process, and personal blockers. Gate: 3 specific blockers identified and removed.\n6. **Short-term wins** — planned, unambiguous business outcomes in 12–24 months. Gate: one win defined and dated at launch.\n7. **Consolidate** — use win credibility to tackle larger obstacles; don't disband the change team. Stop-rule: wins must trace causally to new ways of working.\n8. **Anchor in culture** — four mechanisms: hiring, promotion, onboarding, KPI criteria. Gate: new hire 2 years later experiences new ways as default.\n\n**Output:** `# Change Readiness: <initiative> / Failure mode scores (table) / 8-Step Roadmap (one line per step) / Timeline (24-month milestones)`\n\n*→ Method in Action: [IBM's Turnaround under Lou Gerstner (1993–1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)*\n*→ 2026 lens: [Driving Enterprise AI Adoption (2024–2026)](examples/enterprise-ai-adoption-2024-2026.md)*\n\n## Change-Type Packs\n\n- **Digital/AI:** Step 5 most underinvested — legacy metrics, procurement, and security processes block new ways of working.\n- **Post-merger:** Step 2 highest-risk — coalition must span both entities; Step 6 wins must be jointly owned.\n- **Startup scaling (A–C):** Step 8 most skipped — informal culture breaks at 25→150 people; formal anchoring feels premature but is essential.\n\n## Applying It Well\n\n- Urgency requires sustained evidence exposure, not a one-time announcement; monthly data reviews maintain it longer than any kick-off.\n- Coalition fails by being homogeneous — informal influencers (respected ICs, long-tenured peers) outperform additional VPs.\n- Short-term wins must be defined, measured, and dated at launch — retrospective wins have reduced motivational power.\n- Communication almost always falls short — multiply planned volume by 10; silence is interpreted as reversal.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We announced at the all-hands — it's launched\" | Announcing does not create urgency. Until 75%+ of leadership believes status quo is dangerous, transformation has not started. |\n| [D] \"The guiding coalition is our executive committee\" | Executive committees lack informal credibility. A coalition without informal influencers cannot move the middle of the organization. |\n| [D] \"Our vision is to become the best-in-class provider\" | Not imaginable, not specific, not communicable in 30 seconds. A vision a front-line employee cannot state is a slogan. |\n| [D] \"We communicated at every town hall for three months\" | Likely 5–10% of the volume needed. Leaders underestimate the communication deficit by a factor of 10. |\n| [D] \"The pilot succeeded so rollout will follow naturally\" | Pilot = Step 6 win. Without Steps 7–8, the change team disperses and the org reverts. |\n| [D] \"Culture will follow the process changes\" | Culture follows demonstrated performance improvement with an explicit causal link — not process changes alone. |\n| [D] \"We'll generate quick wins as we go\" | Wins need a definition, measurement system, and celebration mechanism built in at launch. Unplanned wins are weaker. |\n| [D] \"People know it's a priority — no need to put it in reviews\" | Priorities not in performance criteria are cultural wishes, not institutional commitments. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- No pre-diagnostic; coalition is all formal reports to the sponsor; vision unknown to front-line employees 30 days after launch; no win defined or dated at launch; initiative declared complete after first win without Step 8 testing.\n\n## Verification\n\n- [ ] Pre-diagnostic completed (all eight failure modes scored); 75%+ of leadership verified as genuinely sensing urgency\n- [ ] Coalition includes 2+ informal influencers (non-VP); vision passes 30-second front-line test\n- [ ] 3 specific structural obstacles eliminated; 1 short-term win defined, dated, and in the roadmap at launch\n- [ ] Step 8 anchoring mechanisms named (hiring / promotion / onboarding / KPI); stop-rule applied to Step 7\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 189 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/kotter-change** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1783595917700\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**Contemporary context (2024–2026 enterprise AI adoption):**\n- 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\n- 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/\n\n**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.\n\nFile v1.0.4:examples/enterprise-ai-adoption-2024-2026.md\n\n# Method in Action: Driving Enterprise AI Adoption (2024–2026)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nBy 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.\n\n**Pre-diagnostic (highest-risk failure modes for AI transformations):**\n- *Complacency / no urgency* — often HIGH: \"we already bought licenses, we're doing AI.\"\n- *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.\n- *No short-term wins* — often HIGH: pilots are measured on activity, not business outcomes.\n\n**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.\n\n**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.\n\n**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.\n\n**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 the initiative targets their jobs. The vision must be repeated in every forum, review, and one-on-one. The gate: random sampling confirms employees — including skeptical managers — can accurately restate what the change is *and is not*.\n\n**Step 5 (remove obstacles):** For AI this is the most underinvested step and the one where middle-manager resistance becomes structural rather than merely attitudinal. Blockers to identify and remove: data-access and security review processes that make AI tools unusable on real work; procurement cycles that stall integration; and — most importantly — performance metrics and incentives that reward the old way. If a manager is still measured on headcount managed or hours logged rather than outcomes delivered, they are structurally incentivized to resist. The gate requires three specific blockers removed, not a general \"we support AI\" statement.\n\n**Step 6 (short-term wins):** Pilots measured on \"number of users onboarded\" are activity, not wins. Define one unambiguous business outcome, dated at launch — e.g., a specific team cutting cycle time on a real workflow by a target percentage within two quarters, with the measurement system built in beforehand. The win should ideally be owned by a *previously skeptical* team, so its credibility travels to the resistant middle.\n\n**Step 7 (consolidate):** The classic AI-adoption error is declaring victory when a pilot succeeds. A successful pilot is a Step 6 win, not completion — disband the change team and the organization reverts to old workflows. Instead, use the win's credibility to attack the larger obstacles from Step 5 (the incentive and process changes), and hold the stop-rule: wins must trace causally to the new ways of working, not to a motivated pilot team's extra effort.\n\n**Step 8 (anchor in culture):** AI adoption becomes permanent only when it is embedded in the four mechanisms — hiring (AI-fluency in job criteria), promotion (rewarding managers who redesign work around AI, not those who protect legacy processes), onboarding (new joiners learn the AI-native workflow as the default), and KPIs (outcome metrics replace activity metrics). The test: a person who joins two years later experiences the AI-augmented way as simply \"how we work here.\" Until managers are promoted for it rather than despite it, the transformation remains a wish.\n\n**Why middle managers resist, in Kotter terms:** the resistance is not irrational. It concentrates at the exact points the model flags — Step 2 (they are the un-recruited middle), Step 5 (their incentives still reward the old way), and Step 8 (promotion criteria have not changed). Treating it as an attitude problem to be overcome with more town halls (Step 4 alone) is the predictable error; the model locates it as a coalition, obstacle, and anchoring problem.\n\n*Sources: Kotter, J.P. (1996). *Leading Change.* Harvard Business School Press (ISBN 978-0875847474) — the eight-step framework and the Digital/AI-relevant emphasis on urgency, coalition, obstacle removal, and cultural anchoring. Kotter, J.P. (1995). \"Leading Change: Why Transformation Efforts Fail.\" *Harvard Business Review*, 73(2). https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2 — the eight failure modes. The 2024–2026 enterprise-AI adoption pattern (pilots stalling, under-used licenses, difficulty demonstrating ROI on AI spending, and organizational rather than purely technical barriers) is drawn from widely reported industry surveys and reporting on generative-AI adoption in that period; specific figures are omitted here to avoid overstating any single source.*\n\nFile v1.0.4:examples/ibm-turnaround-lou-gerstner-1993-1996.md\n\n# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nGuides agents through diagnosing stalled organizational change and sequencing Kotter's eight steps for planned transformations. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, leaders, and advisors use this skill to assess whether a planned organizational change fits Kotter's model, diagnose skipped steps, and produce a change readiness score, eight-step roadmap, and milestone timeline. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Change-management outputs may reflect incorrect timelines, organizational assumptions, or cited examples if used without local review. <br>\nMitigation: Verify assumptions, timelines, and cited examples with qualified stakeholders before using the guidance for major change-management decisions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/kotter-change) <br>\n- [Primary sources](references/sources.md) <br>\n- [Leading Change: Why Transformation Efforts Fail](https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2) <br>\n- [McKinsey State of AI](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) <br>\n- [MIT Sloan Management Review](https://sloanreview.mit.edu/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [markdown, text, guidance] <br>\n**Output Format:** [Markdown with tables, questions, roadmap steps, and timeline milestones] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause for user input in coach mode before advancing through the diagnostic.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 5 files, 8397 bytes\n\nFiles: examples/ibm-turnaround-lou-gerstner-1993-1996.md (3091b), references/sources.md (1817b), skill-card.md (2209b), SKILL.md (8254b), _meta.json (132b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: kotter-change\ndescription: \"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.\n  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.\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: `okr-goal-setting` inside Steps 3 and 6; `feedback-loops` throughout Steps 6–7; `situational-leadership` for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Absent or unclear vision | /5 |\n| Under-communication | /5 |\n| Obstacles not removed | /5 |\n| No short-term wins | /5 |\n| Premature victory declared | /5 |\n| Not anchored in culture | /5 |\n\nScores 4–5 require pre-treatment before the corresponding step.\n\n**Steps 1–8 (each has a gate):**\n1. **Urgency** — import external data; make cost of inaction concrete. Gate: 75%+ of leadership believes change is necessary.\n2. **Guiding coalition** — needs positional power + expertise + credibility + leadership; map on influence × stance 2×2. Gate: 2–3 informal influencers (non-VP).\n3. **Vision** — 30-second elevator test; six attributes: imaginable, desirable, feasible, focused, flexible, communicable. Gate: passes five-audience test.\n4. **Communicate** — embed vision in every forum, review, conversation. Gate: random sampling confirms employees can repeat vision accurately.\n5. **Remove obstacles** — eliminate structural, process, and personal blockers. Gate: 3 specific blockers identified and removed.\n6. **Short-term wins** — planned, unambiguous business outcomes in 12–24 months. Gate: one win defined and dated at launch.\n7. **Consolidate** — use win credibility to tackle larger obstacles; don't disband the change team. Stop-rule: wins must trace causally to new ways of working.\n8. **Anchor in culture** — four mechanisms: hiring, promotion, onboarding, KPI criteria. Gate: new hire 2 years later experiences new ways as default.\n\n**Output:** `# Change Readiness: <initiative> / Failure mode scores (table) / 8-Step Roadmap (one line per step) / Timeline (24-month milestones)`\n\n*→ Method in Action: [IBM's Turnaround under Lou Gerstner (1993–1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)*\n\n## Change-Type Packs\n\n- **Digital/AI:** Step 5 most underinvested — legacy metrics, procurement, and security processes block new ways of working.\n- **Post-merger:** Step 2 highest-risk — coalition must span both entities; Step 6 wins must be jointly owned.\n- **Startup scaling (A–C):** Step 8 most skipped — informal culture breaks at 25→150 people; formal anchoring feels premature but is essential.\n\n## Applying It Well\n\n- Urgency requires sustained evidence exposure, not a one-time announcement; monthly data reviews maintain it longer than any kick-off.\n- Coalition fails by being homogeneous — informal influencers (respected ICs, long-tenured peers) outperform additional VPs.\n- Short-term wins must be defined, measured, and dated at launch — retrospective wins have reduced motivational power.\n- Communication almost always falls short — multiply planned volume by 10; silence is interpreted as reversal.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We announced at the all-hands — it's launched\" | Announcing does not create urgency. Until 75%+ of leadership believes status quo is dangerous, transformation has not started. |\n| [D] \"The guiding coalition is our executive committee\" | Executive committees lack informal credibility. A coalition without informal influencers cannot move the middle of the organization. |\n| [D] \"Our vision is to become the best-in-class provider\" | Not imaginable, not specific, not communicable in 30 seconds. A vision a front-line employee cannot state is a slogan. |\n| [D] \"We communicated at every town hall for three months\" | Likely 5–10% of the volume needed. Leaders underestimate the communication deficit by a factor of 10. |\n| [D] \"The pilot succeeded so rollout will follow naturally\" | Pilot = Step 6 win. Without Steps 7–8, the change team disperses and the org reverts. |\n| [D] \"Culture will follow the process changes\" | Culture follows demonstrated performance improvement with an explicit causal link — not process changes alone. |\n| [D] \"We'll generate quick wins as we go\" | Wins need a definition, measurement system, and celebration mechanism built in at launch. Unplanned wins are weaker. |\n| [D] \"People know it's a priority — no need to put it in reviews\" | Priorities not in performance criteria are cultural wishes, not institutional commitments. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- No pre-diagnostic; coalition is all formal reports to the sponsor; vision unknown to front-line employees 30 days after launch; no win defined or dated at launch; initiative declared complete after first win without Step 8 testing.\n\n## Verification\n\n- [ ] Pre-diagnostic completed (all eight failure modes scored); 75%+ of leadership verified as genuinely sensing urgency\n- [ ] Coalition includes 2+ informal influencers (non-VP); vision passes 30-second front-line test\n- [ ] 3 specific structural obstacles eliminated; 1 short-term win defined, dated, and in the roadmap at launch\n- [ ] Step 8 anchoring mechanisms named (hiring / promotion / onboarding / KPI); stop-rule applied to Step 7\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/kotter-change** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783508827536\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**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.\n\nFile v1.0.3:examples/ibm-turnaround-lou-gerstner-1993-1996.md\n\n# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nHelps agents diagnose and sequence planned organizational change using Kotter's 8-Step Change Model. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nBusiness leaders, operators, and agents use this skill to assess whether a planned organizational change fits Kotter's model, score common failure modes, and produce an eight-step roadmap with milestones. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Organizational change recommendations may be incomplete or contextually wrong if treated as authoritative business advice. <br>\nMitigation: Use the skill as decision support and have responsible business owners review recommendations before acting. <br>\nRisk: The framework may be misapplied to small process improvements, very small organizations, or crisis situations. <br>\nMitigation: Apply the skill's fit checks first and use a lighter or more direct approach when those checks indicate Kotter's model is not appropriate. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/kotter-change) <br>\n- [Primary Sources](references/sources.md) <br>\n- [IBM Turnaround Example](examples/ibm-turnaround-lou-gerstner-1993-1996.md) <br>\n- [Leading Change: Why Transformation Efforts Fail](https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown readiness diagnostic, failure-mode table, eight-step roadmap, and timeline] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May stop at coaching checkpoints to wait for user input before continuing.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 5 files, 8358 bytes\n\nFiles: examples/ibm-turnaround-lou-gerstner-1993-1996.md (3091b), references/sources.md (1817b), skill-card.md (2040b), SKILL.md (8357b), _meta.json (132b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: kotter-change\ndescription: \"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.\n  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.\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: `okr-goal-setting` inside Steps 3 and 6; `feedback-loops` throughout Steps 6–7; `situational-leadership` for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Absent or unclear vision | /5 |\n| Under-communication | /5 |\n| Obstacles not removed | /5 |\n| No short-term wins | /5 |\n| Premature victory declared | /5 |\n| Not anchored in culture | /5 |\n\nScores 4–5 require pre-treatment before the corresponding step.\n\n**Steps 1–8 (each has a gate):**\n1. **Urgency** — import external data; make cost of inaction concrete. Gate: 75%+ of leadership believes change is necessary.\n2. **Guiding coalition** — needs positional power + expertise + credibility + leadership; map on influence × stance 2×2. Gate: 2–3 informal influencers (non-VP).\n3. **Vision** — 30-second elevator test; six attributes: imaginable, desirable, feasible, focused, flexible, communicable. Gate: passes five-audience test.\n4. **Communicate** — embed vision in every forum, review, conversation. Gate: random sampling confirms employees can repeat vision accurately.\n5. **Remove obstacles** — eliminate structural, process, and personal blockers. Gate: 3 specific blockers identified and removed.\n6. **Short-term wins** — planned, unambiguous business outcomes in 12–24 months. Gate: one win defined and dated at launch.\n7. **Consolidate** — use win credibility to tackle larger obstacles; don't disband the change team. Stop-rule: wins must trace causally to new ways of working.\n8. **Anchor in culture** — four mechanisms: hiring, promotion, onboarding, KPI criteria. Gate: new hire 2 years later experiences new ways as default.\n\n**Output:** `# Change Readiness: <initiative> / Failure mode scores (table) / 8-Step Roadmap (one line per step) / Timeline (24-month milestones)`\n\n*→ Method in Action: [IBM's Turnaround under Lou Gerstner (1993–1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)*\n\n## Change-Type Packs\n\n- **Digital/AI:** Step 5 most underinvested — legacy metrics, procurement, and security processes block new ways of working.\n- **Post-merger:** Step 2 highest-risk — coalition must span both entities; Step 6 wins must be jointly owned.\n- **Startup scaling (A–C):** Step 8 most skipped — informal culture breaks at 25→150 people; formal anchoring feels premature but is essential.\n\n## Applying It Well\n\n- Urgency requires sustained evidence exposure, not a one-time announcement; monthly data reviews maintain it longer than any kick-off.\n- Coalition fails by being homogeneous — informal influencers (respected ICs, long-tenured peers) outperform additional VPs.\n- Short-term wins must be defined, measured, and dated at launch — retrospective wins have reduced motivational power.\n- Communication almost always falls short — multiply planned volume by 10; silence is interpreted as reversal.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We announced at the all-hands — it's launched\" | Announcing does not create urgency. Until 75%+ of leadership believes status quo is dangerous, transformation has not started. |\n| [D] \"The guiding coalition is our executive committee\" | Executive committees lack informal credibility. A coalition without informal influencers cannot move the middle of the organization. |\n| [D] \"Our vision is to become the best-in-class provider\" | Not imaginable, not specific, not communicable in 30 seconds. A vision a front-line employee cannot state is a slogan. |\n| [D] \"We communicated at every town hall for three months\" | Likely 5–10% of the volume needed. Leaders underestimate the communication deficit by a factor of 10. |\n| [D] \"The pilot succeeded so rollout will follow naturally\" | Pilot = Step 6 win. Without Steps 7–8, the change team disperses and the org reverts. |\n| [D] \"Culture will follow the process changes\" | Culture follows demonstrated performance improvement with an explicit causal link — not process changes alone. |\n| [D] \"We'll generate quick wins as we go\" | Wins need a definition, measurement system, and celebration mechanism built in at launch. Unplanned wins are weaker. |\n| [D] \"People know it's a priority — no need to put it in reviews\" | Priorities not in performance criteria are cultural wishes, not institutional commitments. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- No pre-diagnostic; coalition is all formal reports to the sponsor; vision unknown to front-line employees 30 days after launch; no win defined or dated at launch; initiative declared complete after first win without Step 8 testing.\n\n## Verification\n\n- [ ] Pre-diagnostic completed (all eight failure modes scored); 75%+ of leadership verified as genuinely sensing urgency\n- [ ] Coalition includes 2+ informal influencers (non-VP); vision passes 30-second front-line test\n- [ ] 3 specific structural obstacles eliminated; 1 short-term win defined, dated, and in the roadmap at launch\n- [ ] Step 8 anchoring mechanisms named (hiring / promotion / onboarding / KPI); stop-rule applied to Step 7\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/kotter-change?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=kotter-change** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783471914652\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**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.\n\nFile v1.0.2:examples/ibm-turnaround-lou-gerstner-1993-1996.md\n\n# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nGuides agents through Kotter's 8-step change model to diagnose stalled organizational transformations and produce a structured change-readiness roadmap. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, leaders, consultants, and agents use this skill to assess planned organizational change, identify skipped Kotter steps, and draft a 24-month roadmap with failure-mode scores and gated actions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Organizational change guidance may be applied as a substitute for legal, HR, financial, or executive review when decisions affect employees or business operations. <br>\nMitigation: Use the skill as a planning framework and route high-impact organizational decisions through the appropriate legal, HR, financial, and executive reviewers. <br>\n\n\n## Reference(s): <br>\n- [Sources - kotter-change](references/sources.md) <br>\n- [IBM's Turnaround under Lou Gerstner (1993-1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md) <br>\n- [Leading Change: Why Transformation Efforts Fail](https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown] <br>\n**Output Format:** [Markdown with diagnostic tables, roadmap sections, and milestone guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a change-readiness report with failure-mode scores, an 8-step roadmap, and 24-month milestones.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 5 files, 8484 bytes\n\nFiles: examples/ibm-turnaround-lou-gerstner-1993-1996.md (3091b), references/sources.md (1817b), skill-card.md (2485b), SKILL.md (8203b), _meta.json (132b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: kotter-change\ndescription: \"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.\n  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.\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: [`okr-goal-setting`](../okr-goal-setting/SKILL.md) inside Steps 3 and 6; [`feedback-loops`](../feedback-loops/SKILL.md) throughout Steps 6–7; [`situational-leadership`](../situational-leadership/SKILL.md) for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Absent or unclear vision | /5 |\n| Under-communication | /5 |\n| Obstacles not removed | /5 |\n| No short-term wins | /5 |\n| Premature victory declared | /5 |\n| Not anchored in culture | /5 |\n\nScores 4–5 require pre-treatment before the corresponding step.\n\n**Steps 1–8 (each has a gate):**\n1. **Urgency** — import external data; make cost of inaction concrete. Gate: 75%+ of leadership believes change is necessary.\n2. **Guiding coalition** — needs positional power + expertise + credibility + leadership; map on influence × stance 2×2. Gate: 2–3 informal influencers (non-VP).\n3. **Vision** — 30-second elevator test; six attributes: imaginable, desirable, feasible, focused, flexible, communicable. Gate: passes five-audience test.\n4. **Communicate** — embed vision in every forum, review, conversation. Gate: random sampling confirms employees can repeat vision accurately.\n5. **Remove obstacles** — eliminate structural, process, and personal blockers. Gate: 3 specific blockers identified and removed.\n6. **Short-term wins** — planned, unambiguous business outcomes in 12–24 months. Gate: one win defined and dated at launch.\n7. **Consolidate** — use win credibility to tackle larger obstacles; don't disband the change team. Stop-rule: wins must trace causally to new ways of working.\n8. **Anchor in culture** — four mechanisms: hiring, promotion, onboarding, KPI criteria. Gate: new hire 2 years later experiences new ways as default.\n\n**Output:** `# Change Readiness: <initiative> / Failure mode scores (table) / 8-Step Roadmap (one line per step) / Timeline (24-month milestones)`\n\n*→ Method in Action: [IBM's Turnaround under Lou Gerstner (1993–1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)*\n\n## Change-Type Packs\n\n- **Digital/AI:** Step 5 most underinvested — legacy metrics, procurement, and security processes block new ways of working.\n- **Post-merger:** Step 2 highest-risk — coalition must span both entities; Step 6 wins must be jointly owned.\n- **Startup scaling (A–C):** Step 8 most skipped — informal culture breaks at 25→150 people; formal anchoring feels premature but is essential.\n\n## Applying It Well\n\n- Urgency requires sustained evidence exposure, not a one-time announcement; monthly data reviews maintain it longer than any kick-off.\n- Coalition fails by being homogeneous — informal influencers (respected ICs, long-tenured peers) outperform additional VPs.\n- Short-term wins must be defined, measured, and dated at launch — retrospective wins have reduced motivational power.\n- Communication almost always falls short — multiply planned volume by 10; silence is interpreted as reversal.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We announced at the all-hands — it's launched\" | Announcing does not create urgency. Until 75%+ of leadership believes status quo is dangerous, transformation has not started. |\n| [D] \"The guiding coalition is our executive committee\" | Executive committees lack informal credibility. A coalition without informal influencers cannot move the middle of the organization. |\n| [D] \"Our vision is to become the best-in-class provider\" | Not imaginable, not specific, not communicable in 30 seconds. A vision a front-line employee cannot state is a slogan. |\n| [D] \"We communicated at every town hall for three months\" | Likely 5–10% of the volume needed. Leaders underestimate the communication deficit by a factor of 10. |\n| [D] \"The pilot succeeded so rollout will follow naturally\" | Pilot = Step 6 win. Without Steps 7–8, the change team disperses and the org reverts. |\n| [D] \"Culture will follow the process changes\" | Culture follows demonstrated performance improvement with an explicit causal link — not process changes alone. |\n| [D] \"We'll generate quick wins as we go\" | Wins need a definition, measurement system, and celebration mechanism built in at launch. Unplanned wins are weaker. |\n| [D] \"People know it's a priority — no need to put it in reviews\" | Priorities not in performance criteria are cultural wishes, not institutional commitments. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- No pre-diagnostic; coalition is all formal reports to the sponsor; vision unknown to front-line employees 30 days after launch; no win defined or dated at launch; initiative declared complete after first win without Step 8 testing.\n\n## Verification\n\n- [ ] Pre-diagnostic completed (all eight failure modes scored); 75%+ of leadership verified as genuinely sensing urgency\n- [ ] Coalition includes 2+ informal influencers (non-VP); vision passes 30-second front-line test\n- [ ] 3 specific structural obstacles eliminated; 1 short-term win defined, dated, and in the roadmap at launch\n- [ ] Step 8 anchoring mechanisms named (hiring / promotion / onboarding / KPI); stop-rule applied to Step 7\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783463282188\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**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.\n\nFile v1.0.1:examples/ibm-turnaround-lou-gerstner-1993-1996.md\n\n# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nGuides agents through Kotter's eight-step change model to diagnose stalled transformations, sequence planned organizational change, and produce a readiness assessment and roadmap. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, leaders, consultants, and change practitioners use this skill to assess whether Kotter's model fits a planned transformation, score eight common failure modes, and build a sequenced roadmap with checkpoints and short-term wins. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Organizational change guidance can be misapplied to small process improvements, very small organizations, short timelines, or crises that require immediate command-and-control response. <br>\nMitigation: Apply the skill's fit check before using the framework and redirect to lighter improvement methods or crisis leadership approaches when the not-use criteria apply. <br>\nRisk: Roadmaps may overstate readiness if urgency, coalition strength, vision clarity, blockers, wins, or cultural anchoring are not verified with real organizational evidence. <br>\nMitigation: Use the pre-diagnostic, gates, and verification checklist before treating the generated roadmap as actionable. <br>\n\n\n## Reference(s): <br>\n- [Sources - kotter-change](references/sources.md) <br>\n- [IBM's Turnaround under Lou Gerstner (1993-1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md) <br>\n- [Leading Change: Why Transformation Efforts Fail](https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown readiness assessment with a failure-mode score table, eight-step roadmap, and 24-month milestone timeline] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May operate interactively in coaching mode with explicit stop points while gathering change context.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 5 files, 8296 bytes\n\nFiles: examples/ibm-turnaround-lou-gerstner-1993-1996.md (3091b), references/sources.md (1817b), skill-card.md (2141b), SKILL.md (8203b), _meta.json (132b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: kotter-change\ndescription: \"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.\n  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.\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: [`okr-goal-setting`](../okr-goal-setting/SKILL.md) inside Steps 3 and 6; [`feedback-loops`](../feedback-loops/SKILL.md) throughout Steps 6–7; [`situational-leadership`](../situational-leadership/SKILL.md) for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Absent or unclear vision | /5 |\n| Under-communication | /5 |\n| Obstacles not removed | /5 |\n| No short-term wins | /5 |\n| Premature victory declared | /5 |\n| Not anchored in culture | /5 |\n\nScores 4–5 require pre-treatment before the corresponding step.\n\n**Steps 1–8 (each has a gate):**\n1. **Urgency** — import external data; make cost of inaction concrete. Gate: 75%+ of leadership believes change is necessary.\n2. **Guiding coalition** — needs positional power + expertise + credibility + leadership; map on influence × stance 2×2. Gate: 2–3 informal influencers (non-VP).\n3. **Vision** — 30-second elevator test; six attributes: imaginable, desirable, feasible, focused, flexible, communicable. Gate: passes five-audience test.\n4. **Communicate** — embed vision in every forum, review, conversation. Gate: random sampling confirms employees can repeat vision accurately.\n5. **Remove obstacles** — eliminate structural, process, and personal blockers. Gate: 3 specific blockers identified and removed.\n6. **Short-term wins** — planned, unambiguous business outcomes in 12–24 months. Gate: one win defined and dated at launch.\n7. **Consolidate** — use win credibility to tackle larger obstacles; don't disband the change team. Stop-rule: wins must trace causally to new ways of working.\n8. **Anchor in culture** — four mechanisms: hiring, promotion, onboarding, KPI criteria. Gate: new hire 2 years later experiences new ways as default.\n\n**Output:** `# Change Readiness: <initiative> / Failure mode scores (table) / 8-Step Roadmap (one line per step) / Timeline (24-month milestones)`\n\n*→ Method in Action: [IBM's Turnaround under Lou Gerstner (1993–1996)](examples/ibm-turnaround-lou-gerstner-1993-1996.md)*\n\n## Change-Type Packs\n\n- **Digital/AI:** Step 5 most underinvested — legacy metrics, procurement, and security processes block new ways of working.\n- **Post-merger:** Step 2 highest-risk — coalition must span both entities; Step 6 wins must be jointly owned.\n- **Startup scaling (A–C):** Step 8 most skipped — informal culture breaks at 25→150 people; formal anchoring feels premature but is essential.\n\n## Applying It Well\n\n- Urgency requires sustained evidence exposure, not a one-time announcement; monthly data reviews maintain it longer than any kick-off.\n- Coalition fails by being homogeneous — informal influencers (respected ICs, long-tenured peers) outperform additional VPs.\n- Short-term wins must be defined, measured, and dated at launch — retrospective wins have reduced motivational power.\n- Communication almost always falls short — multiply planned volume by 10; silence is interpreted as reversal.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We announced at the all-hands — it's launched\" | Announcing does not create urgency. Until 75%+ of leadership believes status quo is dangerous, transformation has not started. |\n| [D] \"The guiding coalition is our executive committee\" | Executive committees lack informal credibility. A coalition without informal influencers cannot move the middle of the organization. |\n| [D] \"Our vision is to become the best-in-class provider\" | Not imaginable, not specific, not communicable in 30 seconds. A vision a front-line employee cannot state is a slogan. |\n| [D] \"We communicated at every town hall for three months\" | Likely 5–10% of the volume needed. Leaders underestimate the communication deficit by a factor of 10. |\n| [D] \"The pilot succeeded so rollout will follow naturally\" | Pilot = Step 6 win. Without Steps 7–8, the change team disperses and the org reverts. |\n| [D] \"Culture will follow the process changes\" | Culture follows demonstrated performance improvement with an explicit causal link — not process changes alone. |\n| [D] \"We'll generate quick wins as we go\" | Wins need a definition, measurement system, and celebration mechanism built in at launch. Unplanned wins are weaker. |\n| [D] \"People know it's a priority — no need to put it in reviews\" | Priorities not in performance criteria are cultural wishes, not institutional commitments. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- No pre-diagnostic; coalition is all formal reports to the sponsor; vision unknown to front-line employees 30 days after launch; no win defined or dated at launch; initiative declared complete after first win without Step 8 testing.\n\n## Verification\n\n- [ ] Pre-diagnostic completed (all eight failure modes scored); 75%+ of leadership verified as genuinely sensing urgency\n- [ ] Coalition includes 2+ informal influencers (non-VP); vision passes 30-second front-line test\n- [ ] 3 specific structural obstacles eliminated; 1 short-term win defined, dated, and in the roadmap at launch\n- [ ] Step 8 anchoring mechanisms named (hiring / promotion / onboarding / KPI); stop-rule applied to Step 7\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782724660258\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**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.\n\nFile v1.0.0:examples/ibm-turnaround-lou-gerstner-1993-1996.md\n\n# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who Says Elephants Can't Dance?: Inside IBM's Historic Turnaround.* HarperBusiness.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nGuides agents in diagnosing and sequencing planned organizational change using Kotter's eight-step change model. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, consultants, and organizational-change practitioners use this skill to assess stalled or planned transformations, identify skipped Kotter steps, and produce a readiness diagnostic, roadmap, and milestone timeline. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Organizational-change recommendations may be incomplete or inappropriate for sensitive legal, HR, labor, or personnel decisions. <br>\nMitigation: Use the skill as a structured business-framework aid and have qualified legal, HR, or change-management professionals review decisions before implementation. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/kotter-change) <br>\n- [Publisher profile](https://clawhub.ai/user/deciqai) <br>\n- [Sources - kotter-change](references/sources.md) <br>\n- [IBM turnaround example](examples/ibm-turnaround-lou-gerstner-1993-1996.md) <br>\n- [Leading Change: Why Transformation Efforts Fail](https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2) <br>\n- [deciqAI](https://deciqai.com) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown with diagnostic tables, roadmap bullets, and timeline milestones] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces business-framework guidance only; no code execution, tool calls, or external-system actions.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"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","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: kotter-change\ndescription: \"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.\n  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\"\n---\n\n# Kotter's 8-Step Change Model\n\n## Overview\n\nJohn 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.\n\nComposes with: `okr-goal-setting` inside Steps 3 and 6; `feedback-loops` throughout Steps 6–7; `situational-leadership` for individual-level management at each step.\n\n## When to Use\n\n- Planned change (digital transformation, process redesign, cultural shift, merger integration) needs sequencing\n- Transformation is stalling — diagnose which step was skipped\n- Resistance is significant and needs a structured approach\n- Someone says \"nobody's buying in\", \"we went back to old ways\", \"the rollout failed\"\n- 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\n\n**When NOT to use:** small process improvement; org under 30–50 people; change needed in weeks; crisis requiring immediate action.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific transformation → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: eight steps built from studying a hundred real transformations; each step defeats one common failure mode.\n2. Check fit: planned change, 30+ people, 12+ months? If yes, framework fits. Otherwise point to lighter tools.\n3. Elicit the real situation: what is changing, what org, what is the current resistance level?\n> **[WAIT — do not advance until user responds]**\n4. Run the readiness diagnostic (step 1 of The Process) before presenting all eight steps.\n> **[WAIT — do not advance until user responds]**\n5. Close by naming which failure mode is highest-risk and which step defeats it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Pre-diagnostic — score eight failure modes (1–5):**\n\n| Failure mode | Risk |\n|---|---|\n| Complacency / no urgency felt | /5 |\n| Weak coalition — key influencers uncommitted | /5 |\n| Abse"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"kotter-change\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784225053055\n}"},{"path":"references/sources.md","content":"# Sources — kotter-change\n\n> *Primary sources for the [kotter-change](../SKILL.md) skill.*\n\n- 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\n- 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.\n- 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.\n- 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.\n- 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.\n\n**Contemporary context (2024–2026 enterprise AI adoption):**\n- 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\n- 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/\n\n**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."},{"path":"examples/enterprise-ai-adoption-2024-2026.md","content":"# Method in Action: Driving Enterprise AI Adoption (2024–2026)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nBy 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.\n\n**Pre-diagnostic (highest-risk failure modes for AI transformations):**\n- *Complacency / no urgency* — often HIGH: \"we already bought licenses, we're doing AI.\"\n- *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.\n- *No short-term wins* — often HIGH: pilots are measured on activity, not business outcomes.\n\n**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.\n\n**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.\n\n**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.\n\n**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 "},{"path":"examples/ibm-turnaround-lou-gerstner-1993-1996.md","content":"# Method in Action: IBM's Turnaround under Lou Gerstner (1993–1996)\n\n> *Example for the [kotter-change](../SKILL.md) skill.*\n\nIn 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.\n\nKotter's eight steps applied to Gerstner's turnaround:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\n**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.\n\nPrimary source: Gerstner, L.V. (2002). *Who S"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"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","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2108,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:34:54.825Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:34:54.825Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:41:49.983Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}