Jobs to Be Done (JTBD)

Jobs to be done (JTBD) is a way of understanding why customers buy what they buy. Its core claim, popularized by Clayton Christensen, is that people do not really want products — they want to make progress in a particular situation, and they "hire" a product to get that job done. The classic illustration is that someone buying a milkshake on a morning commute is not buying a beverage so much as hiring something to make a boring drive less dull and to stave off hunger until lunch. The job is the progress the person is trying to make, including its functional, emotional, and social dimensions. JTBD focuses attention on that underlying job rather than on the product's features or the buyer's profile, because two people with nothing demographically in common can hire the same product for the same job.

This reframing changes what counts as competition and what counts as insight. If customers are hiring your product for a job, then your real competitors are everything else they could hire to do the same job, including non-obvious alternatives and doing nothing at all. A video-call tool competes not only with other video tools but with flights, phone calls, and emails — anything that does the job of "connect with a colleague far away." JTBD pushes you to study the situation and the struggle that prompts someone to look for a solution, the progress they want, and the obstacles in the way. Get the job right, and product, messaging, and positioning all sharpen, because they are aimed at the progress the customer is actually trying to make rather than at a feature list or a persona.

JTBD is often contrasted with demographic and persona-based thinking, and the contrast is the point. Traditional segmentation groups customers by who they are — age, income, role, attitudes — and builds personas to represent them. JTBD argues that who someone is predicts what they will buy far less reliably than what job they are trying to get done in a given moment. The same person hires very different solutions for different jobs, and very different people hire the same solution for the same job. So instead of asking "who is our customer?", JTBD asks "what job is the customer hiring us to do?" — a question about situation and motivation rather than identity. This does not make demographics useless, but it demotes them from the cause of a purchase to, at most, a loose correlate of it.

JTBD also complements other tools rather than replacing them. It pairs naturally with research methods that reveal what customers actually choose and value — the trade-offs they make, the alternatives they consider — because understanding the job is what gives those trade-offs meaning. Where segmentation tells you which groups exist and conjoint-style methods tell you what features they value, JTBD tells you why they are in the market at all and what "better" would mean to them. The danger is treating JTBD as a slogan rather than a discipline: anyone can assert a job, but a real job statement comes from studying the customer's struggle closely enough to describe the progress they seek in their own terms, not the marketer's.

Use jobs to be done to anchor strategy in the progress customers are trying to make. Start by studying the situation that drives someone to look for a solution — the struggle, the trigger, the desired outcome — through interviews and observation rather than assumption, and write the job as the progress sought in the customer's terms. Then map the full set of alternatives they could hire for that job, including doing nothing, so you understand your true competitive set. Use the job to guide what you build (features that advance the progress), how you message (speaking to the struggle and the outcome), and how you position (against the real alternatives). Done well, JTBD keeps the whole organization pointed at customer progress instead of at internal feature lists or demographic guesses.

Avoid the common abuses. The biggest is inventing a job from the armchair — declaring what customers "really" want without the research to support it — which dresses up the same old assumptions in fashionable language. Another is defining the job too narrowly (around your product) or too broadly (around vague life goals), when the useful level sits in between, at the specific progress in a recognizable situation. A third is treating JTBD as a one-time exercise rather than an ongoing lens, since jobs and alternatives shift over time. And a fourth is discarding demographics and behavioral data entirely, when they remain useful as correlates that help you find people with the job. Used as a disciplined way to see the customer's progress — and to remember that you compete with every alternative that serves it — JTBD sharpens decisions across product and marketing alike.

Jobs to be done — popularized by Clayton Christensen — holds that customers hire products to make progress on a job, shifting focus from demographics to the progress a customer is trying to achieve.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

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