The Innovator's Solution by Christensen and Raynor — Cliff Notes Summary

👁 0 views📖 2,839 words⏱ 13 min read5/31/2026

Direct Answer

The Innovator's Solution by Clayton M. Christensen and Michael E. Raynor (Harvard Business Review Press, 2003) is the operating playbook sequel to Christensen's 1997 classic The Innovator's Dilemma (summarized at bs0047).

Where the original explained why great companies fail to disruption — their resource-allocation systems rationally starve low-margin disruptive threats until it's too late — this sequel answers the harder question: how do you actually BUILD a disruptive business, and how do you avoid being disrupted yourself? The book introduces what became Christensen's most-cited contribution to business thinking — the Jobs-to-be-Done framework ("customers don't buy products — they hire them to do a job") — plus the Resources-Processes-Values (RPV) diagnostic, the 9-box disruption screen, the modularity/integration cycle, and the "be patient for growth, impatient for profit" capital discipline rule.

Less famous than the original, The Innovator's Solution is the more actionable book — and its frameworks now anchor modern product strategy (Marty Cagan's INSPIRED bs0190, Teresa Torres' Continuous Discovery bs0193) and B2B sales discovery ("what JOB are you HIRING our product to do?").

1. Part One — The Growth Imperative (Chapters 1-2)

1.1 Chapter 1 — The Growth Imperative

Christensen and Raynor open with the data: only one company in ten sustains above-average growth for more than a few years. The market savagely punishes growth stalls — a single missed growth target typically erases 30-50% of market capitalization that the firm never recovers.

Yet the corporate-finance machinery that great companies build to defend their core business is the same machinery that kills new growth — because new businesses look small, low-margin, and risky next to a mature core. The book's central premise: predictably building new-growth businesses requires breaking the rules the core business depends on.

1.2 Chapter 2 — How Can We Beat Our Most Powerful Competitors?

The chapter sorts every innovation into one of three categories using what the authors call the three-circles disruption screen:

Sustaining innovations — better products sold at better margins to existing customers. Incumbents win these almost every time.
Low-end disruption — a "good enough" product that targets the overserved customer at the bottom of the market, then improves upward (Korean steel mini-mills, Walmart, southwest discount airlines).
New-market disruption — a product that targets nonconsumers — people who previously couldn't afford or didn't have the skill to use the existing solution (Sony transistor radio, personal computer, Canon desktop copier).

The book's strategic prescription is blunt: never attack an incumbent head-on with a sustaining innovation. You will lose. Either disrupt from below or create a new market the incumbent doesn't see.

2. Part Two — The Customer-Side Frameworks (Chapters 3-4)

2.1 Chapter 3 — What Products Will Customers Want to Buy? (The Jobs-to-be-Done Breakthrough)

This is the chapter that changed product strategy. Christensen's verbatim teaching: "Customers don't buy products — they hire them to do a Job-to-be-Done." The traditional model — segment customers by demographic (age, income, industry) or product attribute — is predictively useless.

People in the same demographic hire radically different products for radically different jobs.

The famous example: the milkshake job at a fast-food chain. Demographic analysis (more chocolate, thicker, cheaper) failed to grow sales. Ethnographic study revealed the dominant morning milkshake job: lonely commuters needed something to occupy a 30-minute drive that wouldn't crumb, spill, or be eaten in two minutes — the milkshake's competition wasn't other milkshakes, it was bananas, bagels, and boredom.

Reformulated for the morning job (thicker, fruit chunks, faster checkout), sales grew dramatically. The afternoon job (parent placating a tired child) demanded the opposite reformulation.

The framework operationalizes: identify the functional, emotional, and social dimensions of the job, find where existing solutions perform the job imperfectly, and build a product whose every feature aligns to the job.

2.2 Chapter 4 — Who Are the Best Customers for Our Products?

The right initial customers for a disruptive product are not the same as the right customers for a sustaining business. Christensen identifies three populations:

Overserved customers — at the high end, paying for performance they don't need. The low-end disruption target.
Undershot customers — at the high end, still hungry for more performance. The sustaining-innovation target.
Nonconsumers — currently shut out of the category entirely by price, complexity, or skill barrier. The new-market disruption target.

The strategic error incumbents make: they look at their existing customer surveys and conclude the disruptive product is "worse" — because their customers are by definition not in the nonconsuming or overserved populations. Listening to your best current customers is exactly the trap that kills you.

