Skills / Business-strategy

Disruptive Innovation

Disruption is a process, not an event, and innovations can only be disruptive relative to something else.

Clayton Christensen's Disruptive Innovation framework is the most rigorously documented theory of why well-managed industry leaders fail — and how entrants topple them. It equips corporate strategists, entrepreneurs, and investors with precise diagnostic tools: disruption typology classification, RPV capability audits, Jobs to Be Done research protocols, and structured threat assessments that distinguish genuine disruption from ordinary competition. Unlike generic strategy frameworks, it provides named mechanisms and structured screening questions that produce verifiable, actionable outputs.

By Clayton Christensen  ·  Free

Use this skill See it in action

Specimen 01 · Live diagnosisDisruptive Innovation

Input

“We're an incumbent. We sell ERP software to mid-market manufacturers — we've been the quality leader for 15 years. Lately these cloud-based…”

Diagnosis

Let's establish whether you're facing disruption or pursuing it.

Full transcript ↓

Calibrated referenceagent-skills.ai

The gap

Escape the innovator's dilemma: spot disruption before your best customers blind you

Christensen's framework operates on two levels: a descriptive theory explaining why well-managed incumbents fail, and a prescriptive toolkit for identifying, launching, and defending against disruptive threats. It identifies two disruption pathways — Low-End Disruption (targeting over-served, least-profitable customers with a 'good enough' lower-cost product that climbs upmarket as capability improves) and New-Market Disruption (enabling non-consumers who previously lacked the money, skills, or access to use a product at all). The Resources, Processes, and Values (RPV) framework explains why incumbents cannot respond internally: their processes and values are calibrated for sustaining innovation, and rational managers defund disruptive initiatives that look too small and too low-margin. The Jobs to Be Done (JTBD) framework provides the demand-side complement: customers 'hire' products to make progress in specific circumstances, and the job has functional, social, and emotional dimensions that reveal non-obvious competitive threats. Together, these frameworks produce a structured set of diagnostics — disruption typology classification, disruption threat assessments, RPV capability audits, Job Spec documents, and innovation portfolio reviews — that give practitioners analytical outputs, not just strategic intuitions.

The problem

Well-managed companies systematically miss disruptive threats because their best customers, highest-margin products, and rational resource allocation processes all point in the wrong direction. The over-served customers who get picked off first are the ones the sales team is relieved to lose. The disruptor's early product looks laughably inadequate by incumbent performance metrics. By the time the threat is undeniable, the disruptor has climbed upmarket and any internal response will be killed by the incumbent's own values — which define the disruptive market as too small, too low-margin, and too risky to pursue.

The solution

Stop misreading disruptive signals as ordinary competition. Apply Christensen's diagnostic frameworks to get a structured verdict — sustaining or disruptive, internal response or separate unit — with the specific mechanisms that explain why incumbents in your position have historically succeeded or failed.

You bring

A description of your market, business model, customer segments, and competitive situation
Details about an innovation idea, strategic initiative, or technology you want to classify and evaluate
Information about competitors you are tracking or disruption threats you suspect are forming
Your organization's current resource allocation priorities and financial metrics for innovation investments

You get

A formal disruption typology classification (sustaining / low-end disruptive / new-market disruptive) with rationale grounded in Christensen's screening criteria
A Disruption Threat Assessment mapping your over-served segments, non-consumer population, competitor performance trajectory, and value network vulnerabilities
An RPV Capability Audit determining whether a disruptive initiative should be pursued internally, in a separate unit, or fully spun out
A Job Spec document capturing the functional, social, and emotional dimensions of the customer's job, plus Four Forces analysis of switching barriers

In action

Watch the methodology work.

Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01  —  The same situation, two ways

Specimens A · B

Specimen AVague

Unaided

