Growth Marketing Glossary

Jobs to Be Done (JTBD)

jobs to be donenoun (framework)

People don't want a drill, they want a hole - the framework that reframes products as jobs customers hire them to do.

you(situation)hirea productto make progresson a jobpeople don't buy products - they hire them to do a job
Schematic — hiring a product to do a job
Term
Jobs to Be Done
Core idea
People hire products to make progress
Popularized by
Christensen; built by Ulwick, Moesta
Famous case
The McDonald's milkshake study

Forms & parts of speech

JTBD · noun
The progress-making framework.
"Jobs to be done reframed the whole roadmap - customers weren't buying features, they were hiring us to make a specific kind of progress."

Definition in plain terms

Jobs to Be Done (JTBD) is a framework built on a deceptively simple idea: people don't buy products, they 'hire' them to make progress on a 'job' in their lives — a goal, a struggle, a situation they're trying to move through. The classic line: customers don't want a quarter-inch drill, they want a quarter-inch hole — and really, they want the shelf hung and the satisfaction of a finished room. JTBD reframes markets around the JOB the customer is trying to get done (stable, durable) rather than the product's features or the customer's demographics (which mislead), and it reshapes how products get built, positioned, and marketed.

The mechanics

The origin and the famous proof: the theory was developed by Tony Ulwick (Outcome-Driven Innovation, from 1990) and popularized by Clayton Christensen, who gave it the 'Jobs-to-Be-Done' name and built it into disruption theory; Bob Moesta's McDonald's milkshake study (mid-1990s) is the canonical illustration — researchers found a large share of milkshakes were 'hired' by morning commuters for a job that had nothing to do with dessert (something filling, one-handed, and slow to consume to survive a boring commute), competing not with other milkshakes but with bananas and bagels, an insight no demographic or product-category analysis would surface. The framework's structure: a job has functional dimensions (the practical task — get to work fed) and emotional/social dimensions (how I want to feel, how I want to be seen), and the unit of analysis is the JOB, not the product or the persona — which is why JTBD practitioners often contrast it with BUYER-PERSONAS (personas describe who; jobs describe what-for, and the same person hires different products for different jobs). The two schools worth knowing (because they diverge): the Christensen/Moesta 'jobs as struggle/progress' school (qualitative, story-driven, the 'switch interview' uncovering what made someone fire the old solution and hire the new — the JOBS-STORIES format lives here), and the Ulwick 'outcome-driven' school (quantitative, mapping the desired outcomes of a job and measuring which are underserved). How marketing uses it: positioning and messaging that speak to the job and the progress (not the feature list), product and roadmap decisions anchored on underserved job outcomes, segmentation by job rather than demographic, and competitive framing that sees the real alternatives (the milkshake's rivals were bagels, not other shakes). The honest caveat: JTBD is a powerful reframing, not a measurement system — its qualitative school can rationalize any story after the fact, so the discipline is using it to generate hypotheses about the job that then get tested, not to narrate conclusions you already held.

When it matters

JTBD matters most at the strategy layer — product positioning, roadmap prioritization, market definition, and messaging — where reframing around the customer's job (instead of the product's features or the buyer's demographics) surfaces the real competition, the underserved needs, and the language that resonates. It matters in innovation and new-market work (where the job is stable but current solutions are bad) and in repositioning (finding the job your product is actually hired for, which may not be the one you built it for). The discipline is treating the job as the durable unit of analysis, distinguishing the functional from the emotional and social dimensions, using the framework to generate testable hypotheses rather than after-the-fact stories, and remembering it's a lens for understanding demand, not a substitute for measuring it.

Worked example. A B2B software company positions its product on a feature list - 'the most integrations, the best dashboard' - competes feature-for-feature with rivals, and watches win rates stagnate even as it ships more features than anyone. A JTBD reframing, built from switch interviews with recent buyers, changes the question from 'what features do they want' to 'what job did they hire us to do, and what did they fire to do it.' The interviews surface a job the feature list had obscured: buyers weren't hiring the product for integrations - they were hiring it to make their team look competent to THEIR boss during a high-stakes quarterly review, a job with heavy emotional and social dimensions the feature comparison completely missed. That reframes everything: the real competition wasn't the rival tools (the feature war) but the spreadsheets-and-manual-effort the buyer was fleeing and the reputational risk they were managing, positioning shifts to speak to the progress (look in control, never get caught flat-footed in the review), the roadmap re-prioritizes the underserved outcomes of that actual job, and messaging stops listing features and starts naming the struggle. Win rates climb - not because the product changed, but because the company finally understood what it was being hired to do. The team keeps JTBD honest by treating each job hypothesis as testable, not as a story to confirm what it already believed.
Failure modes to watch. Using JTBD to narrate conclusions you already held (the qualitative school rationalizes any story after the fact - generate testable hypotheses instead); confusing the job (durable) with the product or persona (misleading); missing the emotional and social dimensions by mapping only the functional task; defining competition by product category instead of by the job (the milkshake's rivals were bagels); and treating a reframing lens as a substitute for measuring demand.

Synonyms & antonyms

Synonyms

jobs to be doneJTBDjobs theory

Antonyms

feature-led product thinkingdemographic-only segmentation

Origin & history

Jobs to Be Done grew from two roots - Tony Ulwick's Outcome-Driven Innovation (1990) and the Harvard Business School thinking of Clayton Christensen, Bob Moesta, and colleagues - with Christensen naming it 'Jobs-to-Be-Done' around 1999 and popularizing it in The Innovator's Solution (2003); the milkshake study made it famous, and it split into qualitative 'progress' and quantitative 'outcome' schools.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is Jobs to Be Done?
A framework holding that people don't buy products, they 'hire' them to make progress on a job in their lives — reframing markets around the customer's durable job rather than product features or demographics.
What is the milkshake story?
Bob Moesta's McDonald's study found morning commuters 'hired' milkshakes for a job (filling, one-handed, slow to drink on a boring commute) — competing with bagels and bananas, not other shakes — an insight no demographic analysis would surface.
How does marketing use JTBD?
To position and message around the customer's job and desired progress, prioritize roadmaps on underserved job outcomes, segment by job rather than demographic, and see the real competition the product is hired against.

Related tools & calculators

Resources & people to follow

Curated, non-competitor resources verified per term.

Related training

Disciplines

Areas of marketing where jobs to be done (jtbd) is a core concern:

Sources

  1. trendsGoogle Trends — "jobs to be done"