Disruptive Innovation

SKILL.md

---
name: disruptive-innovation
description: "Activate when: a founder asks 'can we avoid competing head-on with big players?', someone asks 'is this disruption or just a price war?', an investor wonders if a startup's entry angle creates durable structural advantage, an incumbent spots a cheap new entrant and needs to know if it's a real threat, a product team wants to know which features to deliberately leave out of an MVP.
  Do NOT activate when: the market requires absolute performance with no 'good enough' threshold (aircraft engines, Class III medical devices), or the competitive situation is a pure price war with no cost-structure asymmetry."
---

# Disruptive Innovation

## Overview

Most incumbents fail not because they make bad decisions, but because they make good ones. Clayton Christensen found that leading firms listened to their best customers, invested in high-margin segments, and were displaced anyway. The pattern: incumbents overshoot mainstream customer needs, creating a price window at the low end that a new entrant can enter profitably — and the incumbent cannot match without cannibalizing its own margins. Disruptors enter there, accumulate resources, and migrate upward.

Two paths exist: **low-end disruption** targets price-sensitive existing customers who are over-served; **new-market disruption** creates consumption among people who couldn't previously participate at all.

Compose with neighbors: [s-curve-technology-adoption](../s-curve-technology-adoption/SKILL.md) to assess incumbent vulnerability; [pmf-crossing-the-chasm](../pmf-crossing-the-chasm/SKILL.md) after identifying the entry point; [blue-ocean-strategy](../blue-ocean-strategy/SKILL.md) when the attacker wants to reshape value dimensions; [second-curve](../second-curve/SKILL.md) for the incumbent's response problem.

## When to Use

Apply when: founder choosing market entry to avoid head-to-head; incumbent assessing low-price entrant threat; investor evaluating startup structural advantage; product team defining what to deliberately exclude from MVP.

**When NOT to use:** market requires absolute performance / no "good enough" threshold (aircraft engines, Class III devices); purely a price war with no cost-structure asymmetry; someone labeling every new entrant "disruptive" (Uber is sustaining innovation); insufficient data to assess overshooting.

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** user has a specific market, incumbent, and entry point → run The Process directly.
- **Coach mode:** user asks "what is this / does it apply to me?" → guide step by step.

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

1. One-line what-it-is: incumbents keep improving products beyond what customers need, creating a price window a new entrant can exploit profitably while the incumbent rationally ignores it.
2. Check fit against When to Use / When NOT to use. If safety-critical or pure price war, redirect.
3. Elicit their real case: "Which incumbent, which market, what's your proposed entry angle?"
> **[WAIT — do not advance until user responds]**
4. Walk The Process one step per turn — pose each step's question, wait for their answer, advance with their input.
> **[WAIT — do not advance until user responds]**
5. Close by naming the specific structural reason the incumbent won't follow — the insight that changes how they think about entry.
> **[WAIT — do not advance until user responds]**

## The Process

Run the **Disruption Assessment**. Identify the structural conditions, then map the attacker path.

1. **Map performance-price landscape.** List major incumbents, customers, performance, price. Is any incumbent providing performance clearly beyond what mainstream customers use? If yes — overshooting is present.
2. **Find ignored segments.** (a) *Low-end:* who pays for performance they don't use? (b) *Non-consumption:* who is blocked by price/complexity/access? Name them specifically.
3. **Define "good enough" for entry.** Which dimensions are necessary vs. removable? Cost savings from removal fund the lower price. MVP = target segment's needs, not incumbent feature parity.
4. **Analyze rational neglect.** Why won't the incumbent follow? Cannibalization of high-margin customers? Cost structure makes low-end unprofitable? Sales force incentives anchored on premium accounts? If no structural barrier exists, the disruption window is narrow.
5. **Map upward migration path.** Sketch product roadmap from entry to mainstream. Confirm the path exists — permanently low-end = niche, not disruption.
6. **Stop-rule.** Christensen's three conditions: (a) inferior on mainstream metrics? (b) low-end or non-consumer target? (c) incumbent has rational reason not to compete? All three must pass — otherwise label accurately.

