Jobs to Be Done

The demand-side theory that customers “hire” a product or service to make progress on a specific job, which reframes who a company’s competition actually is and which customer needs are worth building for.

The phrase comes from a way of talking about a purchase that flips the usual question. Most product thinking starts with the customer: who are they, how old, what segment, what features do people like them want. Jobs to Be Done starts with the situation. Clayton Christensen’s example was a milkshake. A fast-food chain wanted to sell more of them and ran the standard playbook: survey milkshake buyers, ask what they’d change, tweak the recipe accordingly. Sales didn’t move. Then a researcher asked a different question: what job were people hiring the milkshake to do? It turned out a large share were bought before 8 a.m. by commuters who needed something to occupy a long, dull drive and keep hunger off until noon. The milkshake wasn’t competing with other milkshakes. It was competing with bananas, bagels, and boredom. Once you know the job, you know who you’re really up against, and “make it thicker so it lasts the whole commute” becomes an obvious move that no amount of demographic surveying would surface.

What It Is

Jobs to Be Done is a theory of demand: customers don’t buy products, they “hire” them to make progress on a job that arises in a specific circumstance. The job is the progress the customer is trying to make. The product is one of several candidates competing to get hired for it, and the customer fires whatever they were using before. The job has a functional dimension (the practical task), but almost always a social and emotional one too: how the choice makes the person look to others, and how it makes them feel. The milkshake’s functional job was filling a long commute; the emotional one was a small, blameless treat at the start of a grinding day.

The theory’s central move is to relocate the unit of analysis. Conventional marketing organizes the world by attributes of the customer (age, income, segment) or categories of the product (we sell milkshakes, so our competitors sell milkshakes). JTBD organizes it by the job, which cuts across both. Two products in entirely different categories compete head-on when they’re hired for the same job, and the same product gets hired for different jobs by the same person on different days. That’s why the framing is diagnostic: it tells you which competitors are real (everything else hired for the job, however unlike your product) and which customer needs are stable enough to build a company on (the job persists even as the solutions churn).

A note on what the term is not. A “job” is not a feature request, and it’s not a demographic. “Users want dark mode” is a feature; “I need to read in bed without waking my partner” is closer to the job under it. “Millennials prefer X” is a demographic correlation that tells you nothing about the progress anyone is trying to make. The theory also splits into two schools that agree on the core and diverge on method. Christensen’s version treats the job as a causal mechanism: understand the circumstance and the job becomes the thing that explains why a purchase happened. It stays largely qualitative. Anthony Ulwick’s Outcome-Driven Innovation instead decomposes the job into roughly a hundred measurable desired outcomes and prioritizes them quantitatively by importance and satisfaction. The split matters in practice: one school sends you to interview deeply, the other to survey and score. Both are recognizably JTBD.

Why It Matters

The job framing earns its place because it answers two questions founders and investors get wrong in predictable ways.

The first is who is the competition. A founder who defines competitors by category (“we’re a project-management tool, so our rivals are other project-management tools”) systematically misses the alternative the customer is actually using, which is often a spreadsheet, an email thread, or nothing at all. Most early-stage products lose not to a named competitor but to the status quo: the customer keeps coping the way they always have. The job lens makes that visible, because it forces the question “what is this person doing today to make this progress?” and the honest answer is rarely a competing startup.

The second is which need is durable enough to build on. Solutions are fashionable and jobs are stable. People have wanted to send a short message to a distant person for two centuries; the telegram, the letter, the phone call, the email, and the text were all hired for versions of that job and all eventually fired. A company anchored to a job rather than to its current expression of a solution can ride the next technology shift instead of being killed by it. For the founder, that’s a roadmap heuristic: build toward the job, not toward the feature. For the investor, the job is a way to judge whether a market is real and lasting or a temporary artifact of one product’s moment.

For the talent reader, the framing is a tell about a company’s strategic clarity. A team that can state, crisply, the job their product is hired for and what it’s competing against tends to make sharper product and positioning decisions than one that describes its market by category and demographic. Reading that clarity (or its absence) is part of judging whether the bet behind an equity offer is well-aimed.

What the concept gives a practitioner is a precise replacement for a fuzzy instinct. “Know your customer” is advice no one disagrees with and no one can act on. “What job is this product getting hired for, in what circumstance, against what alternatives, and what is the social and emotional progress alongside the functional one?” is a question with answers you can test.

How to Recognize It