3. Part Three — The Product Architecture Decisions (Chapters 5-6)

3.1 Chapter 5 — Getting the Scope of the Business Right (The Modularity/Integration Cycle)

Christensen's most underappreciated framework predicts industry waves of consolidation and unbundling. The rule: when a product is not yet good enough, integrated architectures win. When a product overshoots customer needs, modular architectures win.

Why: when performance is the binding constraint, only a vertically integrated firm controlling every interface can squeeze out the last increments of performance (early mainframes — IBM integrated; early autos — Ford integrated). Once performance overshoots, the basis of competition shifts to speed, customization, and convenience, which modular ecosystems serve better (PC era — Intel/Microsoft/Dell horizontal stack beat integrated mainframe).

The strategic implication: ask where on the performance-vs-demand curve your category sits today, and bet accordingly. AI-foundation-model integration in 2024-2026 looks structurally like early mainframes — performance is not yet good enough, so integrated stacks (OpenAI, Anthropic, Google) win. Modularity will follow when overshoot arrives.

3.2 Chapter 6 — How to Avoid Commoditization

When modularization arrives, profits do not disappear — they migrate to whichever stage of the value chain is still not good enough. Christensen calls this the law of conservation of attractive profits. Examples: in the PC value chain, profits migrated from systems integrators (IBM) to microprocessors (Intel) and operating systems (Microsoft).

In personal music, profits migrated from device makers to platform/ecosystem (Apple iTunes / App Store). The strategic question every operator must ask: where will the next not-good-enough bottleneck appear, and can we own that stage?

4. Part Four — The Organization-Side Frameworks (Chapters 7-9)

4.1 Chapter 7 — Is Your Organization Capable of Disruptive Growth? (The RPV Framework)

The single most useful diagnostic Christensen ever published: Resources, Processes, and Values determine what an organization can and cannot do.

Resources — people, cash, equipment, IP, brands. Most fungible. Easiest to change.
Processes — how the organization converts resources into outputs (hiring, product development, budgeting, sales motion). Hardened over years. Hard to change.
Values — the criteria by which the organization decides what is important (gross margin floors, customer-size minimums, deal-size thresholds, growth-rate hurdles). The most ossified. The hardest to change.

The reason great companies fail at disruption: their values were optimized for the core business and literally cannot tolerate the low-margin, small-market, slow-growth characteristics of an early disruptive business. A 60-point-gross-margin enterprise software company cannot psychologically authorize a 20-point-margin disruptive offering — its sales force won't sell it, its finance team won't fund it, its product team won't staff it.

The prescription: disruptive ventures need a separate organization with its own RPV.

4.2 Chapter 8 — Managing the Strategy Development Process

Strategy in a disruptive business is emergent, not deliberate. The plan you write at funding will be wrong — the customer, the job, the price point, and the channel will all shift in the first 18 months. The book prescribes a two-track approach: plan-to-learn in the early stage (small bets, fast iteration, explicit hypothesis testing) and plan-to-execute once a viable strategy emerges.

Trying to run a disruptive venture with the same 5-year financial-plan discipline as the core business is the most common cause of failure.

4.3 Chapter 9 — There Is Good Money and There Is Bad Money (Capital Discipline)

Christensen's most quoted operating principle: "Be patient for growth, impatient for profit. Flip this and disruption dies."

The reasoning: early disruptive ventures cannot accurately forecast revenue (customers and jobs are still being discovered), but they can and must demonstrate unit economics quickly. Capital that demands fast revenue growth pushes the venture into the incumbent's existing customers (where the venture loses) instead of letting it find its true nonconsuming or overserved customers.

Capital that tolerates ongoing losses lets the venture burn through cash without ever proving the economics work.

The right pattern: small initial check, demand profitability per transaction quickly, then scale only what works. The wrong pattern (the one that killed countless dot-coms and SPAC darlings): massive initial check, demand hockey-stick revenue, ignore unit economics. WeWork, Quibi, and Better.com are textbook "bad money" failures by Christensen's standard.

5. Part Five — The Role of Senior Executives (Chapter 10)

5.1 Chapter 10 — The Role of Senior Executives in Leading New Growth

The CEO's irreducible job in a disrupting company: stand at the interface between the core and the new venture and protect the new venture's separate RPV. Specifically:

