Competing Against Luck

Competing Against Luck argues that innovation feels random because companies usually study the wrong unit of demand. They measure customers, markets, product categories, satisfaction scores, and feature preferences, then hope those correlations reveal what to build. Christensen, Hall, Dillon, and Duncan say the more useful question is causal: what progress is a person or organization trying to make in a particular circumstance, and what solution do they hire to make that progress?

That shift is the book’s main contribution. It does not say customer data is useless. It says most customer data describes who bought, what they bought, or how they rated it, while leaving the reason for the choice unexplained. A demographic segment may correlate with a purchase, but it does not cause the purchase. A product category may show where a company competes on a shelf, but it may not show what the customer was actually comparing in the moment of decision. The “job to be done” is meant to reveal that moment: the struggle, aspiration, context, alternatives, anxieties, and social meaning that make one solution feel worth hiring and another worth firing.

Demand lives in the circumstance, not in the customer profile

A job is not a task in the narrow sense. It is the progress someone seeks when a circumstance makes the current state unsatisfactory. The word “progress” matters because the customer is moving from one condition to another, not merely buying an object or completing a function. The word “circumstance” matters because the same person can hire different solutions at different times, and the same product can be hired for different jobs.

This is why the theory resists ordinary segmentation. A customer’s age, income, role, or industry may help locate a pattern, but it rarely explains the pressure that produced a purchase. Two people with similar profiles may buy for different reasons; two people with different profiles may hire the same product for the same job. Likewise, a product category can hide true competition. A company may think it competes with other products that look like its own, while customers compare it with routines, workarounds, or unrelated objects that satisfy the same progress.

The book’s milkshake example makes this concrete. Researchers studying a fast-food chain observed that many milkshakes were bought early in the morning by commuters, taken to cars, and consumed alone. Interviews showed that the milkshake was not simply a dessert or beverage in that circumstance. It helped make a long commute less boring, occupied one hand, fit the cupholder, stayed relatively clean, and delayed hunger. The alternatives included bananas, bagels, donuts, coffee, candy, and similar options, not just other milkshakes.

The same milkshake could be hired later for a different job, such as a parent-child treat. That distinction is not cosmetic. If a company improves the product for the commute job, it may emphasize thickness, neatness, portability, and staying power. If it improves the product for the treat job, speed, indulgence, and the parent’s emotional role may matter differently. The category stayed the same; the job changed.

The job includes functional, social, and emotional progress

A job has functional dimensions, but the book warns against reducing it to functional performance. Customers also care about how a choice makes them feel and how it affects their relationships or identity. A product may solve the practical problem and still fail if it creates anxiety, embarrassment, guilt, or social friction. Conversely, a solution that looks technically inferior may win because it handles the emotional or social side of the job better.

The condominium example in the book shows this more clearly than a feature checklist could. A Detroit-area builder was targeting downsizing retirees and divorced single parents with attractive units and luxury finishes, yet visits were not converting into sales. Bob Moesta’s interviews with actual buyers revealed that the issue was not simply floor plans or finishes. The dining-room table symbolized family continuity and the difficulty of leaving a home full of memory and identity.

That finding changed the nature of the problem. The job was not merely “buy a smaller home.” It was to make a major life transition without severing family meaning, memory, and self-conception. The builder’s response included larger dining areas, storage, moving help, and a sorting room. Those changes reduced the anxiety of transition rather than merely adding luxury. The product was still a condominium, but the value was organized around helping people move from one life stage to another.

This is the part of Jobs to Be Done that is easy to miss. The functional question asks whether the solution can do the task. The social and emotional questions ask whether the customer can live with the choice. In many important purchases, especially those involving transition, risk, status, family, money, or identity, those questions are inseparable. A team that interviews only for desired features may hear requests for bigger rooms, better finishes, or lower price, while missing the deeper obstacle: the customer is trying to preserve continuity while changing circumstances.

Switching depends on four forces, not need alone

