Clayton Christensen and his co-authors argue that customers do not simply buy products; in particular circumstances, they “hire” them to make progress. Understanding this job to be done provides a causal explanation for choice that demographics and product categories often miss.
A job includes functional, social and emotional dimensions, as well as the circumstances that shape what progress means. When an organization aligns its offering, processes and measures around a clearly understood job, innovation becomes more predictable and harder to copy as a collection of features.
For executives, the theory redirects research from customer characteristics to struggling moments, desired progress and competing solutions. It does not remove portfolio choices: firms may identify many legitimate jobs and still need to decide which deserve concentrated enterprise investment.
OutcomesLab profiles Competing Against Luck because it grounds strategic outcomes in customer progress. A clear job strengthens the Focus Multiplier and creates a Coherence Premium by giving functions a shared causal purpose.
How the argument works
The argument works by explaining customer choice through the progress people seek in particular circumstances. Rather than treating demand as a correlation with demographics or product attributes, Jobs to Be Done asks what causes a customer to “hire” one solution and “fire” another.
A job is not a product category or a general desire. It combines the functional, social and emotional progress a person is trying to make with the circumstances that make that progress important. Those circumstances define the real competitive set. A milkshake may compete with a breakfast bar, boredom or an empty commute rather than only with other drinks.
The method begins with struggling moments and switching behavior. Interviews reconstruct what happened before a purchase: the push of an unsatisfactory situation, the pull of a new solution, anxieties about change and habits supporting the status quo. This timeline reveals the trade-offs customers actually make, including non-consumption and improvised alternatives that conventional market research overlooks.
Once the job is understood, the organization designs an experience that resolves it reliably. Product features, service, channels, brand promises, processes and measures are aligned around the same progress. That integration is harder to copy than a feature because competitors must reproduce the whole system and the customer’s confidence that it will work.
The causal chain is therefore explicit: circumstances create a desire for progress; that desire defines the choice criteria and competing solutions; a coherent experience satisfies the job; repeated delivery builds trust and demand. Innovation becomes less dependent on luck when leaders organize around the cause of choice rather than the characteristics of the people choosing.
What the book gets right
The book’s strongest contribution is replacing descriptive segmentation with a causal question about demand. Demographics can reveal who bought, and analytics can reveal what they did, but neither necessarily explains why a choice made sense in that moment. The job supplies that missing logic.
The insistence on circumstances is especially valuable. It prevents teams from turning a job into an abstract aspiration such as “convenience” or “connection.” The same person can hire different solutions for different progress in different situations. This directs research toward real trade-offs, anxieties and workarounds rather than averaged preferences.
The book also gets competition right. Customers compare any solution capable of making the desired progress, including doing nothing. That widens strategic imagination and helps explain why apparently superior products fail against habits or improvised alternatives.
Most importantly, Jobs to Be Done connects insight to operating design. A job is strategically useful only when the company aligns the complete experience and its supporting processes around it. That moves customer centricity beyond empathy and into resource allocation, capability design and measurement. The result is a shared causal purpose that can coordinate functions more effectively than a generic customer segment or product roadmap.
That shared purpose can also improve measurement by replacing departmental outputs with evidence that the customer actually made the intended progress.
Where the argument has limits
The theory can become circular when a job is inferred from a successful choice and then used to explain that same choice. Researchers may construct a persuasive story after the fact without proving that the identified job predicts behavior across customers or contexts.
Job definitions also vary in altitude. “Get a meal during a commute” may be actionable; “make progress in life” is not. A narrow job can produce a feature brief, while a broad job can justify almost any innovation. The framework offers judgment but no definitive test for choosing the right level.
The book gives less attention to market structure, economics and capability advantage. A company can identify a real job that is too small, unprofitable or easy for competitors to serve. It may also discover several legitimate jobs and still need a portfolio choice about which one deserves concentrated investment.
Interview evidence has limits. Memory is reconstructed, stated motives can differ from behavior and the customers willing to speak may not represent the market. Teams already attached to an idea can selectively hear the progress story that supports it.
Use the job as a falsifiable hypothesis. Test whether it improves prediction, whether customers sacrifice for the proposed progress and whether a coherent solution can earn attractive economics. Jobs to Be Done strengthens strategy, but it does not replace decisions about market attractiveness, differentiation or what the organization will decline to serve.
How it connects to Strategic Coherence
Competing Against Luck gives Strategic Coherence an external anchor: the organization should cohere around the customer progress it has chosen to enable.
The strongest connection is the Focus Multiplier. A precise job narrows the field of relevant features, channels and service choices. It helps leaders distinguish requirements that improve the intended progress from attractive additions that serve a different problem. This allows subtraction to improve the experience rather than merely reduce cost.
The book also clarifies the Coherence Premium. When product design, brand, delivery, support and measurement all reinforce the same job, the customer experiences a reliable solution rather than a set of departmental outputs. The premium comes from integration: each capability increases the value of the others.
A third connection is Capability Compounding. Repeatedly serving the same job allows the organization to accumulate distinctive data, routines and judgment about the circumstances surrounding it. Those capabilities can become harder to imitate than the visible product.
The tension is between customer focus and portfolio Optionality. Customers have multiple jobs, and markets evolve. Treating one job as permanent can narrow sensing; treating every discovered job as strategic recreates Dilution Drag. Leaders should separate the job the operating model is built to serve from adjacent jobs being tested.
What the book adds to OutcomesLab is a sharper definition of an outcome. Enterprise goals matter, but coherence becomes valuable only when it connects to progress for a chosen customer. OutcomesLab adds back a resource test: a claimed job must change investment, measures and stopped work. If the same roadmap survives every new customer insight, the job is descriptive rather than strategic.
Put it to work
Use Jobs to Be Done when growth has stalled despite feature investment, when segmentation explains customers but not choice, or when teams disagree about the outcome the offering should create.
Investigate recent switches and non-consumption:
- What struggling moment made the existing situation unacceptable?
- What functional, social and emotional progress was the customer seeking?
- Which alternatives—including doing nothing—were seriously considered?
- What anxieties or habits almost prevented the switch?
- Which parts of the complete experience made the new solution trustworthy?
Interview for sequence and behavior, not opinions about hypothetical features. Compare several cases and identify a pattern that explains meaningful trade-offs. Then state the job at a level that is stable enough to guide design but specific enough to exclude choices.
Translate it into an operating hypothesis: which experience, capabilities, channels and measures must reinforce the job, and what should be removed because it serves a different purpose? Test whether customers recognize and value the resulting progress.
The common misapplication is to label an existing product idea with a convenient job. Require disconfirming evidence, attractive economics and visible resource movement. A useful job should change what the organization builds, how it delivers and which opportunities it declines.
Record which evidence would cause the team to reject or redefine the job before product decisions are made.