Decide which decisions belong to the core organization (most) and which belong to the new venture (the ones the core would reflexively kill).
Personally coach the leaders of the new venture on emergent-strategy discipline.
Maintain a portfolio of growth bets — not one big strategic gamble — so that learning from the failures funds the eventual winner.

The closing argument: most CEOs delegate disruption to a corporate-venturing group, then judge it by core-business metrics. That guarantees failure. Disruption is the CEO's job, not a department's.

flowchart TD A[Identify a Job-to-be-Done] --> B{Performed Imperfectly Today?} B -->|No| C[Pass — sustaining territory] B -->|Yes| D{Who is the Customer?} D --> E[Overserved — Low-End Disruption] D --> F[Nonconsumer — New-Market Disruption] E --> G[Design Good-Enough Product at Lower Cost] F --> H[Design Simpler Product at Lower Skill Threshold] G --> I{Existing RPV Compatible?} H --> I I -->|No| J[Spin Out Separate Org with Own RPV] I -->|Yes| K[Rare — proceed inside core] J --> L[Be Patient for Growth, Impatient for Profit] K --> L L --> M[Prove Unit Economics at Small Scale] M --> N[Scale Only What Works] N --> O[Migrate Upmarket as Performance Improves]

6. Frameworks at a Glance

The frameworks from The Innovator's Solution now embedded in modern product, strategy, and sales practice:

Jobs-to-be-Done (JTBD) — the foundational customer-research lens of modern product management; powers Cagan's INSPIRED (bs0190), Torres' Continuous Discovery (bs0193), and Christensen's own follow-up Competing Against Luck (2016).
Three-Circles Disruption Screen — sustaining vs low-end vs new-market disruption; the test every strategy deck should run.
Resources-Processes-Values (RPV) — the org-capability diagnostic; explains why acquisitions of disruptive startups by incumbents almost always fail.
Modularity/Integration Cycle — predicts which industry stages will consolidate vs unbundle as performance overshoots.
Conservation of Attractive Profits — predicts where profits migrate when modularization arrives.
Be Patient for Growth, Impatient for Profit — the capital-discipline rule that separates real disruptors from cash-burning impostors.
Emergent vs Deliberate Strategy — the two-track approach to running a new venture before vs after product-market fit.

flowchart LR A[Find the Job-to-be-Done] --> B[Pick Disruption Type] B --> C[Design Product for the Job] C --> D[Spin Out with Separate RPV] D --> E[Impatient for Profit — Prove Unit Economics] E --> F[Patient for Growth — Let Strategy Emerge] F --> G[Scale What Works, Kill What Doesnt] G --> H[Migrate Upmarket as Performance Improves]

7. What Holds Up, What Has Aged

What still holds (2025-2027):

Jobs-to-be-Done is now foundational to product management — every PM bootcamp, every Cagan-school product-strategy doc, every modern discovery framework cites it. Competing Against Luck (Christensen, 2016) and Alan Klement's "Switch" interview methodology extend it.
The RPV framework still explains why incumbent attempts at disruption keep failing — Google killing Stadia (values mismatch with games-as-a-service), Disney's streaming margin pain (values built for box-office economics), every legacy bank's "innovation lab" theater.
The 2022-2025 AI wave is a textbook Christensen disruption case: GPT-class models are low-end disruption of search (Google) and new-market disruption of coding assistants (incumbent IDE vendors). Christensen's frameworks predict the dynamics cleanly.
"Be patient for growth, impatient for profit" has been brutally vindicated by the 2022-2024 unicorn die-off (WeWork, Convoy, Olive, Bird, Better.com — every one a violation of this rule).

What has aged or drawn pushback:

Jill Lepore's 2014 New Yorker piece "The Disruption Machine" argued Christensen's disruption theory has been over-applied as universal explanation for any market change. Fair critique — not every new entrant is a "disruptor" in Christensen's strict definition. Many are just better products.
Christensen's prediction that the iPhone would fail as a sustaining innovation famously didn't pan out — Apple's vertical-integration + ecosystem play didn't fit the original frame cleanly. He later acknowledged platform-economics complications.
The modularity-integration cycle has held up but moves slower than the book implied — categories can stay integrated for decades when ecosystem effects compound.
PLG (product-led growth) as a go-to-market model isn't well-handled by the original framework, though JTBD still applies to feature design inside a PLG product.

FAQ

How is this different from The Innovator's Dilemma (bs0047)? The Dilemma diagnoses why incumbents fail; the Solution prescribes how to build a disruptor and how to defend against being disrupted. The Dilemma is the more famous book; the Solution is the more actionable one.

