Jobs to Be Done Theory Explained for Customer Experience

Clayton Christensen once pointed out that nobody wants a quarter-inch drill. They want a quarter-inch hole — and if a better way to make that hole appears tomorrow, the drill is dead to them by lunchtime. That is the uncomfortable truth sitting underneath most failed product launches, most loyalty programmes nobody loves, and most customer journeys that score well on satisfaction and still bleed customers.

Jobs to be Done (JTBD) theory says people don't buy products, services, or even experiences. They hire them to make progress against a specific struggle in their life, and they fire them the moment something does the job better. For a CX practice built on personas, demographics, and journey stages, that is a more radical idea than it sounds.

What is the Jobs to Be Done theory?

Jobs to Be Done theory, developed by Harvard Business School professor Clayton Christensen, holds that customers don't simply purchase products or services — they "hire" them to make progress or resolve a specific problem in their life. The "job" is the progress the customer is trying to make; the product or service is just the tool hired to get it done. Competitors aren't just similar products — they are anything else a customer could plausibly hire for the same job, including doing nothing at all.

This reframes the basic unit of analysis in customer experience work. Instead of asking "what does this customer segment want from us," JTBD asks "what progress is this person struggling to make, and what did they hire before they hired us." It's a small linguistic shift with large structural consequences for how you design journeys, build archetypes, and prioritise fixes.

Why did Christensen develop JTBD theory in the first place?

Christensen built the theory to explain a pattern he kept seeing: companies that followed every rule of market segmentation — age, income, lifestyle, product category — still launched products that flopped, while customers with wildly different demographic profiles bought the same thing for the same hidden reason.

The clearest public account of this comes from his December 2005 Harvard Business Review article, "Marketing Malpractice: The Cause and the Cure," co-written with Scott Cook and Taddy Hall. In it, they describe a fast-food chain trying to improve milkshake sales by testing flavour, thickness, and price with "typical milkshake buyers" — the standard segmentation playbook. Sales barely moved. A researcher then spent full days in the stores simply watching who bought milkshakes and why, and found a large, unexpected cluster of customers buying them alone, early in the morning, to eat during a long commute. They weren't hiring a dessert. They were hiring something dense enough to stay interesting for twenty minutes, tidy enough to drink one-handed, and filling enough to make the mid-morning hunger disappear. A banana or a doughnut couldn't compete with that job — even though, on paper, they were the "healthier" or "more convenient" alternative.

Christensen later expanded the theory with co-authors Taddy Hall, Karen Dillon, and David S. Duncan in the 2016 book Competing Against Luck, which remains the most complete public statement of the framework and the one most CX and product teams cite today.

How is JTBD different from traditional customer segmentation?

Traditional segmentation groups customers by who they are. JTBD groups them by what they are trying to accomplish — and those two groupings rarely line up. A 28-year-old graphic designer and a 55-year-old accountant can be hiring the exact same banking app for the exact same job: "give me enough confidence that I won't be embarrassed at the till." Meanwhile, two customers who look identical on a CRM dashboard — same age, same income bracket, same city — can be hiring completely different jobs from the same insurance product: one wants peace of mind for his family, the other wants the cheapest box ticked to satisfy a mortgage requirement.

This matters enormously for anyone building CX archetypes. A persona built on demographics tells you who to market to. A persona built on jobs tells you what to design for — and the two produce very different journey maps, service blueprints, and prioritisation calls.

• Segmentation asks: who looks like our best customer?
• JTBD asks: what struggle is this person trying to resolve, and who else competes for that struggle?
• Segmentation groups by: age, income, geography, lifecycle stage.
• JTBD groups by: the circumstance that triggers the need and the progress sought.
• Segmentation's blind spot: it can't explain why near-identical customers behave completely differently.
• JTBD's blind spot: it says less about who to target with media spend, since jobs cut across demographics.

What are the three dimensions of a "job"?

Every job a customer hires a product or service for has three dimensions, and most experience failures trace back to a company optimising only one of them.

The functional dimension is the practical task — transferring money, getting from A to B, resolving a billing error. The emotional dimension is how the customer wants to feel while doing it, or as a result of it — reassured, competent, unhurried, in control. The social dimension is how they want to be perceived by others while hiring the solution — responsible, generous, savvy, discreet.

A private bank that nails the functional job (accurate statements, fast transfers) but ignores the emotional one (the client wants to feel respected, not processed) will still lose that client to a competitor who gets the feeling right, even with marginally worse technology. This is precisely why customer experience work that stops at process efficiency consistently underperforms work that treats the emotional and social dimensions as equally real requirements, not soft extras.

How does JTBD change customer journey mapping?

A journey map built around jobs starts before the first touchpoint and ends after the last one — because the job existed before the customer ever met the brand, and the job's resolution (or failure to resolve) is what determines whether they return.

Conventional journey maps tend to start at "awareness" and end at "post-purchase support." A JTBD-based map starts at the moment of struggle — the morning the commuter first felt the mid-morning slump, the day the account holder first worried about not having enough saved — and treats everything before the purchase as diagnostic gold. That pre-purchase struggle tells you which competitors you're actually up against, and they are rarely the obvious ones. The milkshake's real competitor wasn't another milkshake; it was boredom on a boring commute.

