Concept

Jobs to Be Done

concept jtbd jobs-to-be-done product demand-side innovation b2b

Jobs to Be Done

Jobs to Be Done (JTBD) is a framework for understanding why people switch products, developed by Bob Moesta and Clay Christensen. The core claim: people hire products to make progress in their lives. The unit of analysis is not a feature, a demographic, or a product category — it is the struggling moment: the context+outcome vector that causes someone to act.


The fundamental reframe

JTBD shifts the lens from supply side to demand side:

Supply-side viewDemand-side view
Competitors = similar productsCompetitors = what the customer would use instead
Market = product categoryMarket = struggling moments
Customer need = stated preferenceCustomer need = context + desired outcome
Build features → create demandStruggling moment → creates demand → product hired to fill it

The canonical example: Snickers and Milky Way appear to compete (same category, same aisle, similar ingredients). JTBD reveals they are hired for entirely different jobs. Snickers = meal replacement in high-output, time-constrained contexts (competes with protein drinks and Red Bull). Milky Way = emotional recentring after a stressful event (competes with wine, brownies, a run).


The four forces model

Every switch from an old product to a new one is governed by four forces:

ForceLabelDirectionDescription
PushF1Away from oldContext making the current situation untenable — the only reason people leave
PullF2Toward newAttraction to the new outcome
Anxiety of the newF3Against switchUncertainty whether the new solution will work
Habit of the presentF4Against switchInertia; cost of giving up familiar routines and artefacts

Switch condition: F1+F2 must exceed F3+F4.

Key counterintuitive implication: adding features increases F2 (pull) but also increases F3 (anxiety — “can it really do all that?”). Reducing friction — eliminating F3+F4 — is often more effective and cheaper than building more product.

  • Condo with storage included: removing the inertia of dealing with possessions → 30% sales increase.
  • Dining table space sacrificed from 2nd bedroom: removing the emotional attachment to the family table → 22% sales increase.

Six phases of buying

The buying journey has six distinct phases; most sales processes are mapped to the seller’s timeline, not the buyer’s:

  1. First thought — vague awareness something must change
  2. Passive looking — problem-aware, solution-unaware; absorbing context
  3. Active looking — comparing alternatives
  4. Deciding — trade-off resolution
  5. First use — highest anxiety; onboarding critical
  6. Ongoing use — habit formation; job is being done repeatedly

Aligning the sales process (including demo structure) to the buyer’s current phase — rather than pushing everyone toward a close — can dramatically reduce cycle time and increase conversion.


The struggling moment

A struggling moment is not a pain point. It is the specific situational trigger that causes a person to say “today’s the day I have to do something different.” Struggling moments:

  • Exist before any product is built.
  • Create demand; product launches do not.
  • Are durable — most struggling moments existed 10 years ago and will exist 20 years from now; only the technology that fulfils them changes.
  • Become a more durable roadmap than feature lists (which can be disrupted by technological shifts).

Southern New Hampshire University: 60 anomalies (students paying full price but never attending in person) → revealed a struggling moment for people who needed to go back to school but couldn’t attend physically → grew to over 200,000 students.


Interview method

Who: people who recently completed the switch (bought or churned). “Bitchin’ ain’t switchin’” — complaints do not predict behaviour change. Only past behaviour is causally informative.

How many: 10–12 per job cluster. Patterns recur by 7–8 interviews. Two rounds of 12 outperforms one round of 24.

Method: extract the causal story through criminal-and-intelligence interrogation that feels like therapy.

  • No standardised discussion guide — follow the highest-information thread.
  • Misparaphrase technique: play back the story incorrectly → the subject corrects and elaborates. “Yes” ends conversation; “no” opens it.
  • Bracket technique at the “edge of language”: offer two wrong alternatives to force more disclosure.
  • Move through three layers of language: pablum → fantasy/nightmare → what actually happened.

Reference: Never Split the Difference (Chris Voss) for interrogation technique.

For zero-to-one: study what people would fire when your product launches. Jobs preexist products; find the struggling moment, then build.


Clustering, not segmenting

Segmentation groups people by demographics → produces averages → no actionable jobs. Clustering groups people by shared push+pull pathways → produces job profiles → drives product, pricing, and positioning.

Most products are hired for 3–5 different jobs that conflict with each other. Identifying the conflicts enables deliberate decisions about which jobs to serve and which to decline. Intercom identified four distinct jobs and aligned product bundles and pricing to each, competing differently against HubSpot (acquisition job) vs. Zendesk (support job).


Three energy sources

Every job has three dimensions of energy (functional, emotional, social):

DimensionScopeExample
FunctionalTime, space, effort, knowledge”I need this done in three bites so I can keep working”
EmotionalFeelings, self-perception”I feel overlooked and inadequate”
SocialHow others perceive me”My boss thinks I’m not moving fast enough”

Omitting the emotional or social dimensions produces an incomplete job profile and will cause product or messaging failures.


Demand Side Sales

JTBD applied to the sales process: stop trying to sell and help people buy. The seller’s default process (qualify → demo → close) is mapped to the seller’s timeline. Matching the process to the buyer’s phase eliminates friction from the purchase process itself.

Parallel to Product Positioning (April Dunford’s “teaching the customer how to buy”) — both argue that the seller’s job is to reduce the buyer’s cognitive burden, not to push.


Where mainstream views differ

Most product teams treat customer research as hypothesis-testing: form a hypothesis, run surveys or usability tests to validate or disprove. JTBD is hypothesis-building research — the point is to discover what the questions are, not to test pre-formed answers. Teams that do “JTBD in a conference room” — discussing what the jobs probably are without interviewing — will “guarantee 100% wrong” outcomes (Moesta).

Mainstream competitive analysis groups by product category and feature set (supply side). JTBD defines competition from the demand side — which often reveals unexpected competitors outside the apparent category.


Flavours of JTBD

Three distinct traditions share the JTBD label:

TraditionApproachBest for
MoestaQualitative, story-based, causal. Hypothesis-building. Demand-side first.Startups, zero-to-one, new product strategy
ChristensenPhilosophical/strategic framing; less prescriptive methodStrategic thinking, theory
Ulwick (ODI)Quantitative, outcome-driven, 100+ stepsRegulated industries, complex systems with high research budgets

Key distinction: in Moesta’s view, only people have jobs — products don’t have jobs. Ulwick’s ODI can veer toward attributing jobs to product functions.


See also