Read the Dilemma for the theory, the Solution for the operating playbook.

What is Jobs-to-be-Done, in one sentence? A customer doesn't buy your product — they hire it to do a specific job that arose in a specific context, and they will fire it the moment a better-fitting product appears. Design and market to the job, not the demographic.

How does this apply to B2B sales discovery? Christensen's JTBD reframes the entire opening of a sales call. Instead of "what are your pain points?" the Challenger-tier question is "what job were you trying to get done when you started looking for a solution like ours?" The answer reveals the competing alternatives (often a spreadsheet, an existing tool, or doing nothing), the success criteria (functional + emotional + social), and the buying trigger — the three things MEDDPICC discovery has to surface anyway.

How does the RPV framework explain failed enterprise rollouts? When a deal stalls in implementation, it's almost never a Resources problem (the customer has the people, the budget, the tools). It's a Processes problem (their workflow doesn't accommodate your tool) or a Values problem (their organization doesn't actually believe the priority is high enough to disrupt entrenched habits).

Diagnose RPV during discovery — accounts with a fundamental Values mismatch should be disqualified, not pushed.

Is Christensen's disruption theory still credible after Jill Lepore's critique? Yes, with discipline. Lepore's fair point is that "disruption" became a buzzword applied to any change. The theory still works in the cases that fit the definition — low-end or new-market entrants with worse-on-traditional-metrics products that improve to overtake incumbents.

AI-foundation-model disruption of search (Google) and coding tools (legacy IDEs) is a textbook fit.

What should I do Monday morning after reading this? Three things. (1) Rewrite your top-three product discovery questions to start with "what job is the customer hiring our product to do?" (2) Audit any new-growth bet inside your company against the RPV test — is it being run with the core business's processes and values?

If yes, it will die. (3) Apply the "be patient for growth, impatient for profit" test to your own portfolio — anything burning cash without proven unit economics is bad money, regardless of how big the TAM looks on the slide.

Bottom Line

Read The Innovator's Solution if you build new businesses inside large companies, if you're a founder trying to disrupt an entrenched incumbent, or if you sell into accounts whose existing processes and values determine whether they can adopt your product. The book is less famous than its predecessor but vastly more useful — it gives you the Jobs-to-be-Done lens, the RPV diagnostic, the disruption-type screen, and the patient-for-growth/impatient-for-profit capital rule in a single coherent playbook.

Christensen's frameworks have held up better than almost any other strategy work from the 2000s, and the AI disruption wave of 2022-2026 is making them more relevant, not less.

Sources

Christensen, Clayton M. & Raynor, Michael E. — *The Innovator's Solution* (Harvard Business Review Press, 2003)
Christensen, Clayton M. — *The Innovator's Dilemma* (Harvard Business School Press, 1997) — predecessor, summarized at bs0047
Christensen, Clayton M. & Anthony, Scott D. & Roth, Erik A. — *Seeing What's Next* (HBR Press, 2004) — disruption-prediction companion volume
Christensen, Clayton M. & Hall, Taddy & Dillon, Karen & Duncan, David S. — *Competing Against Luck* (Harper Business, 2016) — definitive JTBD treatment
Cagan, Marty — *INSPIRED: How to Create Products Customers Love* (Wiley, 2017) — modern product-management application of JTBD, summarized at bs0190
Torres, Teresa — *Continuous Discovery Habits* (Product Talk, 2021) — JTBD-driven discovery cadence, summarized at bs0193
Lepore, Jill — "The Disruption Machine" (The New Yorker, June 2014) — the canonical critique of Christensen's theory's over-application
Harvard Business Review — Clayton Christensen retrospective and follow-up essays (2003-2020)
Klement, Alan — *When Coffee and Kale Compete* (NYC Publishing, 2016) — JTBD "Switch" interview methodology
Gartner — Hype Cycle and Emerging Tech research — applied disruption-pattern analysis (2020-2026)

Keep reading

Download:

### Direct Answer