This is also where voice of customer work earns its keep. Satisfaction surveys ask how customers felt about a touchpoint they've already hired you for. JTBD-style interviews ask what was happening in their life the week before they switched — the circumstance, the moment of frustration, the almost-decision they made with a competitor before changing their mind. That is a fundamentally different, and far richer, data set for anyone building out CX journeys.

Where does JTBD intersect with behavioral economics?

JTBD and behavioral economics were built independently but describe the same terrain from different angles, and the overlap is where the theory becomes genuinely useful for experience design rather than just product strategy.

The clearest bridge is loss aversion — Daniel Kahneman and Amos Tversky's well-established finding that losses loom psychologically larger than equivalent gains. JTBD practitioners (most visibly Bob Moesta, who worked alongside Christensen on the theory's development) formalised this into what's often called the "Four Forces" model of switching: two forces push a customer toward hiring something new (dissatisfaction with the current situation, and the pull of a better alternative), and two forces hold them back (the anxiety of the new choice, and the habit or attachment to the status quo). That second pair is loss aversion wearing a different hat — the customer isn't weighing features, they're weighing the certain loss of a familiar routine against the uncertain gain of a new one.

This is also where the status quo bias and System 1/System 2 thinking (Kahneman's dual-process framework) do real work. Most "job switches" aren't decided through careful comparison. They happen in a quick, affect-driven System 1 judgment triggered by a moment of acute frustration — the transfer that bounced, the call that went unanswered — and only justified afterwards with System 2 reasoning. A CX team that understands this stops asking "what features would make customers switch to us" and starts asking "what moment of struggle makes someone finally willing to break a habit," which is a far sharper design brief.

How do you apply JTBD inside a CX practice?

JTBD is a research discipline before it's a design framework. Skipping the research and jumping straight to "jobs" that sound plausible is the single most common way teams misuse it.

1. Find the switch moment. Interview customers who recently hired your product or a competitor's, and work backwards to the exact circumstance that made them start looking. The goal is a timeline, not an opinion.
2. Separate the functional, emotional, and social job. For each switch story, write down what they needed to accomplish, how they wanted to feel, and how they wanted to be seen. Most teams only capture the first.
3. Map the forces of progress. Identify what pushed them away from the old solution, what pulled them toward the new one, what anxiety nearly stopped them, and what habit they had to overcome. This becomes the real friction map, often more revealing than a standard pain-point audit.
4. Re-segment around the job, not the demographic. Group customers by the progress they're seeking rather than who they are, and check whether your current customer experience strategy and messaging are actually built around demographic segments that don't predict behaviour.
5. Redesign the moment of truth around the job, not the transaction. If the job is "feel competent handling my own finances," the account-opening flow should be judged on whether it builds that feeling, not just on how many clicks it takes.
6. Track rehire, not just satisfaction. Satisfaction scores measure how a transaction felt. JTBD discipline asks whether the customer would hire you again for the same job next time the circumstance recurs — a stricter and more predictive test of loyalty.

Teams running a formal CX maturity assessment often discover their journey maps are comprehensive but job-blind — every touchpoint is documented, but nobody can state, in one sentence, the job each journey exists to resolve. That gap is usually where the biggest, cheapest wins are sitting.

What are the limits of Jobs to Be Done theory?

JTBD is a powerful diagnostic, not a complete operating system, and treating it as one creates its own blind spots.

• It under-weights who should receive the message. Jobs cut across demographics, which is precisely their strength for product design — and precisely their weakness for media targeting, where you still need to know who to reach, not just what job they're hiring for.
• It's expensive to do properly. Real switch-moment interviews take skill and time; shortcuts produce "jobs" that are really just features restated in job-sounding language.
• It can miss structural and regulatory constraints. A customer's "job" in banking or healthcare often has to be resolved within rules the customer didn't choose and can't negotiate around, and JTBD alone won't surface those constraints.
• It needs pairing with a prioritisation lens. Knowing the job is urgent and under-served tells you nothing about whether solving it is commercially viable — that still requires a separate commercial and operational filter.

None of this invalidates the theory. It just means JTBD earns its keep as the lens that tells you what to build and why, sitting alongside — not instead of — the operational discipline of good service design and the targeting discipline of segmentation.

The real shift JTBD asks of CX leaders

Most CX functions are built to measure how a journey felt. JTBD insists you also know why the customer started that journey in the first place — and what they were prepared to fire to get there. That's a harder question to answer than any satisfaction survey, and it's exactly why so few organisations ask it properly.

The teams that do ask it stop optimising touchpoints in isolation and start optimising for rehire — the only metric that actually predicts whether the customer comes back next time the same circumstance strikes. In a market where switching costs keep falling and alternatives keep multiplying, that distinction between "satisfied" and "rehired" is going to separate the CX leaders who compound loyalty from the ones who keep re-winning the same customers at growing cost.

If your organisation wants to find out whether its journeys are actually built around real customer jobs or just around internal process stages, Renascence's team can help you run that diagnosis and turn the findings into a working implementation roadmap — get in touch to start the conversation.