What is Competing Against Luck about?

Competing Against Luck is Clayton Christensen's most complete development of the Jobs to Be Done framework, which he introduced briefly in The Innovator's Solution. The core argument is that most companies innovate through a process that resembles luck — adding features, improving specifications, conducting demographic research — rather than through a disciplined understanding of why customers actually buy the things they buy. Jobs to Be Done provides an alternative: customers hire products to accomplish specific jobs in their lives, and understanding the job, not the customer's profile, is what drives reliable innovation.

The jobs framework reframes what a competitor is. A product doesn't just compete with similar products; it competes with anything else the customer might hire to do the same job. Milkshakes compete with bananas and bagels, not just other milkshakes, when the job is to get through a boring morning commute without getting hungry. Understanding the competing hires opens up the design space for improvement in ways that traditional competitive analysis misses entirely.

Christensen distinguishes between functional, social, and emotional dimensions of every job. A functional job is the practical task; the social job is about how doing it makes you appear to others; the emotional job is about how it makes you feel. Products that address all three dimensions create stronger loyalty than products that address only the functional dimension. This is why some products that are functionally inferior become market leaders — they win on social or emotional dimensions that their functional competitors ignore.

The book also addresses the organizational challenge: building a company that consistently identifies and solves the right jobs requires processes, metrics, and language that most organizations don't have. The Jobs to Be Done framework is not just a product insight — it is an organizational capability that must be deliberately built. The last section on organizational implications is the most challenging to implement and the most commonly skipped.