**The Innovator's Solution** by **Clayton M. Christensen** and **Michael E. Raynor** (Harvard Business Review Press, 2003) is the operating playbook sequel to Christensen's 1997 classic **The Innovator's Dilemma** (summarized at bs0047). Where the original explained **why** great companies fail to disruption — their resource-allocation systems rationally starve low-margin disruptive threats until it's too late — this sequel answers the harder question: **how do you actually BUILD a disruptive business, and how do you avoid being disrupted yourself?** The book introduces what became Christensen's most-cited contribution to business thinking — the **Jobs-to-be-Done framework** ("customers don't buy products — they hire them to do a job") — plus the **Resources-Processes-Values (RPV) diagnostic**, the **9-box disruption screen**, the **modularity/integration cycle**, and the **"be patient for growth, impatient for profit"** capital discipline rule. Less famous than the original, **The Innovator's Solution is the more actionable book** — and its frameworks now anchor modern product strategy (**Marty Cagan's INSPIRED** bs0190, **Teresa Torres' Continuous Discovery** bs0193) and B2B sales discovery ("what JOB are you HIRING our product to do?").

## 1. Part One — The Growth Imperative (Chapters 1-2)

### 1.1 Chapter 1 — The Growth Imperative

Christensen and Raynor open with the data: **only one company in ten sustains above-average growth for more than a few years**. The market savagely punishes growth stalls — a single missed growth target typically erases **30-50% of market capitalization** that the firm never recovers. Yet the corporate-finance machinery that great companies build to defend their **core business** is the same machinery that **kills new growth** — because new businesses look small, low-margin, and risky next to a mature core. The book's central premise: **predictably building new-growth businesses requires breaking the rules the core business depends on.**

### 1.2 Chapter 2 — How Can We Beat Our Most Powerful Competitors?

The chapter sorts every innovation into one of three categories using what the authors call the **three-circles disruption screen**:

- **Sustaining innovations** — better products sold at better margins to existing customers. Incumbents win these almost every time.
- **Low-end disruption** — a "good enough" product that targets the **overserved** customer at the bottom of the market, then improves upward (Korean steel mini-mills, Walmart, southwest discount airlines).
- **New-market disruption** — a product that targets **nonconsumers** — people who previously couldn't afford or didn't have the skill to use the existing solution (Sony transistor radio, personal computer, Canon desktop copier).

The book's strategic prescription is blunt: **never attack an incumbent head-on with a sustaining innovation.** You will lose. Either disrupt from below or create a new market the incumbent doesn't see.

## 2. Part Two — The Customer-Side Frameworks (Chapters 3-4)

### 2.1 Chapter 3 — What Products Will Customers Want to Buy? (The Jobs-to-be-Done Breakthrough)

This is the chapter that changed product strategy. Christensen's verbatim teaching: **"Customers don't buy products — they hire them to do a Job-to-be-Done."** The traditional model — segment customers by **demographic** (age, income, industry) or **product attribute** — is **predictively useless**. People in the same demographic hire radically different products for radically different jobs.

The famous example: **the milkshake job** at a fast-food chain. Demographic analysis (more chocolate, thicker, cheaper) failed to grow sales. Ethnographic study revealed the dominant **morning milkshake job**: lonely commuters needed something to occupy a 30-minute drive that wouldn't crumb, spill, or be eaten in two minutes — the milkshake's competition wasn't other milkshakes, it was **bananas, bagels, and boredom**. Reformulated for the morning job (thicker, fruit chunks, faster checkout), sales grew dramatically. The **afternoon job** (parent placating a tired child) demanded the opposite reformulation.

The framework operationalizes: identify the **functional, emotional, and social dimensions** of the job, find where existing solutions perform the job **imperfectly**, and build a product whose every feature aligns to the job.

### 2.2 Chapter 4 — Who Are the Best Customers for Our Products?

The right initial customers for a disruptive product are **not the same** as the right customers for a sustaining business. Christensen identifies three populations:

- **Overserved customers** — at the high end, paying for performance they don't need. The low-end disruption target.
- **Undershot customers** — at the high end, still hungry for more performance. The sustaining-innovation target.
- **Nonconsumers** — currently shut out of the category entirely by price, complexity, or skill barrier. The new-market disruption target.

The strategic error incumbents make: they look at their **existing customer surveys** and conclude the disruptive product is "worse" — because their customers are by definition not in the nonconsuming or overserved populations. Listening to your best current customers is **exactly the trap that kills you**.

## 3. Part Three — The Product Architecture Decisions (Chapters 5-6)

### 3.1 Chapter 5 — Getting the Scope of the Business Right (The Modularity/Integration Cycle)

Christensen's most underappreciated framework predicts industry **waves of consolidation and unbundling**. The rule: **when a product is not yet good enough, integrated architectures win. When a product overshoots customer needs, modular architectures win.**

