One-page summary · 2 min read
HBR's 10 Must Reads on Innovation
by Harvard Business Review, Peter F. Drucker, Clayton M. Christensen
The big idea
Innovation isn't a flash of inspiration, it's a discipline of specific, learnable practices, systematic opportunity-scanning, disciplined project evaluation, and structural protection from the core business, that determines whether creativity actually turns into results.
Developed by Rita McGrath and Ian MacMillan and featured in the collection, this is a planning method for ventures built on uncertain assumptions: instead of a fixed forecast-based business plan, teams state their assumptions explicitly, define the specific milestones that would confirm or kill those assumptions, and budget in small stages tied to hitting those checkpoints, deliberately building in the ability to reverse course cheaply rather than over-committing to an unproven bet.
One of ten distinct essay-level frameworks in the anthology; Drucker's seven sources of innovation, the featured article, and Christensen's disruption concepts are separate, equally central tools in the same book.
Key ideas
The discipline of innovation
Systematic innovation means monitoring seven specific sources of opportunity, from unexpected successes and failures to demographic shifts, rather than waiting for a stroke of genius.
Innovation's classic traps
Companies repeatedly fail at innovation for predictable, avoidable reasons, including misjudging what customers actually value and over-relying on existing customer feedback for breakthrough bets.
How GE disrupted itself
Reverse innovation, building stripped-down products for emerging markets first, then adapting them for developed markets, can open growth that traditional top-down R&D misses.
Is it real? Can we win? Is it worth doing?
A simple three-question screen helps leaders kill weak innovation bets early instead of letting sunk-cost thinking carry them forward.
The customer-centered innovation map
Innovation should be organized around the sequence of a customer's experience with a product or service, not around internal departmental boundaries.
Six myths of product development
Common assumptions, like a fast development process yields fast results, or more people mean faster progress, are frequently wrong and lead teams to optimize the wrong things.
Try it this week
- Run the seven-sources scan against your own team: which source, industry changes, process needs, demographic shifts, have you been ignoring?
- Pick one active project and apply the three-question test: is it real, can we win, is it worth doing? Kill or double down based on honest answers.
- Write down the assumptions behind your riskiest current initiative, then define the cheapest possible test for the shakiest one.
- Map a customer's full journey with your product end-to-end and note where your internal team boundaries are creating friction.
Is it for you?
Best for
- Managers and executives wanting condensed access to foundational innovation thinking without reading full books
- Teams designing an innovation process or portfolio-review system
Less useful if
- Readers wanting a single unified narrative, since this is ten standalone essays from different decades and authors
- Readers seeking very current case studies, since several essays are decades-old classics