Jobs To Be Done

What is it?

Jobs To Be Done is a discovery lens that explains customer behaviour by the progress someone is trying to make in a situation - the "job" they "hire" a product to do - rather than by the product's features or the customer's demographics.

What problem does it fix?

It stops two expensive mistakes: building features nobody actually hired your product for, and defining your market by who customers are ("35-year-old urban moms") instead of what they're trying to get done.

Most famous flameouts are "we forgot the real job" stories. Kodak thought it sold film and cameras; the real job was "keep and relive my memories - and show them off." Blockbuster thought it rented movies; the real job was "entertain me tonight without friction or late fees." In both cases a competitor served the job better, and the category leader's features became irrelevant.

The one big idea

People don't buy products. They hire them to make progress in a specific situation. Nail the job, and your roadmap, positioning, and pricing get a lot clearer.

The shortest version: nobody wants a drill → they want a hole → they actually want a photo on the wall they're proud of. The drill is just hired help.

Key terms

Job - the progress someone wants. Not a task, not a feature.
Hire / Fire - adopt a product / churn to a better one.
Situation (context) - the trigger that switches a job on. The same person hires a $4 airport coffee and instant coffee at home - different situation, different job.
The three sides of a job - Functional (the task), Emotional (how they want to feel), Social (how they want to be seen). Most differentiation hides in the last two.
The Four Forces - Push (frustration with today) + Pull (attraction of the new) drive the switch; Worry (anxiety) + Habit (inertia) resist it.
The struggling moment - the point where someone is fed up enough to start looking. This is where demand is created.
Opportunity - a need that is important but underserved. That's your roadmap gold.

The steps - how to actually do it

Find recent switchers and interview them. People who just started using you (or a rival). Walk them back to the moment they got fed up. This is the "switch interview."
Write the job statement: "When [situation], I want to [motivation], so I can [outcome]." Keep your product's name out of it.
Capture the three sides - functional, emotional, social.
Map the Four Forces - what pushes/pulls them, and what worry/habit blocks them.
List their wants and score them - Importance vs. Satisfaction. The big gaps are your opportunities.
Build, prioritize, and message around the job - sell the progress, not the parts.

What you get out of it

Shared job statements the whole team aligns on - your real customer-need definition.
A switching map (the Four Forces) that tells you exactly what to fix to win and retain customers, and what's driving churn.
A prioritized opportunity list - what to build first, grounded in underserved needs rather than opinion.
Sharper positioning and a tighter value proposition. Dropbox's "your files, anywhere" is a job statement, not a feature list.
A market defined by the job, which reveals your true competitive set - including habits, spreadsheets, and "doing nothing."

When to use it - and when not to

Reach for JTBD when you're:

Running early discovery for a new product or feature.
Deciding what's on the roadmap, or diagnosing churn and weak retention.
Repositioning, refreshing messaging, or building a go-to-market story.
Entering a new market and sizing up real competition.

Don't over-rely on it when you're:

Doing pure optimization where the job is obvious and stable (load time, conversion tweaks → use analytics and A/B testing).
Building to a hard spec (regulatory, hardware).
Trying to produce market-size numbers - JTBD gives you the what and why; pair it with quantitative research for how much and willingness to pay.

JTBD tells you what to build and why - not how to build it well. Usability, design, and execution are still on you.

Strengths and weak spots

Strengths

Durable. Jobs outlast technology - "get me there reliably" survived horses, taxis, and ride-hailing.
Reveals true competition. The milkshake competed with bananas and bagels, not other milkshakes.
Customer-centred and cross-functional - engineering, design, and support can all use it.
Excellent for innovation and positioning.

Weak spots

Can feel subjective if done sloppily.
The two "schools" (story-based vs. measurement-based) confuse newcomers.
Bad job statements are easy to write.
It's a demand-side lens - it won't tell you how to execute.
Interview quality is skill-dependent.

Common mistakes

Hiding a solution inside the job. "The job is to use our app" is wrong - a real job survives even if every product disappeared.
Confusing your ICP's demographics with the job. A teenager and a CEO hire the same meditation app for the same job: "quiet my racing mind so I can sleep."
Wrong altitude. Too granular = a feature; too broad = "be happy."
Skipping the emotional and social sides because they're hard to measure - that's usually where you differentiate.
Trusting survey stated-preferences over real switching behaviour.
Treating JTBD as a one-off workshop instead of an ongoing discovery habit.

How it fits with other frameworks

Personas - JTBD swaps "who they are" for "what progress they want," and usually fixes shallow personas.
Design Thinking / Double Diamond - sharpens the Discover / Define stages so you solve the right problem.
Lean Startup / MVP - tells you which hypothesis is worth testing first.
Value Proposition Canvas (Strategyzer) - literally runs on "customer jobs, pains, and gains." JTBD is its engine.
Kano model + Opportunity Scoring - natural partners for prioritization.
Product-Market Fit & North Star - PMF is nailing an important, underserved job; your North Star metric should trace back to it.

A full example - Uber

Situation: It's 11pm, you're on a cold street with no car, and you need to get home.

Job statement:

"When I need to get somewhere and don't have my own car, I want a reliable ride quickly and the certainty it's actually coming - so I can get home without stress."

The three sides:

Functional - get from A to B.
Emotional - feel safe and in control.
Social - don't look stranded or cheap.

Real competition: taxis, walking, transit, calling a friend, or giving up and staying out.

The Four Forces that won the switch:

Push: no cabs, no shows, cash hassle, zero visibility on arrival.
Pull: live map, ETA, cashless, set price.
Worry: is a stranger's car safe? will the price surge?
Habit: "I've always just hailed one on the corner."

What Uber built and said: the live map and ETA killed uncertainty (push → pull); ratings and trip-sharing reduced the safety worry; cashless removed friction; upfront pricing addressed the surge worry. None of those are "transport features" - they're all forces work. By serving the job instead of the category, Uber competed against the entire way cities moved.

JTBD in famous products

The job line - and the real competitor it's fighting - for products you already know:

Netflix - "When I want to relax, give me something good to watch instantly." → competes with YouTube, scrolling, and sleep.
Slack - "When work is scattered across tools, give me one place to talk and find things." → competes with email and meetings.
Airbnb - "When I travel, let me stay somewhere local and personal." → competes with hotels and staying with family.
Spotify - "When I want the right music for this moment, give it to me instantly without managing files." → competes with radio and silence.
Headspace / Calm - "When my mind won't switch off, give me a simple way to relax and sleep." → competes with scrolling, wine, and TV.
Duolingo - "When I want to learn a language but lack time and discipline, give me short, fun daily practice." → competes with classes and giving up.
Canva - "When I need something that looks professional but I'm not a designer, let me make it fast." → competes with PowerPoint and hiring a designer.

Who made it?

JTBD grew from several thinkers, not one:

Theodore Levitt planted the seed in Marketing Myopia (1960) - the "people want a hole, not a drill" idea.
Clayton Christensen (Harvard) made it mainstream through The Innovator's Solution (2003) and Competing Against Luck (2016), home of the milkshake story.
Tony Ulwick built the rigorous, measurable version - Outcome-Driven Innovation - in What Customers Want (2005) and Jobs to Be Done: Theory to Practice (2016).
Bob Moesta & Chris Spiek developed the switch interview and the Four Forces, captured in Demand-Side Sales 101 (2020).
Alan Klement wrote the clearest popular introduction, When Coffee and Kale Compete (2016).