Why: when performance is the binding constraint, only a vertically integrated firm controlling every interface can squeeze out the last increments of performance (early mainframes — IBM integrated; early autos — Ford integrated). Once performance overshoots, the basis of competition shifts to **speed, customization, and convenience**, which modular ecosystems serve better (PC era — Intel/Microsoft/Dell horizontal stack beat integrated mainframe).

The strategic implication: ask **where on the performance-vs-demand curve** your category sits today, and bet accordingly. AI-foundation-model integration in 2024-2026 looks structurally like early mainframes — performance is not yet good enough, so integrated stacks (OpenAI, Anthropic, Google) win. Modularity will follow when overshoot arrives.

### 3.2 Chapter 6 — How to Avoid Commoditization

When modularization arrives, **profits do not disappear — they migrate** to whichever stage of the value chain is still not good enough. Christensen calls this the **law of conservation of attractive profits**. Examples: in the PC value chain, profits migrated from systems integrators (IBM) to microprocessors (Intel) and operating systems (Microsoft). In personal music, profits migrated from device makers to platform/ecosystem (Apple iTunes / App Store). The strategic question every operator must ask: **where will the next not-good-enough bottleneck appear, and can we own that stage?**

## 4. Part Four — The Organization-Side Frameworks (Chapters 7-9)

### 4.1 Chapter 7 — Is Your Organization Capable of Disruptive Growth? (The RPV Framework)

The single most useful diagnostic Christensen ever published: **Resources, Processes, and Values determine what an organization can and cannot do.**

- **Resources** — people, cash, equipment, IP, brands. Most fungible. Easiest to change.
- **Processes** — how the organization converts resources into outputs (hiring, product development, budgeting, sales motion). Hardened over years. Hard to change.
- **Values** — the criteria by which the organization decides what is **important** (gross margin floors, customer-size minimums, deal-size thresholds, growth-rate hurdles). The most ossified. The hardest to change.

The reason great companies fail at disruption: their **values** were optimized for the **core business** and **literally cannot tolerate** the low-margin, small-market, slow-growth characteristics of an early disruptive business. A 60-point-gross-margin enterprise software company **cannot psychologically authorize** a 20-point-margin disruptive offering — its sales force won't sell it, its finance team won't fund it, its product team won't staff it. The prescription: **disruptive ventures need a separate organization with its own RPV.**

### 4.2 Chapter 8 — Managing the Strategy Development Process

Strategy in a disruptive business is **emergent, not deliberate**. The plan you write at funding will be wrong — the customer, the job, the price point, and the channel will all shift in the first 18 months. The book prescribes a two-track approach: **plan-to-learn** in the early stage (small bets, fast iteration, explicit hypothesis testing) and **plan-to-execute** once a viable strategy emerges. Trying to run a disruptive venture with the same 5-year financial-plan discipline as the core business is the most common cause of failure.

### 4.3 Chapter 9 — There Is Good Money and There Is Bad Money (Capital Discipline)

Christensen's most quoted operating principle: **"Be patient for growth, impatient for profit. Flip this and disruption dies."**

The reasoning: early disruptive ventures cannot accurately forecast revenue (customers and jobs are still being discovered), but they **can and must** demonstrate unit economics quickly. Capital that demands fast revenue growth pushes the venture into the **incumbent's existing customers** (where the venture loses) instead of letting it find its true nonconsuming or overserved customers. Capital that tolerates ongoing losses lets the venture **burn through cash without ever proving the economics work**.

The right pattern: small initial check, demand profitability per transaction quickly, then scale only what works. The wrong pattern (the one that killed countless dot-coms and SPAC darlings): massive initial check, demand hockey-stick revenue, ignore unit economics. **WeWork, Quibi, and Better.com** are textbook "bad money" failures by Christensen's standard.

## 5. Part Five — The Role of Senior Executives (Chapter 10)

### 5.1 Chapter 10 — The Role of Senior Executives in Leading New Growth

The CEO's irreducible job in a disrupting company: **stand at the interface between the core and the new venture and protect the new venture's separate RPV**. Specifically:

- Decide **which decisions belong to the core organization** (most) and **which belong to the new venture** (the ones the core would reflexively kill).
- Personally **coach the leaders of the new venture** on emergent-strategy discipline.
- Maintain a **portfolio of growth bets** — not one big strategic gamble — so that learning from the failures funds the eventual winner.