The book’s hiring metaphor is useful only if it includes the forces that make switching happen or stall. Customers do not adopt a new solution simply because they have a need. They move when the pressure of the current situation and the attraction of a new solution overcome the forces that keep them where they are.

The book’s framework can be stated as a compact decision rule:

• Strengthen the push away from the current situation by understanding the struggle that makes the old way unacceptable.
• Strengthen the pull of the new solution by showing how it enables the desired progress.
• Weaken the habit of the present by making the new behavior fit the customer’s context.
• Weaken anxiety about the new solution by reducing risk, confusion, identity threat, and switching burden.

This is not a mathematical formula. The book presents it as a managerial way to reason about causation in customer choice, grounded in observation and interviews rather than as a guaranteed forecasting model. Its usefulness is diagnostic: when a promising product does not sell, the failure may be in any of the four forces. The customer may not feel enough push. The new offer may not be compelling enough. The old routine may be too convenient. The new solution may create too much uncertainty.

That qualification matters because a superficial version of Jobs to Be Done can become just another slogan. Saying customers “hire” products is not enough. A team has to identify the circumstance, the progress sought, the current workaround, the competing alternatives, and the anxieties that surround the switch. Otherwise, it may define a job that sounds plausible but does not explain behavior.

The milkshake case again shows why competition is broader than the category. If the morning job is to make a commute less boring while delaying hunger cleanly, then a banana competes because it is portable and easy, but may be consumed too quickly. A bagel competes, but may be messy or inconvenient in a car. The point is not that every product is a competitor to every other product. The point is that competition is set by the job in the circumstance.

Better innovation organizes the experience around the job

The book’s argument is often summarized as a product research method, but its implications reach beyond features. If customers hire a solution to make progress, then the whole experience matters: how the customer discovers the solution, decides to trust it, buys it, starts using it, explains it to others, and stops worrying about the old problem. A company can differentiate by organizing its processes, measures, and brand around the job rather than around internal categories.

That is why the condominium response included moving help and a sorting room, not only product changes inside the unit. Those elements belonged to the job because the customer’s struggle was the transition itself. The customer was not merely evaluating square footage; they were trying to cross an emotional and logistical threshold. The surrounding experience reduced friction that a conventional product specification might never capture.

This also changes how a company should listen. Asking customers what features they want can produce useful input, but it can also trap the team inside the current category. Asking about a recent switch, a failed attempt, or the moment dissatisfaction became strong enough to act is more likely to reveal causality. What was happening? What did the person try before? What made the old solution inadequate? What attracted them to the new one? What nearly stopped them? Those questions follow from the book’s theory because they focus on the forces of progress rather than on abstract preference.

The discipline is to keep the unit of analysis stable. If the team starts with a job, then product design, onboarding, messaging, channel choices, service policies, and success metrics should all be judged by whether they help the customer make that progress. If the team drifts back to internal measures alone, it may optimize the product while neglecting the actual hiring decision.

The theory narrows uncertainty by explaining choice

Competing Against Luck does not claim that innovation can be made risk-free. It claims that some uncertainty is self-inflicted because companies confuse correlation with causation. They collect more data about customers and products, but fail to explain why a choice happens in a circumstance. Jobs to Be Done is the book’s remedy: find the progress sought, locate it in context, include functional, social, and emotional dimensions, and study the forces that enable or block switching.

The practical consequence is a different definition of what a company is building. It is not only building a product in a category. It is building a way for customers to make progress. That progress may involve performance, convenience, identity, reassurance, transition, or relief. The solution may compete with products that look similar, with products that look unrelated, or with the customer’s current habit of doing nothing.

The book is strongest when used as a causality lens for real customer behavior: observed purchases, switch stories, interviews with actual buyers, and analysis of the old solutions customers fire. It is weaker when reduced to invented job statements detached from circumstance. The difference is the difference between naming a desire and explaining a decision. Innovation becomes less dependent on luck when teams can explain why the customer would change.