A genuine job is recognized by its shape, not by how it’s phrased in a deck. The reliable signals:

• It’s framed as progress in a circumstance, not as a product attribute. “When I’m starting a long, boring commute and I want to stay full and occupied” is a job. “A thicker milkshake” is a solution to it. If the statement names your product, it isn’t the job.
• It’s stable while solutions come and go. The test is whether the job would have existed before your category did and will outlast it. If the “job” disappears the moment the technology changes, it’s a feature, not a job.
• It has a social or emotional dimension, not only a functional one. Purely functional accounts of why people buy are usually incomplete. The customer who buys the premium tool often hires it partly to feel competent or to be seen as serious, and missing that explains why the cheaper, functionally-equal option loses.
• The competition it implies includes non-consumption and odd substitutes. If naming the job surfaces rivals you’d never have listed (a spreadsheet, a habit, doing nothing), the framing is working. If the only competitors it surfaces are the obvious same-category players, you’ve described a category, not a job.

How It Plays Out

The milkshake study is the canonical illustration, and it shows the theory doing real work. The chain’s category-and-demographic research had stalled because it asked existing milkshake buyers how to improve milkshakes, a question that can only ever return a better milkshake. The job inquiry asked when and why people bought, found the morning-commute job hiding inside the sales data, and turned up a competitive set (bananas, bagels, doughnuts, an empty cup-holder) that the category framing had made invisible. The product implications followed directly: thicker so it survives the commute, available fast at a drive-through, sized to last. A separate afternoon job (a parent placating a child) wanted the opposite, a thinner and smaller shake, and trying to serve both with one recipe had been quietly hobbling both.

The framing reaches into validation, too. A founder running honest discovery interviews needs to know which past behavior to dig into. “Tell me about the last time you tried to make this progress” is a far better prompt than “would you use a tool that does X.” The job tells the interviewer what story to chase: the circumstance that triggered the need, what the person hired to meet it, where that choice fell short, and what they were willing to give up to do better. Without the job lens, discovery collects a pile of anecdotes; with it, the founder knows which anecdote is evidence of a real, recurring, fundable need and which is a one-off.

Consequences

Adopting the job lens changes which competitors a team watches, which features it builds, and how it reads a market, with real costs alongside the clarity.

Benefits. A founder who works from the job tends to define the competitive set honestly (including the status quo, the most under-counted rival of all), to build toward a durable need rather than chasing the feature requests of the loudest current users, and to position the product against the alternative the customer is actually firing. The framing is also a strong antidote to the demographic trap, the habit of mistaking a correlation (“our users skew young”) for a reason anyone buys. And because the job outlasts its solutions, a job-anchored strategy degrades gracefully as technology shifts instead of being obsoleted by it.

Liabilities. The theory is a lens, not a generator. It explains demand well once you’ve understood a circumstance deeply, but it doesn’t hand you the insight, and “find the job” can become a slogan teams repeat without doing the patient inquiry the milkshake study actually required. It’s also genuinely hard to bound a job at the right altitude. Define it too narrowly (“hire a milkshake”) and you’ve just renamed the product; define it too broadly (“be happy on my commute”) and it’s useless for any decision. The two schools’ disagreement is a live cost here, because the qualitative and quantitative methods can point in different directions and the theory itself doesn’t adjudicate. And like any framework that explains purchases convincingly in hindsight, JTBD invites just-so storytelling: a tidy job narrative constructed to fit a decision already made. The discipline that makes it valuable is the same one the loose usage discards. The job has to be discovered from how real people actually behaved, not authored to justify the product you wanted to build.

Related Articles

Sources

• Clayton Christensen, Taddy Hall, Karen Dillon, and David Duncan, Competing Against Luck: The Story of Innovation and Customer Choice (2016) — the book-length statement of the theory, the milkshake study, and the causal-job framing.
• Clayton Christensen, Taddy Hall, Karen Dillon, and David Duncan, “Know Your Customers’ ‘Jobs to Be Done’” Harvard Business Review (September 2016) — the concise article version of the causal school, widely used as the canonical short reference.
• Anthony Ulwick, Jobs to Be Done: Theory to Practice (2016) — the Outcome-Driven Innovation school, which turns the job into measurable desired outcomes that can be prioritized quantitatively.
• The framing traces to Theodore Levitt’s observation, taught for decades, that people don’t want a quarter-inch drill, they want a quarter-inch hole — the demand-over-product idea that Christensen and Ulwick later formalized into a working method.