“Your product outperforms every cloud competitor on every benchmark that matters to your top accounts. You've lost a handful of small customers to cheaper alternatives, but those were low-margin accounts your sales team was already deprioritizing. Your enterprise pipeline is strong, your renewal rate is 94%, and your product roadmap is driven by requests from your five largest customers. The cloud competitors' product is missing three modules that any serious manufacturer requires.”

×Vague — nothing concrete to act on.

Specimen BCalibrated

With Disruptive Innovation

“The Disruption Threat Assessment confirms a low-end disruption in early progress: 35% of your installed base is over-served and paying for capabilities they never activate, while a non-consumer population three times your current market size exists just below your entry price point. The competitor's improvement trajectory puts them inside your mid-market customers' minimum requirements in approximately four years. The RPV Audit reveals your margin values will kill any internal cloud initiative — so you've designed a separate organizational unit with distinct financial metrics (revenue growth instead of gross margin), staffed with people who have experience in high-volume, low-touch sales models, and insulated from your enterprise P&L.”

◦Specific, grounded, and ends with one clear next step.

Fig.02  —  A real session, unedited

In-app · assistant

Disruptive InnovationClaude

Disruptive Innovation

Let's establish whether you're facing disruption or pursuing it. The Christensen framework starts with a precise question most strategists skip: are your competitors attacking your strengths, or are they serving customers you've stopped caring about? Which situation brings you here — an incumbent trying to assess a threat, an entrepreneur seeking a disruptive entry point, or an investor evaluating whether a startup qualifies as genuinely disruptive?

We're an incumbent. We sell ERP software to mid-market manufacturers — we've been the quality leader for 15 years. Lately these cloud-based competitors have been undercutting our price, but our enterprise customers say the competition's product is nowhere near our capability level. Our sales team isn't worried. I'm not sure whether to be.

Your sales team's confidence is the warning signal, not the reassurance. Christensen documented this pattern precisely: incumbents get the most dangerous comfort from their best customers, who are telling the truth about today's performance gap — but who are the wrong oracle for the disruption trajectory. Let me run the first diagnostic. In the past 18 months, which customer segments have you lost to these cloud competitors? Were they your highest-revenue accounts or your smallest, most price-sensitive, highest-support-cost customers — the ones your sales team quietly deprioritizes?

Honestly, mostly the smaller guys. Companies that pushed back on our pricing, needed a lot of hand-holding during implementation, and generated thin margins. Our sales team was almost relieved when they churned. We won a couple big enterprise renewals the same quarter so it didn't show up in the numbers.

That's the Low-End Disruption pattern in its early stage. Christensen called this 'asymmetric motivation' — you are structurally incentivized not to fight for these customers, and the disruptor is structurally incentivized to win them. Here's what makes it dangerous: each time you retreat upmarket, you hand the disruptor a larger installed base to fund product improvement. Now the critical question for the threat assessment: are these competitors improving their product year over year? Not are they at your level — are they on a trajectory that will get them to your mainstream customers' minimum requirements within 3–5 years?

Yes — one of them raised a big funding round last year and shipped an AI-driven analytics module that two of our mid-tier customers mentioned in their renewal conversations. They're moving faster than we expected.

This warrants a full Disruption Threat Assessment and an RPV Capability Audit. The threat assessment will formalize what you've just described: map the over-served segment size, estimate the non-consumer population (manufacturers running on spreadsheets or legacy systems who can't afford your offering at all), and plot the competitor's improvement trajectory against your mainstream customers' minimum performance thresholds. The RPV Audit is equally urgent — and most incumbents skip it. Even if leadership decides to launch a lower-cost cloud offering in response, your organization's current processes (built for 18-month implementation cycles) and values (calibrated for enterprise margins and complex customization) will systematically defund and slow the initiative until it fails. Christensen found that incumbents almost always need a separate organizational unit — different P&L, different success metrics, different hiring profiles — to pursue a disruptive response without the internal immune system killing it. Do you want to start with the threat assessment to quantify the risk, or the RPV Audit to assess your response capacity?

Threat assessment first — I need to know how serious this is before I take it to the board.

