What is Jobs-to-be-Done?

Jobs-to-be-Done (JTBD) is a framework holding that customers "hire" products and services to accomplish a job: progress they are trying to make in a particular circumstance. The unit of analysis shifts from the customer's attributes to the customer's situation and goal. A job has functional dimensions (get from A to B, keep the team informed) and, crucially, emotional and social ones (feel in control, look competent to my boss), and the full job statement includes the circumstance: not "listen to music" but "stay motivated through the last stretch of a long run". The framework's sharpest implication is about competition. Products compete with everything else a customer might hire for the same job, which is how a video call competes with an office lease, and a glass of wine competes with a meditation app.

A Brief History

The intellectual seed is usually credited to marketing professor Theodore Levitt's drill-and-hole aphorism, but the framework's modern form comes from two overlapping streams: Clayton Christensen and colleagues at Harvard, who popularized the "job" language and connected it to disruption theory, and Tony Ulwick, whose Outcome-Driven Innovation formalized jobs into measurable desired outcomes. Christensen's canonical story is the milkshake study, recounted in his own Harvard Business Review article: a fast-food chain trying to sell more milkshakes got nowhere improving the product against category benchmarks, until researchers noticed that a large share of shakes sold before 9am, to solo commuters, who were hiring the shake to make a long boring drive more interesting and stave off mid-morning hunger, with one hand free. The competition was bananas, bagels, and boredom, not other milkshakes, and the improvements that mattered (thicker shake, longer-lasting, easier to grab) fell straight out of the job.

Running Jobs Research

1. Interview around real switching moments.
The richest jobs data lives in recent, concrete decisions: people who just bought, switched, or quit. In interviews, reconstruct the timeline like a documentary: what was happening the first time you thought about changing? What did you try before? What nearly stopped you? The forces at work (the push of the current struggle, the pull of the new solution, the anxiety of change, the inertia of habit) surface in the narrative, never in a direct question.

2. Separate the job from the solution.
Jobs are stable; solutions churn. "Store my files" is not a job; "be certain I can produce the contract when the client disputes it" is closer. Push each candidate job up a level by asking why until the answer stops changing when the technology does.

3. Capture all three dimensions.
Functional jobs get over-collected because they're easy to say; the emotional and social dimensions ("not look like the person who lost the file") often decide the hiring. Listen for them in tone and asides, the material that video and audio answers preserve and tick-boxes destroy.

4. Validate breadth quantitatively.
Once qualitative work has named the jobs and desired outcomes, surveys can measure which outcomes are most important and least satisfied across the market, which is the Ulwick playbook for finding underserved opportunity. Mixed-method tools like Ballpark suit this loop well: jobs interviews and video questions to find the language, then structured studies to size what you found.

JTBD and Personas

The framework is often staged as a rival to personas, and the criticism lands when personas are demographic decoration: the same person hires wildly different products in different circumstances, and circumstance is what personas flatten. But the lenses compose. Personas describe recurring patterns of who and context; jobs describe the progress being sought within those contexts. Mature teams use jobs to explain motivation and switching, and personas to keep design grounded in real usage patterns, rather than joining a methodology tribe.

The Benefits

JTBD explains behavior that segmentation cannot, redraws competitive maps around real alternatives, generates innovation prompts (serve an underserved outcome; remove a hiring anxiety), and produces language for positioning that customers recognize as their own. It also travels well across teams: a well-stated job aligns product, marketing, and sales around the same customer progress.

The Limitations

The framework's vocabulary is contested (Christensen and Ulwick schools define terms differently), and job statements are easy to write badly: too abstract to guide anything, or so concrete they're just features restated. Jobs research leans heavily on retrospective interviews, inheriting the usual memory and narrative biases. And JTBD explains motivation better than it specifies interfaces; it tells you what to build for, less often what to build. It is a lens, at its best when paired with methods that watch actual behavior.

The Short Version

Jobs-to-be-Done asks the most clarifying question in product research: what progress is this person trying to make, in what circumstance, and what are they firing to make room for us? Interview around real switches, keep jobs solution-free, honor the emotional dimensions, and size the opportunities quantitatively. Do that, and the milkshake lesson generalizes: the product improves fastest when you finally understand what it was hired to do.