The closing argument: most CEOs delegate disruption to a corporate-venturing group, then judge it by core-business metrics. That guarantees failure. Disruption is the CEO's job, not a department's.

```mermaid
flowchart TD
    A[Identify a Job-to-be-Done] --> B{Performed Imperfectly Today?}
    B -->|No| C[Pass — sustaining territory]
    B -->|Yes| D{Who is the Customer?}
    D --> E[Overserved — Low-End Disruption]
    D --> F[Nonconsumer — New-Market Disruption]
    E --> G[Design Good-Enough Product at Lower Cost]
    F --> H[Design Simpler Product at Lower Skill Threshold]
    G --> I{Existing RPV Compatible?}
    H --> I
    I -->|No| J[Spin Out Separate Org with Own RPV]
    I -->|Yes| K[Rare — proceed inside core]
    J --> L[Be Patient for Growth, Impatient for Profit]
    K --> L
    L --> M[Prove Unit Economics at Small Scale]
    M --> N[Scale Only What Works]
    N --> O[Migrate Upmarket as Performance Improves]
```

## 6. Frameworks at a Glance

The frameworks from **The Innovator's Solution** now embedded in modern product, strategy, and sales practice:

- **Jobs-to-be-Done (JTBD)** — the foundational customer-research lens of modern product management; powers **Cagan's INSPIRED** (bs0190), **Torres' Continuous Discovery** (bs0193), and Christensen's own follow-up **Competing Against Luck** (2016).
- **Three-Circles Disruption Screen** — sustaining vs low-end vs new-market disruption; the test every strategy deck should run.
- **Resources-Processes-Values (RPV)** — the org-capability diagnostic; explains why acquisitions of disruptive startups by incumbents almost always fail.
- **Modularity/Integration Cycle** — predicts which industry stages will consolidate vs unbundle as performance overshoots.
- **Conservation of Attractive Profits** — predicts where profits migrate when modularization arrives.
- **Be Patient for Growth, Impatient for Profit** — the capital-discipline rule that separates real disruptors from cash-burning impostors.
- **Emergent vs Deliberate Strategy** — the two-track approach to running a new venture before vs after product-market fit.

```mermaid
flowchart LR
    A[Find the Job-to-be-Done] --> B[Pick Disruption Type]
    B --> C[Design Product for the Job]
    C --> D[Spin Out with Separate RPV]
    D --> E[Impatient for Profit — Prove Unit Economics]
    E --> F[Patient for Growth — Let Strategy Emerge]
    F --> G[Scale What Works, Kill What Doesnt]
    G --> H[Migrate Upmarket as Performance Improves]
```

## 7. What Holds Up, What Has Aged

**What still holds (2025-2027):**
- **Jobs-to-be-Done** is now foundational to product management — every PM bootcamp, every Cagan-school product-strategy doc, every modern discovery framework cites it. **Competing Against Luck** (Christensen, 2016) and **Alan Klement's "Switch" interview methodology** extend it.
- **The RPV framework** still explains why incumbent attempts at disruption keep failing — Google killing Stadia (values mismatch with games-as-a-service), Disney's streaming margin pain (values built for box-office economics), every legacy bank's "innovation lab" theater.
- **The 2022-2025 AI wave** is a textbook Christensen disruption case: GPT-class models are low-end disruption of search (Google) and new-market disruption of coding assistants (incumbent IDE vendors). Christensen's frameworks predict the dynamics cleanly.
- **"Be patient for growth, impatient for profit"** has been brutally vindicated by the 2022-2024 unicorn die-off (WeWork, Convoy, Olive, Bird, Better.com — every one a violation of this rule).

**What has aged or drawn pushback:**
- **Jill Lepore's 2014 New Yorker piece "The Disruption Machine"** argued Christensen's disruption theory has been **over-applied** as universal explanation for any market change. Fair critique — not every new entrant is a "disruptor" in Christensen's strict definition. Many are just better products.
- **Christensen's prediction that the iPhone would fail** as a sustaining innovation famously didn't pan out — Apple's vertical-integration + ecosystem play didn't fit the original frame cleanly. He later acknowledged platform-economics complications.
- The **modularity-integration cycle** has held up but moves slower than the book implied — categories can stay integrated for decades when ecosystem effects compound.
- **PLG (product-led growth)** as a go-to-market model isn't well-handled by the original framework, though JTBD still applies to feature design inside a PLG product.

