Discovery & customer understanding · Theory / research lens
Jobs to Be Done
Understand the progress people seek in a particular circumstance and why they switch solutions.
Start here · 5-minute visual lesson
People choose products to make progress in a situation. Study the struggle and the switch—not just the person or feature request.
Think of it like this: A customer “hires” a product like they hire a taxi: for progress from one situation to another.
- 1Find the struggle
- 2Rebuild the decision timeline
- 3Map push, pull, habit, and anxiety
- 4Name the progress sought
“Freelancers want more invoice themes.” The team follows stated preferences.
“Freelancers want confidence they will be paid without harming the client relationship.” The solution space changes.
Learn by deciding
Why prettier invoices did not help
Freelancers ask for customization. What should you interview about?
Ask about the last invoice that felt risky: what happened, what they tried, and when they considered changing tools.
Several mention awkward follow-ups with clients. What is the job?
Help me feel certain I will be paid without damaging the client relationship.
What competes with invoicing software?
Anything that gets the progress done: spreadsheets, email, an accountant, avoiding the conversation, or doing nothing.
01 · Understand
In plain English
JTBD explains demand through the progress a person seeks—not demographics or product categories—and includes functional, social, and emotional dimensions.
Origin and context
JTBD has several related schools. Clayton Christensen and collaborators popularized demand-side “hiring” and progress language; Tony Ulwick developed outcome-driven innovation and job mapping. Treat these as related traditions, not perfectly interchangeable recipes.
The problem it solves
Personas and feature feedback may describe who bought and what they asked for without explaining the causal struggle that produced a switch. JTBD uncovers circumstances, competing solutions, and desired progress.
The concepts, explained
Learn the vocabulary first. Each concept changes a decision you will make when using the framework.
Job
The progress a person is trying to make in a particular situation. It should describe the change they seek without naming your product.
Functional, social, and emotional dimensions
A choice must work practically, feel right personally, and make sense socially. Ignoring any one dimension can make a strong feature lose.
Hire and fire
People “hire” a solution when it helps them progress and “fire” it when another option—including a workaround or doing nothing—works better.
Forces of progress
Push and pull encourage a switch; habit and anxiety resist it. A new product wins only when the forces for change become stronger.
Desired outcomes
The concrete criteria people use to judge whether the job was done well, such as less uncertainty, less time, or fewer mistakes.
02 · Deep dive
Go beyond the definition
Follow the reasoning inside Jobs to Be Done, then challenge it before you use it.
1 of 4mental model
The mental model
What changes in the way you see the problem
Job
progress sought in a circumstance
Functional, social, and emotional dimensions
Use this concept to examine the problem from a distinct Jobs to Be Done perspective.
Hire / fire
adopt or leave a solution
Forces of progress
push, pull, habit, anxiety
Desired outcomes
criteria for getting the job done well
Reasoning trace
Watch each step earn the next one
An invoicing SaaS team interviews 12 freelancers who recently changed tools. The recurring job is not “create invoices”; it is “help me feel certain I will be paid without damaging the client relationship.” The team prioritizes polite escalation, payment visibility, and an accountant handoff over new invoice themes. It tests a prototype with time-to-follow-up and confidence ratings.
- 01Frame
Choose a recent switch, purchase, workaround, or abandonment.
Decision question: What did the customer stop doing to adopt this? - 02Interrogate
Interview for a concrete timeline; avoid hypothetical preference questions.
Decision question: Which circumstance changes the priority of the job? - 03Interrogate
Capture the old situation, triggering event, search, trade-offs, and decision.
Decision question: What did the customer stop doing to adopt this? - 04Interrogate
Map push, pull, habit, and anxiety without forcing every quote into a box.
Decision question: Which circumstance changes the priority of the job? - 05Interrogate
Synthesize recurring circumstances and progress patterns.
Decision question: What did the customer stop doing to adopt this? - 06Interrogate
Write a solution-neutral job statement.
Decision question: Which circumstance changes the priority of the job? - 07Decide
Design and test experiences against desired outcomes and competing solutions.
Decision question: What did the customer stop doing to adopt this?
Failure-mode lab
Which mistake is most likely on your team?
Choose one to turn it into a control for your next workshop.
Context adaptation
The canonical version is only a starting point
Startups can study 6–10 recent switches; enterprises can connect job segments to outcome surveys. In B2B, distinguish job executor, buyer, approver, and implementation roles.
Signals it fits
- Customers switch among surprising categories
- Segmentation predicts poorly
- A team needs durable opportunity language
Signals to switch tools
- You need only a usability diagnosis of one interface
- There is no observable behavior or recent decision to study
- The team wants demographic targeting, not demand causality
Now use the framework. The workbench below turns your own context into a first decision draft.
Work my problem03 · Apply
How to use Jobs to Be Done
- 01
Choose a recent switch, purchase, workaround, or abandonment.
- 02
Interview for a concrete timeline; avoid hypothetical preference questions.
- 03
Capture the old situation, triggering event, search, trade-offs, and decision.
- 04
Map push, pull, habit, and anxiety without forcing every quote into a box.
- 05
Synthesize recurring circumstances and progress patterns.
- 06
Write a solution-neutral job statement.
- 07
Design and test experiences against desired outcomes and competing solutions.
04 · See it work
A worked example
An invoicing SaaS team interviews 12 freelancers who recently changed tools. The recurring job is not “create invoices”; it is “help me feel certain I will be paid without damaging the client relationship.” The team prioritizes polite escalation, payment visibility, and an accountant handoff over new invoice themes. It tests a prototype with time-to-follow-up and confidence ratings.
Business case study
Evidence-based reconstruction
The Christensen Institute describes a homebuilder learning that the dining-room table represented transition anxiety for condominium buyers. The Atlas reconstructs the decision logic from the published account; it does not claim access to the original research data.
Across company types
Startups can study 6–10 recent switches; enterprises can connect job segments to outcome surveys. In B2B, distinguish job executor, buyer, approver, and implementation roles.
05 · Work your problem
Turn the framework into a result
Explore the mechanics
Copy the working template
Switch event: First thought: Push of current situation: Pull of new solution: Habit holding back: Anxiety about change: Progress sought: Functional / social / emotional outcomes:
06 · Use judgment
Where it helps—and where it breaks
Use when
- Customers switch among surprising categories
- Segmentation predicts poorly
- A team needs durable opportunity language
Do not use when
- You need only a usability diagnosis of one interface
- There is no observable behavior or recent decision to study
- The team wants demographic targeting, not demand causality
Advantages
- Reveals real competition and context
- Produces solution-independent language
- Connects research to positioning and innovation
Limitations & criticisms
- Schools use conflicting terminology
- Retrospective interviews contain recall bias
- Jobs can become vague slogans without behavior
Common failure modes
- Writing “use our app” inside the job
- Asking what people would buy
- Treating one interview as a market segment
Often confused with
Personas organize shared characteristics; JTBD organizes causal circumstances and desired progress. They can be complementary.
Practical checklist
Reflection questions
- What did the customer stop doing to adopt this?
- Which circumstance changes the priority of the job?
07 · Check
Five-question knowledge check
Key takeaways
- Understand the progress people seek in a particular circumstance and why they switch solutions.
- Reveals real competition and context
- Schools use conflicting terminology
08 · Go deeper
Sources and further reading
- Jobs to Be Done TheoryClayton Christensen Institute · Christensen Institute
JTBD definition, circumstances, progress, and functional/social/emotional dimensions.
- Building Your Job MapStrategyn · Strategyn
Job mapping sequence and solution-independent outcomes.