Jobs to Be Done Framework: Why Customers Hire Your Product
Customers don't buy your product; they hire it to make progress in a specific situation. Where JTBD came from, how to interview for the job, and what it changes.
Share
The jobs to be done framework says customers don't buy products for their features; they "hire" a product to make progress in a specific situation, and "fire" it when something else does that job better. Developed by Clayton Christensen, Bob Moesta and Tony Ulwick, it changes who you see as competition, what you prioritise and how you describe your product.
Key takeaways
A job is the progress a person is trying to make in a particular circumstance, with functional, social and emotional dimensions (Christensen Institute).
JTBD has several originators: Ulwick dates his work to 1990, Moesta worked on it with Christensen from the mid-1990s, and Christensen popularised it in The Innovator's Solution in 2003 (Strategyn; Re-Wired Group).
You find jobs in stories about a recent switch, not in surveys. Ten interviews is a useful minimum (Re-Wired Group).
Four forces decide a switch: the push of the current situation, the pull of the new option, anxiety about the new option and the habit of the old one.
Most products serve a handful of jobs; the Re-Wired Group suggests aiming for 3–5 clear ones.
What is the jobs to be done framework?
The jobs to be done framework is a way of explaining why people buy and switch. The Christensen Institute defines a job as the progress people are trying to make toward a goal within particular circumstances; when that job arises, they "hire" a product or service to get it done (Christensen Institute).
Two ideas in that definition do most of the work:
Progress, not features. People want to get from where they are to somewhere better. Your product is a means.
Circumstance, not demographics. The same person hires different products for the same goal in different situations. A founder writing a spec at 11 p.m. before an investor meeting has a different job from the same founder planning a quarter.
What are the functional, social and emotional dimensions of a job?
Every job has three dimensions. The Christensen Institute's example is a family hiring a new home: space is functional, family dynamics and neighbours are social, and caretaking and achievement are emotional (Christensen Institute).
For a B2B product, take a head of product who buys a roadmap tool:
Dimension
What the person wants
What it means for the product
Functional
Agree priorities with the team in less time
Fast import, clear views, simple sharing
Social
Be seen by the CEO as running a disciplined process
Board-ready output, visible reasoning
Emotional
Stop dreading the quarterly planning meeting
Fewer surprises, decisions that hold
Feature requests usually describe the functional job. The social and emotional parts come out in interviews, and they often decide whether someone switches.
Who created Jobs to Be Done?
No single person. Attribution matters here, because the three originators built different versions of the idea.
Person
Contribution
When
Source
Tony Ulwick (Strategyn)
Applied process thinking to innovation; named his method Outcome-Driven Innovation and introduced it to Christensen
Lenny Rachitsky's podcast introduces Moesta as a co-creator of the framework (Lenny's Podcast, 2023). Strategyn, Ulwick's firm, says The Innovator's Solution cited its work.
Jobs as progress vs jobs as steps and outcomes
In practice there are two schools, and it helps to know which one a book or consultant follows.
Jobs as progress (Christensen, Moesta)
Outcome-Driven Innovation (Ulwick)
What a job is
Progress a person wants in a circumstance
What the customer is trying to get done, broken into a job map of steps with measurable desired outcomes
Main research method
Story-based interviews with recent switchers
Interviews, then a survey measuring the importance and current satisfaction of each outcome
Key output
The circumstances, forces and triggers behind a switch
A job map and a ranked list of underserved outcomes
Scale
About 10–20 interviews
Strategyn says a market typically has 50–150 measurable desired outcomes
Best for
Positioning, messaging, finding real competitors
Sizing opportunities in a well-understood market
Strategyn's job map breaks every job into 8 steps: define, locate, prepare, confirm, execute, monitor, modify and conclude. Strategyn also claims an 86% success rate for ODI projects; the page doesn't name who verified it, so treat that as the vendor's claim.
What is the jobs to be done milkshake example?
It is the story Christensen used most to explain the idea. A fast-food chain wanted to sell more milkshakes. Improving the product along obvious lines — thicker, sweeter, more flavours — didn't move sales. Researchers then asked a different question: what job are people hiring a milkshake to do?
Morning buyers turned out to be commuters. They hired the milkshake to fill them up, make a long, boring drive more interesting and be easy to hold in the car. In the afternoon, parents hired the same milkshake as a treat for their children (Christensen Institute). The Re-Wired Group's retelling notes the morning buyers came in around 8:00 a.m. and that a milkshake took about 20 minutes to drink — long enough to last the commute (Re-Wired Group).
The lesson is in the competitors. In the morning, the milkshake competed with bananas and bagels, not with other milkshakes. A thicker shake that lasts longer serves the morning job; a smaller, quicker one serves the afternoon job. One product, two jobs, two different improvements.
Two cautions: the story is told as an illustration, and we found no published dataset behind it. Use it to explain the idea, not as evidence that your own customers behave the same way.
Why does Jobs to Be Done beat personas and feature requests?
Because a job explains why someone switches, and personas and requests usually don't. Christensen, Scott Cook and Taddy Hall wrote in 2005 that about 30,000 new consumer products launch each year and over 90% fail, despite heavy spending on understanding customers (HBR, 2005). Their argument: companies segment by product and demographic attributes instead of by the job the customer needs done. In 2016, Christensen and co-authors cited a McKinsey poll in which 84% of executives said innovation was extremely important to growth, but 94% were dissatisfied with their innovation performance (HBR, 2016).
Artefact
Answers
Weakness
Use it for
Persona
Who is the customer?
Describes attributes that rarely cause a purchase
Recruiting, tone of voice
Feature request
What did the customer ask for?
Describes a solution, not the problem
Spotting where to dig
User story
What should the system do for a user?
Assumes the solution is already chosen
Delivery and acceptance criteria
Job statement
What progress is wanted, in what situation, and why now?
Takes interviews to get right
Strategy, positioning, prioritisation
Jobs are also more stable than solutions. The job "get paid on time by clients" has been served by paper invoices, email, accounting software and payment links; the job barely changed while the solutions turned over. Anchor your roadmap to the job and a new technology becomes a new way to serve it, not a reason to rethink your strategy.
How do you find the real job? A step-by-step JTBD interview
You find jobs in stories about real decisions. Surveys ask people to predict or rationalise; a switch interview reconstructs what actually happened.
Recruit recent switchers. Talk to people who started using your product, or left it, in the last few months, while they still remember the details. Include people who chose a competitor or a spreadsheet.
Plan at least 10 interviews. The Re-Wired Group says you can learn a lot from as few as ten varied interviews, that newcomers might do 15–20, and that this is not about statistical significance (Re-Wired Group).
Build the timeline. Start with "When did you first realise you needed something different? What was happening?" Then walk forward: what they tried, what they compared, what made them decide, and the first days of use.
Ask for specifics. Dates, places, people, numbers. "We were three weeks from launch and the spec still didn't match the designs" beats "planning was hard".
Map the four forces. For each interview, note what pushed them, what pulled them, what made them anxious and what habit held them back.
Look for patterns across interviews. Group circumstances that produced the same struggle. Aim for 3–5 clear jobs, not 20.
Write job statements and test them. Show them to the next interviewees and to your sales and support team. Rewrite until people say "yes, that's exactly it".
The four forces explain why people switch, or don't, even when a better option exists. The Re-Wired Group's guide covers them as push, pull, anxiety and habit (Re-Wired Group).
Force
Direction
What it is
Interview question
Push of the situation
Toward change
The struggle with the current way
"What was going wrong that made you look?"
Pull of the new solution
Toward change
The better future the new option promises
"What did you hope would be different?"
Anxiety of the new solution
Against change
Worries about switching
"What almost stopped you?"
Habit of the present
Against change
Comfort with the old way, even if it's worse
"What did you have to give up or relearn?"
A switch happens when push plus pull outweigh anxiety plus habit. Most teams invest only in pull — new features. Reducing anxiety (free migration, a trial with real data) and habit (import from the old tool) often moves more customers.
Worked example: from interviews to a job statement
The example is illustrative. Say a 5-person team building a feedback tool runs 10 switch interviews with customers who signed up in the last 60 days.
Push: 8 of 10 described a meeting where they couldn't answer "how many customers asked for this?"
Pull: 6 of 10 wanted to walk into planning with evidence attached to each request.
Anxiety: 7 of 10 worried about re-tagging hundreds of old requests.
Habit: 5 of 10 had a spreadsheet that "mostly worked".
Job statement: When I'm preparing for a planning meeting, help me show how many customers need each item, so I can defend priorities without a debate — without re-tagging two years of old feedback.
That last clause changes the roadmap: the team's next build is a one-click import of old feedback, not the new dashboard it had planned. Pull was already strong; anxiety was the blocker.
How does JTBD change prioritisation, roadmaps and messaging?
Prioritisation. Score opportunities against the job, not the request. In a RICE prioritisation, "impact" becomes "how much does this help customers make the progress they hired us for?"
Competition. List everything customers hire for the job today, including spreadsheets, agencies and doing nothing.
Onboarding and activation. The first session should deliver the progress customers hired you for. Our SaaS activation playbook shows how to measure it.
Journey mapping. The trigger stage of a customer journey map is the push force. Map it from interviews, not assumptions.
Retention. Customers fire products when a job changes or another option does it better. Many customer churn early warning signs are signs the job has moved.
Messaging. Lead with the progress and the situation ("Walk into planning with the evidence"), not the feature list.
When does Jobs to Be Done go wrong?
Jobs written at the wrong altitude. "Be successful at work" is too broad; "export a CSV" is a task. A good job names a situation and a measurable kind of progress.
Surveys instead of stories. Asking "what job do you hire us for?" gets you rationalisations. Reconstruct a real decision.
Interviewing only happy customers. People who left, or chose a competitor, show you the forces that work against you.
Treating JTBD as a one-off workshop. Jobs shift as markets change. Revisit them every time you plan a quarter.
Building for jobs nobody has. A clever feature that serves no clear job tends to go unused; see our analysis of why 80% of features go unused.
Confusing the two schools. Mixing story-based interviews with ODI's survey scoring without understanding either produces neither benefit.
Where Specky fits
Most teams lose the job between the interview and the roadmap: it ends up in a slide deck that's stale by the next quarter. Specky reads interviews, calls, tickets and other feedback into a Product Graph, so a job you identify stays linked to the customer evidence behind it. When you draft a spec, the quotes that support the job come along as inline citations. Its research agent, Alex, can also run customer interviews from a shareable link, so switch interviews don't wait on calendars.
Frequently asked questions
What is Jobs to Be Done in simple terms?
Jobs to Be Done says people buy a product to make progress in a specific situation, not because of who they are or what features it has. They "hire" a product for that job and "fire" it when something does the job better. Product teams use it to find real competitors, prioritise work and write messaging.
Who created the Jobs to Be Done framework?
Several people. Tony Ulwick dates his work to 1990 and named his method Outcome-Driven Innovation in 1999. Bob Moesta helped develop the theory with Clayton Christensen from the mid-1990s. Christensen popularised it in The Innovator's Solution in 2003 and in Harvard Business Review articles in 2005 and 2016.
What is the jobs to be done milkshake example?
A fast-food chain found that morning commuters hired milkshakes to stay full and make a long drive less boring, while parents in the afternoon hired them as a treat for children. In the morning the milkshake competed with bananas and bagels, not other milkshakes. One product served two jobs needing different improvements.
How many JTBD interviews do you need?
Start with at least 10 interviews of people who recently switched to or away from a product like yours. The Re-Wired Group suggests 15–20 if you are new to the method, and says the goal is understanding causes, not statistical significance. Stop when new interviews stop changing your job statements.
What questions do you ask in a JTBD interview?
Ask about a real, recent decision: when they first realised they needed something different, what was happening, what they tried, what almost stopped them and what made them decide. Probe for dates, people and numbers. Our free JTBD interview template has 21 questions across warm-up, core, probe and closing phases.
What is the difference between JTBD and Outcome-Driven Innovation?
Outcome-Driven Innovation is Tony Ulwick's version of JTBD. It breaks a job into a job map of 8 steps, lists the customer's desired outcomes and surveys customers on the importance and satisfaction of each to find underserved needs. The Christensen and Moesta version treats a job as progress in a circumstance and relies on story-based switch interviews.
GDPR-aligned. EU workspace data is stored in Frankfurt, Germany. GDPR and EU data Built in Vienna, Austria. A product of influence solutions fm GmbH (FN 675374y). Imprint 14-day trial. Card required, and nothing is charged until day 14. 30-day refund after subscribing. See pricing