Disruption threat test
Christensen's test, applied narrowly: is a new entrant taking your least profitable customers or serving people who were not buying, and does responding need a separate unit.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
Clayton Christensen's disruption theory, used narrowly rather than as a general-purpose label for any new competitor. Three specific questions decide whether a threat is genuinely disruptive: is the entrant taking the incumbent's least profitable, most over-served customers, or serving people who were not buying the category at all; is its rate of improvement steeper than customers' requirements are rising; and would responding require a separate unit because the incumbent's own economics and incentives will otherwise refuse the necessary trade-offs.
- Low-end entry
- The entrant targets the incumbent's least profitable, most over-served customers with a simpler, cheaper offer those customers are happy to accept.
- New-market entry
- The entrant serves people who were not consuming the category at all — competing against non-consumption rather than against the incumbent directly.
- Sustaining competition, not disruption
- The entrant competes head-on for the incumbent's best customers with a straightforwardly better version of the same offer. Real competition, and not what this test is built to find — misapplying the disruption label here produces the wrong response.
- Trajectory of improvement
- Whether the entrant's rate of improvement is steeper than the rate at which customer requirements are rising. If the trajectories will cross, the entrant eventually serves the incumbent's core customers too.
- The separate-unit test
- Whether responding on the entrant's terms would require cost, pricing or channel choices the incumbent's existing business would refuse — in which case a separate, differently incentivised unit is the only credible response.
How you run it
- Identify exactly who the entrant is winningWhich specific customer segment or use case — the incumbent's least profitable, over-served customers, people not previously buying, or the incumbent's best customers directly.
- Classify low-end, new-market or sustainingOnly the first two are disruption in Christensen's sense. Sustaining competition against the incumbent's core customers is ordinary competition, not disruption.
- Track the entrant's trajectory of improvementOver the period observed so far, is its rate of improvement steeper than customer requirements are rising. If the lines will cross, the threat eventually reaches the core.
- Test what responding on the entrant's terms would requireCost, pricing or channel choices the incumbent's existing business, incentives and cost structure would refuse to make.
- State whether a separate unit is genuinely requiredOnly where the existing business's own economics would block the necessary response. Not a default recommendation — a specific, tested conclusion.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- Where specifically the entrant is winning — which customer segment, which use case
- The entrant's trajectory of improvement over the period observed so far, not just its current position
- This business's own cost structure and what responding on the entrant's terms would do to it
You’ll end up with
- A specific answer on whether this is low-end, new-market or sustaining competition
- Whether the entrant's improvement trajectory is steeper than customers' rising requirements
- A clear statement of whether responding needs a separate, differently-run unit