The Innovator’s Solution by Clayton M. Christensen and Michael E. Raynor, published in 2003, is the practical sequel to The Innovator’s Dilemma. The first book explained why great companies lose to disruptive newcomers. This one asks how a manager or founder can create that kind of growth on purpose. Raynor, then a consultant at Deloitte, worked with Christensen to turn the theory into guidance for building new businesses.
What is The Innovator’s Solution about?
The authors argue that new growth looks random only because managers use the wrong theories. If you understand the forces at work, you can predict which ventures are likely to succeed and shape your plans to match. The book walks through the decisions every new business faces and shows how disruption theory answers each one.
It splits disruption into two types. Low-end disruption serves customers who are getting more than they need from current products and would happily pay less for something simpler. New-market disruption reaches people who could not use the existing products at all because of cost, skill or access. Both give newcomers room because incumbents have little reason to fight back.
The middle chapters cover which customers to target, how to define the product around the job customers want done, and when to build everything yourself versus relying on outside suppliers. The authors argue that tightly linked, interdependent designs win while a product is still not good enough, and modular designs with standard parts win once performance exceeds what buyers need. The final chapters deal with money, senior managers and the processes that make large companies kill promising projects.
What are the main lessons for founders?
- Pick your type of disruption. Decide whether you serve overserved customers at the low end or people who use nothing today. Each calls for a different product and price.
- Segment by the job. Ask what job a customer hires your product to do, and design around that instead of age, income or industry codes.
- Compete against nothing. The easiest early customers are those whose alternative is doing without. They judge you against their current struggle, not against the market leader.
- Choose your architecture for the stage. When the product still falls short, control the parts that matter most. Once it is good enough, open up and use standard components.
- Spend like a startup. The authors warn against large early budgets that demand fast scale. Aim for early profit on a small base and let growth follow.
Who should read The Innovator’s Solution?
Founders who already know The Innovator’s Dilemma and want a method, and teams building a cheaper or simpler alternative to an established product. It also suits corporate venture builders who must protect a new unit from the parent company’s habits. The jobs-to-be-done chapter alone is worth the read for anyone working on positioning.
Skip it if you have not read the first book or a good summary of it. The sequel assumes you know the vocabulary and moves quickly.
How do you put The Innovator’s Solution to work this week?
- Write one sentence describing the job your customers hire your product to do, in their words, without naming your product.
- List the people who currently do without any solution for that job and talk to 3 of them.
- Decide which parts of your product you must control and which you can buy off the shelf, and note why.
To capture what you learn about customer jobs and the gaps they face, use the free Lean Canvas tool on Fe/male Switch.
Where does The Innovator’s Solution fall short?
The book is written mainly for managers inside large firms, so many chapters on senior executives and budgeting feel remote to a small founding team. The examples come from the late 1990s and early 2000s and some predictions did not age well. The theory is elegant but hard to apply before the fact, since it is easier to label a disruption once it has happened. The criticism of the original case selection in The Innovator’s Dilemma applies here too. For a more hands-on way to map customer jobs, pair it with Value Proposition Design.