### Output: Disruption Assessment

```
Performance Landscape: incumbents / overshooting evidence / mainstream ceiling
Ignored Segments: low-end (who, need, price) / non-consumers (who, barrier)
"Good Enough" Definition: must-haves / safely removed / entry product (1-2 sentences)
Incumbent Rational Neglect: structural reason(s) / confidence (H/M/L + rationale)
Upward Migration Path: Stage 1 → Stage 2 → Stage 3+ (customer tier + required improvement)
Disruption Verdict: genuine / partial / no — if no, label accurately / primary invalidation risk
```

*→ Method in Action: [Netflix vs. Blockbuster (1997–2010)](examples/netflix-vs-blockbuster-1997-2010.md)*

## Disruption Packs

Domain-specific stop-rules (the Assessment runs identically everywhere):

- **Enterprise software:** stop-rule: incumbent already has an SMB product line → neglect window closed.
- **Financial services:** stop-rule: regulatory costs (KYC, AML) independently make low-end unprofitable → regulatory floor, not opportunity.
- **AI/software tools:** stop-rule: incumbent can replicate via API in two sprints → you have a feature, not a disruption.

## Applying It Well

- **Disruption is a structural pattern, not a label.** Apply the three-condition test before using the word.
- **The rational neglect is the moat.** Spend more time documenting the incumbent's structural inability to respond than designing the product.
- **"Good enough" is a precision concept.** Strip to what the target segment needs — each added feature narrows the cost advantage.
- **The upward path must exist.** Permanently low-end = niche, not disruption. Disruptors become incumbents — map your own future disruption.

*→ Primary sources: [references/sources.md](references/sources.md)*

## Common Rationalizations

**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**

| Fake move | Reality |
|---|---|
| [D] "We're disrupting the market" — any new entrant | Requires all three conditions: inferior on mainstream metrics, ignored segment, incumbent structural neglect. A better product at higher price is sustaining innovation. |
| [D] Low price = disruption proof | Low price is necessary, not sufficient. The incumbent must have a *structural* reason not to match it. |
| [D] No upward migration path considered | Disruption requires migration from low to mainstream. Permanently low-end = niche, not disruptive. |
| [D] Current non-response treated as permanent neglect | Neglect analysis must be time-stamped. An incumbent can acquire or build a response in 18 months. |
| [D] Assuming overshooting without evidence | "Customers don't need all those features" is not evidence — requires demonstrated switching behavior or WTP studies. |
| [D] Framework used predictively, not diagnostically | "Fits the pattern" ≠ "will succeed." The framework identifies conditions, not timing or probability. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |

## Red Flags

- Cannot name which specific customers are over-served and what performance they don't use
- Rational neglect asserted but not analyzed — no specific cost-structure or channel conflict identified
- Roadmap targets incumbent benchmarks, not the next tier of underserved customers
- "Disruption" label applied to a product *better* than incumbent on mainstream metrics (that's sustaining innovation)
- No upward migration path — business assumes permanent occupation of the low end
- Incumbent already launched a simplified product line in target segment (neglect window may be closed)
- Disruption case relies on technology not yet proven at scale

## Verification

- [ ] Overshooting evidenced by specific customer behavior — which performance dimensions exceed actual use
- [ ] Ignored segment named specifically with estimated size and willingness-to-pay
- [ ] "Good enough" defined by target segment needs, not incumbent feature parity
- [ ] Rational neglect analyzed structurally — specific cost, channel, or org friction identified
- [ ] Upward migration has ≥2 stages with named customer tiers and required improvements
- [ ] All three conditions documented: inferior on mainstream metrics / low-end or non-consumer / rational neglect
- [ ] If any condition fails, an honest alternative label is given

---

*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.*