Good call. Let's build it systematically. I need four inputs: (1) Describe your lowest-margin customer segment — industry sub-type, company size, average deal size, and what they actually use your product for day-to-day. (2) Estimate what percentage of manufacturers in your total addressable market currently use no ERP or use spreadsheets — these are your non-consumers and the disruptor's true growth fuel. (3) What's the minimum performance level your mid-market customers actually require — not the full feature set you sell, but the baseline they'd accept? (4) What's your read on the cloud competitor's improvement rate — are they shipping meaningful capability every quarter, or is progress slower? With those inputs I can produce a disruption verdict with a confidence level and a timeline estimate for when the threat reaches your core business.

Reply to Disruptive Innovation…

What the skill is doing

01Disruption Typology Classification

02Disruption Threat Assessment

03RPV Capability Audit

Fig.03  —  The same skill, in the channel you already use

WhatsApp · live

9:41

DIDisruptive Innovationtyping…

Messages are end-to-end encrypted. No one outside of this chat can read them.

Today

We're an incumbent. We sell ERP software to mid-market manufacturers — we've been the quality leader for 15 years. Lately these cloud-based competitor…9:14✓✓

Let's establish whether you're facing disruption or pursuing it.9:14

Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

◦Reads the situation, names the pattern, returns one concrete next move.

◦Delivered in seconds, inside a conversation that already exists.

Specimen · WhatsApp Business API · live

Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Disruption Typology Classification

Apply Christensen's structured screening questions to classify any proposed innovation as sustaining, low-end disruptive, or new-market disruptive — and prescribe the organizational and financial response that matches. Misclassification is the most costly error practitioners make: sustaining innovations require different resource allocation, organizational structure, and success metrics than disruptive ones, and conflating them leads incumbents to defund genuine disruption attempts or over-invest in doomed me-too products.

◦ MethodBased on Christensen's disruptiveness screening questions from The Innovator's Solution (2003), which test whether a large non-consumer population or over-served segment exists, whether a viable lower-cost business model is achievable, and whether the opportunity is disruptive to all significant incumbents or only some.

CapabilityC-02

Disruption Threat Assessment

Map an incumbent's exposure to disruptive attack across four analytical dimensions: identification of over-served customer segments being ceded to entrants, sizing of the non-consumer population that entrants can unlock, tracing of competitor performance improvement trajectories against incumbent standards, and assessment of value network fragility. Produces a structured threat profile with a disruption verdict and timeline estimate.

◦ MethodImplements Christensen's signal-based analytical framework from Seeing What's Next (2004), which identifies four categories of disruptive signal: evidence of non-consumption, evidence of performance overshooting, enabling technology maturation that removes historical barriers, and incumbent retreat patterns that signal rational market abandonment.

CapabilityC-03

RPV Capability Audit

Assess an organization's Resources (what it has — people, capital, technology, brand), Processes (how it does things — patterns of coordination and decision-making), and Values (what it prioritizes — margin thresholds, customer definitions, project selection criteria) against the requirements of a disruptive initiative. Produces a verdict on whether the initiative can succeed internally, requires a separate organizational unit, or needs a full spin-out with its own funding and culture.

◦ MethodBased on Christensen's RPV framework from The Innovator's Solution — the core insight being that the processes and values that make incumbents excellent at sustaining innovation are structurally incompatible with disruptive innovation, and that the Resource Allocation Process (RAP) will rationally kill disruptive initiatives unless they are organizationally insulated from incumbent values.

CapabilityC-04

Jobs to Be Done Research Design

Structure a JTBD research protocol for discovering what customers truly 'hire' a product to accomplish — mapping functional, social, and emotional job dimensions, designing purchase-event interview guides, and applying the Four Forces of Progress (Push of Dissatisfaction + Pull of New Solution vs. Anxiety about Change + Inertia with Current Solution) to understand switching barriers. Produces a formal Job Spec document that defines what the product must deliver to win the hire.

