Jobs-to-be-Done: Nobody Wants Your Product — They Want to Get One Thing Done
Topic: Jobs-to-be-Done·4 principles
"People don't want a quarter-inch drill; they want a quarter-inch hole." And really — they don't even want the hole. They want the picture hung on the wall.
Switch your point of view first. You think the customer is choosing between you and a competitor. What they're actually asking themselves is a different question: "Given the mess I'm in, how do I move one step forward?" People don't want to own a product — they're stuck on some bit of progress in their life and are temporarily hiring something to give them a push. A milkshake, a drill, your software, even you as a person — all of them get "hired" to do a job. Once you see the real job (the progress they're trying to make), three things get easier at once: you know what to say, you know who your real competitor is, and you know when to say "this isn't right for you." Today we install the job-centered lens — the foundation under everything that follows: selling the outcome, digging for pain, building a value proposition.
PRINCIPLE 01
People Don't Buy Products — They Hire Them to Do a Job
People don't buy products — they hire them to do a job
job lensprogressredraw the rivals
The principle, in one line
Don't ask "what features does my product have"; ask "in what situation, and to make what progress, did the customer hire me?" A product is a noun; a job is a verb — and people always pay for the verb.
From the masters
"People don't want a quarter-inch drill. They want a quarter-inch hole."— Theodore Levitt / popularized by Clayton Christensen
The real structure of a purchase
Scene
You sell an online course. The prospect asks: "How are you different from platform XX?"
✗ Product lens (spec war)
"We have more hours, better instructors, a community, a workbook…" You're going head-to-head on features against the "competitor list" in their head — and that race almost always ends on price, cheapest wins.
✓ Job lens (ask the job first)
Ask the progress they want: "After you finish, what one thing do you specifically want to be able to pull off? Land a job in a new field? Ship your current project solo? Or systematically fill a gap?"
Speak to the job: "If it's landing a job, then what you actually need isn't 'more hours' — it's 'a portfolio + passing interviews.' Ours is built dead-on for that: you walk out with three projects you can take into interviews." You've moved the battlefield from course specs to the progress they want — and the competitor list gets redrawn on the spot.
Why it works · mechanism & evidence
Why it works
Mechanism: people buy progress, not products. In a specific situation, someone is stuck at state A and wants to move to a better state B; the product is just a tool temporarily "hired" to make that move. So what closes the deal is never the feature list — it's "is your tool the one that best does this job, right now?" See the job, and you know what to highlight and who your rivals really are.
Jobs-to-be-Done theory (Clayton Christensen et al., Competing Against Luck, 2016) — reframes buying as "hiring a solution to do a job."
The milkshake case (Christensen & Bob Moesta, for a fast-food chain) — morning milkshake buyers were hiring it to do the job of "something one-handed for a boring commute that lasts till noon." The real rivals weren't other shakes — they were bananas, bagels, and "buy nothing." Change the job and both the recipe and the pitch change.
Honest on strength: JTBD is mainly a business framework + case studies, not a randomized controlled experiment — don't treat it as a proven causal law. But its explanatory power and usability are high, and it points the same way as the two harder findings below (the reward-brain of status, and status-quo bias).
Boundary: the job is stable; solutions get swapped. So don't fall in love with your product — fall in love with the job. The day a better way to do it shows up, the customer will fire you without hesitation.
Translate "product description" into "job" (checklist)
What situation were they in when they started looking for a solution? (What happened in that moment?)
Which state are they moving from, to which state? (The A → B "progress.")
To do this job, who else could they hire? (Include workarounds and "buy nothing.")
Is my thing genuinely the best at doing this job right now? If not, say so.
Common mistakes
Falling for the product, forgetting the job. The better you know your features, the more you pitch the feature list — which the customer isn't even listening to.
Mistaking a demographic for a job. "My customer is a 25–35 urban woman" isn't a job — it's just who's buying. The same person hires you for wildly different jobs in different situations.
Seeing only the functional layer. Next up: a job usually has three layers.
Key references
Clayton Christensen et al., Competing Against Luck — the definitive JTBD book and source of the milkshake case. Theodore Levitt, Marketing Myopia — origin of the "drill / hole" metaphor: don't fall for your product, watch the thing it does for the customer.
Scripts to steal
Ready-to-use lines
"What job are they hiring it for?" — the core JTBD question.
"They fired their old solution and hired yours." — switching vendors = firing the old, hiring you.
"Sell the progress, not the product." — the whole lens in five words.
PRINCIPLE 02
Every Job Has Three Layers: Functional, Emotional, Social
Every job has three layers: functional, emotional, social
three layersemotionidentity
The principle, in one line
Functional is "get the task done," emotional is "how I want to feel," social is "how I want to be seen." The pricier and more visible the thing, the bigger the top two layers loom — pitch only the functional one and you hand away the two most profitable layers for free.
The three-layer value stack
Scene
You're selling team-collaboration software to a department manager.
✗ Only the functional layer
"We've got kanban, Gantt charts, auto-reminders, 100 integrations…" All features. But this manager's real job — features are only the bottom layer of it.
✓ Hit all three layers
Functional: "The whole team's progress on one screen — no more chasing people one by one."
Emotional: "You stop lying awake wondering which ball got dropped — you feel on top of it."
Social: "Next time you report upward, you pull up one clean progress chart, and your boss thinks your team is rock-solid." That last line is often the real reason they pay.
Why it works · mechanism & evidence
Why it works
Mechanism: social approval and status run on the same reward "currency" in the brain as money. Being looked up to, being recognized, signaling identity — these light up brain regions that overlap with getting a monetary reward. So "how others will see me" isn't a vain add-on; it's a real payoff the brain can price like hard cash. Name it out loud and you switch on a value the buyer never said aloud.
Neuroscience · social and monetary rewards share a circuit: Izuma, Saito & Sadato (2008, Neuron) — gaining a good reputation (social reward) activates the striatum, heavily overlapping the region activated by monetary reward, suggesting a "common neural currency" the brain uses to price social value. (cross-ref neuroscience on the reward system, psychology on social proof)
The emotional layer: buying leans hard on anticipated feeling — people often buy "the version of themselves / the mood they imagine afterward." This tracks with "emotion decides first, logic rationalizes after" (see this site's Buyer's Brain topic).
Evidence strength: the brain-imaging evidence is solid and replicated; the "three-layer" split itself is a practical framework (from the JTBD / consumer-behavior tradition) — useful, not a law.
Boundary: the layer mix varies by category. For toothpaste or screws, the functional layer all but dominates; for watches, bags, courses, career moves — anything visible and tied to identity — the emotional and social layers often outweigh function. Don't pitch identity to a screw buyer, and don't pitch only timekeeping accuracy to a luxury-watch buyer.
Probe all three layers (script)
One job, questioned on three layers
· Functional: "Once this is handled, what can you get more of / worry less about?"
· Emotional: "With this unsolved, what bugs you most? How would it feel once it's fixed?"
· Social: "If this goes well / badly, who notices? How do they see you?"
Common mistakes
Pitching all three as features. "Peace of mind" turned into "cuts communication cost 30%" — the number buries the feeling and misses.
Forcing the social layer, sounding slimy. Name the social layer along a concern they already hold; don't manufacture status envy. You can't invent a vanity they don't have — you'll only put them on guard.
Wrong layer for the wrong person. Saving money is the buyer's job; saving hassle is the user's job (finding each person's job is the Decision-Chain topic's work).
Key references
Izuma, Saito & Sadato (2008), "Processing of Social and Monetary Rewards in the Human Striatum," Neuron — the classic evidence that social and monetary rewards share brain regions. Anthony Ulwick, Jobs to Be Done: Theory to Practice — one operational source for splitting a job into measurable outcomes across functional / emotional / social.
Scripts to steal
Ready-to-use lines
"How do you want to feel once this is handled?" — opens the emotional layer.
"Who notices if this goes well?" — opens the social layer.
"It's not just faster — it makes you look on top of it." — lights the social layer in one line.
PRINCIPLE 03
Your Real Competitor Isn't a Rival — It's "No Change"
Your real competitor is "no change"
"do nothing" winsstatus-quo biasfour forces
The principle, in one line
Most deals aren't lost to a competitor — they're lost to the customer deciding to do nothing. They already have a "good enough" workaround; change means paying a certain cost for an uncertain gain. What you must beat first is that inertia, not the shop next door.
Will change happen: four forces in a tug-of-war
Scene
The customer clearly likes your product but keeps stalling on the signature: "Let me think about it."
✗ Just add more "pull"
"Let me knock off another discount / throw in a bonus!" You assume the pull is too weak — but what's blocking them is anxiety (afraid the switch breaks something) and habit (they can cope as is). Adding pull is flooring the gas with the handbrake still on.
✓ Release the handbrake (lower anxiety + loosen habit)
Lower anxiety: "Are you worried the switch will be messy and the team won't adopt it? We do a 14-day free migration + a dedicated onboarding person, and full refund anytime it doesn't fit — you carry almost no risk."
Loosen habit / amplify the pain of the status quo: "How many hours a week does your current setup burn on manual reconciliation? … That's X days a year. Do you keep paying that bill, or stop the bleeding now?"
Why it works · mechanism & evidence
Why it works
Mechanism: status-quo bias + loss aversion. "No change" is the default, and change means paying a certain cost (money, learning, switch risk) for an uncertain gain. The brain feels the pain of a certain loss more sharply than the pleasure of a possible gain, so the scale defaults toward "keep things as they are." Don't actively release those two forces and the customer agrees in words while staying put in action.
Status-quo bias: Samuelson & Zeckhauser (1988, Journal of Risk and Uncertainty), "Status Quo Bias in Decision Making" — a series of experiments shows a strong preference for keeping the default / current state, even when switching to a better option costs almost nothing.
Loss aversion: Kahneman & Tversky (1979), prospect theory — a loss hurts about twice as much as an equivalent gain feels good (loss aversion, λ≈2). This is why a "certain switching cost" can scare off a "larger potential gain." (cross-ref psychology, the Buyer's Brain topic)
The four forces (Bob Moesta & Chris Spiek, JTBD "switching forces") — push + pull vs anxiety + habit; a practical framework, not an experiment, but it translates the two hard findings above into four actionable handles.
Boundary: status-quo experiments mostly sit in economic-decision settings; the direction is robust and replicated. For any one deal, the strength of the four forces has to be asked and measured, not plugged into a formula.
Diagnose "why they won't move" (checklist)
What are they making do with right now? How much does it actually hurt? (Is the push enough?)
What's the biggest "what if" in their head about switching to you? (Where's the anxiety?)
What does "staying put" cost them a year in money / time / energy? Did I do that math for them?
Am I frantically piling on benefits (pull), or also lowering risk and loosening habit?
Common mistakes
Treating "no buy" as no competition. You think you're fighting a rival; the biggest opponent is "they decide to do nothing." Ignore it and you won't even know who you lost to.
Solving anxiety with discounts. Price isn't the real reason they hesitate; cutting it just makes them wonder "what's the catch." Kill anxiety with guarantees, trials, migration support.
Afraid to spotlight the cost of the status quo. Fearing you'll look like a fear-monger, you won't do the "cost of not changing" math — but showing someone a real cost is a duty, not manipulation.
Key references
Samuelson & Zeckhauser (1988), "Status Quo Bias in Decision Making" — the founding experiments on status-quo bias. Bob Moesta, Demand-Side Sales — the operational blueprint for the "four forces" and the "progress-making interview" through a JTBD lens.
Scripts to steal
Ready-to-use lines
"Your biggest competitor is the status quo."
"What's the cost of doing nothing?" — do the "no change" math for them.
"Let's de-risk the switch." — lower the anxiety force.
PRINCIPLE 04
Find the Job by Replaying the Moment of Hire and Fire
Find the job by replaying the moment of hire and fire
progress interviewask the past, not the futuretimeline
The principle, in one line
Don't ask "what features do you want" or "would you buy this someday" — ask "the last time you paid for / switched something like this, what actually happened?" The real job hides in one concrete purchase that already occurred, not in imagined futures.
From the masters
"People don't buy for logical reasons. They buy for emotional reasons — then justify with logic."— Zig Ziglar (paraphrase)
Scene
You want to figure out why a customer buys (or doesn't buy) something like your product.
✗ Ask the future / a hypothetical (you get polite lies)
"Do you think you'd use this feature?" "If we added X, would you buy?" To spare your feelings, they politely say "sure, sounds great." You collect a pile of fake signals, build the thing, and nobody buys.
✓ Ask about one concrete past time (rebuild the timeline)
"The last time you paid to fix a problem like this — when was it? What exactly happened that made you go 'no more, this has to change'?"
"How were you making do before that? Why did that day become the day you stopped making do?"
"What other options did you weigh? Why did you pick that one — and why did you later 'fire' it?" Every answer is anchored to something that actually happened; it can't be faked.
Why it works · mechanism & evidence
Why it works
Mechanism: memory of a concrete past event is far more reliable than an abstract future intention. Ask "would you buy someday" and you get imagination plus courtesy, contaminated by politeness and optimism; ask "why did you switch last time" and the answer is anchored to a real situation, date, and amount — hard to fabricate and awkward to. People predict their own future behavior badly but recall a specific thing they did fairly well.
The intention–behavior gap: Sheeran (2002) and Sheeran & Webb (2016) meta-analyses — "intending to" explains "actually doing" only weakly; a large change in intention tends to produce only about half as large a change in behavior. So "would you buy" is a weak signal.
The Mom Test (Rob Fitzpatrick) — the operational version of the same logic: ask about concrete past behavior and money actually spent; don't ask about future intent, don't float hypotheticals, don't ask them to rate your idea. (This site's Mom Test topic unpacks the method.)
Evidence strength: the intention–behavior gap is a robust meta-analytic finding (fairly hard); the "timeline / progress interview" is a JTBD operational method (framework-level — useful, not experimentally proven).
Boundary: for a brand-new category the person has never bought before, there's no "last time" to replay — then fall back to asking how they're currently coping with the problem (the status-quo workaround), which still beats asking about future intent.
The progress interview · five questions (script)
Replay the timeline of one real purchase
· Trigger: "What happened that day that made you start thinking you had to fix this?"
· Status quo: "How were you getting by before that?"
· Candidates: "What options did you consider? (Including 'just leave it.')"
· Choice: "Why did you pick that one? What was the moment that sold you?"
· Fire: "If you later dropped it, what was the one thing that made you say 'done with this'?"
Common mistakes
Mistaking future intent for real need. "Would you recommend it to a friend?" — warm to hear, weak at predicting.
Fishing for praise on your idea. "Do you think my idea's good?" — you'll only get polite lies; ask instead what they actually did in the past.
Taking the conclusion, skipping the situation. "Because it's cheap" is a conclusion, not a job; press on "what actually happened that day" to dig out the real trigger.
Key references
Rob Fitzpatrick, The Mom Test — how to ask so polite lies don't mislead you (this site covers it in its own topic). Paschal Sheeran (2002), "Intention–Behavior Relations: A Conceptual and Empirical Review" — source of the intention–behavior gap meta-analysis.
Scripts to steal
Ready-to-use lines
"Walk me through the last time you…" — replay one concrete past.
"What were you using before?" — ask the status quo / old solution.
"What finally made you pull the trigger?" — ask the trigger moment.
Your Day 4 Action
No reading, no reflecting — do one concrete thing this week:
Pick one real thing you're actually selling (a product, a service, an idea, even "yourself" in a job hunt) and write down three things:
(1) The job — in what situation, to make what progress, would they "hire" you? Write it as "When I ___, I want to ___, so I can ___." (2) The three layers — what are the functional / emotional / social layers of this job? (Which layer have you never once pitched?) (3) The real rival — if they don't pick you, it's most likely not a competitor but "keep coping with what / do nothing." What is it?
Then rewrite one opening line using these three. Boundary reminder: the job is stable, solutions get swapped — don't fall in love with your product, fall in love with the job, and see the better solution before your customer does.
Think It Through
1. How is "find the job" different from last time's "understand the buyer's brain"? Isn't it the same thing reworded?
Complementary, not repetitive. The Buyer's Brain topic is about "how people decide" — emotion first, logic after, loss aversion, status-quo bias: a universal set of decision mechanics. Today's JTBD is about "what this one person, right now, specifically wants to get done" — it lands those general mechanics on one customer, one situation, one concrete piece of progress. The former tells you roughly how human nature runs; the latter is the probe you aim at this deal: same status-quo bias, but only by pinning down their current job and the old workaround they're coping with do you know which force to release. Stacked together they're complete — mechanism plus landing point.
2. I sell a plain commodity (screws, tissues). Where's the "emotional or social layer"? Isn't that forced?
Don't force it — a commodity's job is often functional-dominant, and hammering identity there just sounds slimy and annoying. The three-layer frame isn't "stuff every layer full"; it's "first judge which layer this deal's center of gravity sits on." For screws and tissues, the job is usually "reliable supply, no stock-outs, no quality incidents, an easy life for procurement" — and note that last one already carries a bit of emotional layer (making the buyer feel at ease, not blamed). So even for a commodity there's often an overlooked soft line: not emotion about the product, but emotion about dealing with you — dependable, no worries, you've got their back if something breaks. That line is frequently exactly where you can command a premium among identical commodities.
3. The customer can't even articulate what they want, and can't answer "why did you buy last time." Now what?
Totally normal — people genuinely can't articulate their own real motives (the reasons they give afterward are mostly logical rationalizations). So don't expect them to "tell" you the job; your work is to reconstruct it. Don't ask "why," ask "what exactly happened that day" — ask for facts, sequence, details (what time, with whom, what they'd tried before, how urgent it felt). Pile up enough facts and the job surfaces on its own, often truer than what they'd say out loud. If there's no concrete past at all (a brand-new category), step back and watch how they're currently coping with the problem — that makeshift workaround is a living fossil of their job.