## FAQ

**How is this different from The Innovator's Dilemma (bs0047)?** The Dilemma diagnoses **why incumbents fail**; the Solution prescribes **how to build a disruptor and how to defend against being disrupted**. The Dilemma is the more famous book; the Solution is the more actionable one. Read the Dilemma for the theory, the Solution for the operating playbook.

**What is Jobs-to-be-Done, in one sentence?** A customer doesn't buy your product — they hire it to do a specific job that arose in a specific context, and they will fire it the moment a better-fitting product appears. Design and market to the job, not the demographic.

**How does this apply to B2B sales discovery?** Christensen's JTBD reframes the entire opening of a sales call. Instead of "what are your pain points?" the Challenger-tier question is **"what job were you trying to get done when you started looking for a solution like ours?"** The answer reveals the **competing alternatives** (often a spreadsheet, an existing tool, or doing nothing), the **success criteria** (functional + emotional + social), and the **buying trigger** — the three things MEDDPICC discovery has to surface anyway.

**How does the RPV framework explain failed enterprise rollouts?** When a deal stalls in implementation, it's almost never a Resources problem (the customer has the people, the budget, the tools). It's a **Processes** problem (their workflow doesn't accommodate your tool) or a **Values** problem (their organization doesn't actually believe the priority is high enough to disrupt entrenched habits). Diagnose RPV during discovery — accounts with a fundamental Values mismatch should be disqualified, not pushed.

**Is Christensen's disruption theory still credible after Jill Lepore's critique?** Yes, with discipline. Lepore's fair point is that "disruption" became a buzzword applied to any change. The theory still works **in the cases that fit the definition** — low-end or new-market entrants with worse-on-traditional-metrics products that improve to overtake incumbents. AI-foundation-model disruption of search (Google) and coding tools (legacy IDEs) is a textbook fit.

**What should I do Monday morning after reading this?** Three things. **(1)** Rewrite your top-three product discovery questions to start with "what job is the customer hiring our product to do?" **(2)** Audit any new-growth bet inside your company against the RPV test — is it being run with the core business's processes and values? If yes, it will die. **(3)** Apply the "be patient for growth, impatient for profit" test to your own portfolio — anything burning cash without proven unit economics is bad money, regardless of how big the TAM looks on the slide.

## Bottom Line

Read **The Innovator's Solution** if you build new businesses inside large companies, if you're a founder trying to disrupt an entrenched incumbent, or if you sell into accounts whose existing processes and values determine whether they can adopt your product. The book is less famous than its predecessor but vastly more useful — it gives you the **Jobs-to-be-Done lens, the RPV diagnostic, the disruption-type screen, and the patient-for-growth/impatient-for-profit capital rule** in a single coherent playbook. Christensen's frameworks have held up better than almost any other strategy work from the 2000s, and the AI disruption wave of 2022-2026 is making them more relevant, not less.

## Sources

- Christensen, Clayton M. & Raynor, Michael E. — *The Innovator's Solution* (Harvard Business Review Press, 2003)
- Christensen, Clayton M. — *The Innovator's Dilemma* (Harvard Business School Press, 1997) — predecessor, summarized at bs0047
- Christensen, Clayton M. & Anthony, Scott D. & Roth, Erik A. — *Seeing What's Next* (HBR Press, 2004) — disruption-prediction companion volume
- Christensen, Clayton M. & Hall, Taddy & Dillon, Karen & Duncan, David S. — *Competing Against Luck* (Harper Business, 2016) — definitive JTBD treatment
- Cagan, Marty — *INSPIRED: How to Create Products Customers Love* (Wiley, 2017) — modern product-management application of JTBD, summarized at bs0190
- Torres, Teresa — *Continuous Discovery Habits* (Product Talk, 2021) — JTBD-driven discovery cadence, summarized at bs0193
- Lepore, Jill — "The Disruption Machine" (The New Yorker, June 2014) — the canonical critique of Christensen's theory's over-application
- Harvard Business Review — Clayton Christensen retrospective and follow-up essays (2003-2020)
- Klement, Alan — *When Coffee and Kale Compete* (NYC Publishing, 2016) — JTBD "Switch" interview methodology
- Gartner — Hype Cycle and Emerging Tech research — applied disruption-pattern analysis (2020-2026)

Was this helpful?

⌬ Apply this in PULSE

Gross Profit CalculatorModel margin per deal, per rep, per territory

Related in the library