◦ MethodImplements Christensen's Jobs to Be Done methodology from Competing Against Luck (2016), including the interview design for purchase-event research, the Four Forces analytical model, and the formal Job Spec template — which together move teams from demographic customer descriptions to circumstance-based behavioral understanding.

CapabilityC-05

Innovation Portfolio Review

Audit an organization's current innovation investment portfolio against Christensen's Good Money / Bad Money distinction — identifying disruptive-stage initiatives being held to mature-market financial standards (the primary mechanism by which incumbents kill their own disruption attempts). Produces a portfolio classification with stage-appropriate financial metrics and reallocation recommendations.

◦ MethodBased on Christensen's Good Money / Bad Money framework from The Innovator's Solution — disruptive investments require patient money (focused on growing revenue to confirm a business model), while sustaining innovations require impatient money (focused on improving profit on proven business models); applying mature-stage financial criteria to emergent-stage disruptive investments is the most common way incumbents defund the initiatives that could save them.

Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces

OutputD-01

Disruption Threat Assessment

A structured four-quadrant analysis mapping your incumbent's vulnerability: over-served segment identification (which customers are overpaying for capability they don't need), non-consumer population sizing (who currently lacks access and why), competitor performance trajectory (are they improving fast enough to reach your mainstream customers in 3–5 years?), and value network fragility (would responding require dismantling your supplier and channel relationships?). Includes a disruption verdict with confidence level.

OutputD-02

RPV Capability Audit Report

A diagnostic report assessing three organizational dimensions against a specific disruptive initiative: Resources (do you have the assets needed?), Processes (can your coordination patterns support a different value proposition?), and Values (will your margin thresholds, customer definitions, and project criteria allow the initiative to survive internal competition for resources?). Concludes with an organizational structure recommendation: internal, separate unit, or spin-out.

OutputD-03

Job Spec Document

A formal Jobs to Be Done output: a precisely worded job statement, decomposed functional/social/emotional job dimensions, a Four Forces analysis quantifying the push, pull, anxiety, and inertia forces acting on the switching decision, and a set of hiring criteria the product must satisfy to win the job. Replaces persona-based customer descriptions with a circumstance-based behavioral specification.

OutputD-04

Innovation Portfolio Map

A visual classification of your current innovation investments by type (sustaining vs. low-end disruptive vs. new-market disruptive), annotated with Good Money / Bad Money flags and stage-appropriate success metrics for each initiative. Highlights misallocations — typically disruptive-stage investments being evaluated against mature-market ROI thresholds — and provides reallocation recommendations.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Clayton Christensen

Clayton Christensen (1952–2020) was the Kim B. Clark Professor of Business Administration at Harvard Business School and the most cited management theorist of his era. He introduced disruptive innovation theory in his landmark 1995 HBR article 'Disruptive Technologies: Catching the Wave' and developed it through seven major books, including The Innovator's Dilemma — named by the Economist as one of the six most important business books ever written. He co-founded Innosight, a global strategy consulting firm dedicated to applying his frameworks, and Rose Park Advisors, an investment fund that used disruption theory as its investment lens.

Status · Inspired by Clayton Christensen’s work — not yet claimed. Are you Clayton Christensen?

Primary sourceS-01

The Innovator's Dilemma (1997) and The Innovator's Solution (2003)

by Clayton Christensen

Harvard Business School Professor; co-founder of Innosight consulting; author of The Innovator's Dilemma, named by The Economist as one of the six most important business books ever written.

Read the original ↗

Citationhbr.org

In the build queue

Be first to run it.

Disruptive Innovation is being built right now. Leave your email and we’ll tell you the moment it goes live.

Notify meEmail

At launchWe're an incumbent in [industry] and smaller, cheaper competitors are picking off our lowest-margin customers. Our sales team isn't worried because the competitors' products are still below our quality level. Can you run the Christensen disruption diagnostic to tell me whether this is genuine Low-End Disruption in progress or just ordinary competition?