Competing Against Luck: The Story of Innovation and Customer Choice
Christensen's Jobs-To-Be-Done framework finally given book-length treatment — the argument that customers do not buy products, they "hire" them to make progress in their lives, and that understanding the job tells you more than any demographic or segmentation.
The milkshake example (commuters hiring a milkshake for a boring morning drive) is probably the most famous concrete illustration of the idea in the literature.
For product direction the book is a useful antidote to feature thinking: most product conversations are about what to build, while JTBD forces the prior question of what progress the customer is trying to make.
Christensen's prose is characteristically measured. Read alongside Ulwick's What Customers Want for the operational companion.
Central argument
Christensen and co-authors argue that innovation fails at high rates not because of poor execution but because companies misunderstand why customers make choices. The core thesis is that customers 'hire' products to accomplish a specific job — to make progress in a particular circumstance — and that this causal mechanism explains purchase behavior better than demographic profiles or product attributes. The famous milkshake example illustrates the point: commuters hired a thick, slow milkshake to make a boring drive more tolerable, a job invisible to any conventional segmentation. Knowing the job, including its functional, emotional, and social dimensions, is what makes innovation predictable rather than lucky.
Critique
The framework is powerful as a diagnostic lens but underdeveloped as an operational method — the book offers limited guidance on how to rigorously identify and validate jobs at scale, leaving practitioners with an evocative metaphor more than a repeatable process. There is also a latent tension in the theory: JTBD assumes jobs are relatively stable while the contexts in which people try to make progress shift constantly, especially in digital environments where new affordances rapidly reshape what 'progress' even means. Ulwick's outcome-driven approach, which Christensen conspicuously does not engage with despite the shared intellectual lineage, addresses some of this operational gap.
Why it matters for product
For a product leader, JTBD reframes the fundamental unit of discovery: instead of asking what features users request or what personas need, the prior question becomes what progress a specific person is trying to make in a specific circumstance — which directly challenges how most product teams structure roadmap conversations and prioritization. This has concrete consequences for metrics: if you define success around job completion rather than engagement or feature adoption, you get a different signal about whether the product is actually working. It also has implications for segmentation in strategy — grouping customers by the job they are hiring for, rather than by firmographic or behavioral cohorts, can reveal underserved markets that conventional analysis masks.