Quick answer
Jobs to Be Done is a way to understand demand by examining the progress a customer seeks in a particular circumstance. Customers effectively hire products, services or workarounds to do a job and can fire them when another solution fits better. JTBD research reconstructs real choice: the trigger, prior struggle, alternatives, anxieties, habits and desired outcome. Teams use the evidence to define opportunities, design offers and position them around the job rather than demographics or features alone.
What is Jobs to Be Done?
Jobs to Be Done is a demand-side perspective on why customers choose and switch. It focuses on the progress a person seeks in a circumstance and treats products, services and workarounds as candidates hired to help produce that progress.
A job is not the product task alone. Drilling a hole may describe a functional task, but a useful job also includes situation, desired outcome and relevant emotional or social consequences. Context determines which trade-offs matter and why action occurs now.
JTBD complements segmentation rather than making all segmentation unnecessary. Demographics and firmographics help estimate and reach markets. Job evidence explains causality and value. Teams often need both: who can be reached and what progress drives choice.
Where the JTBD perspective comes from
The language of customers hiring products is strongly associated with Clayton Christensen and collaborators and their work on innovation and customer choice. Their 2016 Harvard Business Review article argued that understanding the job can make innovation less dependent on correlations among customer attributes.
Jobs thinking has several practitioner traditions with different terminology and methods. Some emphasize the causal forces behind switching, others define measurable outcomes around a job, and the Value Proposition Canvas uses customer jobs alongside pains and gains. Do not assume every method carrying the label is identical.
The shared principle is to study choice in context. Rather than beginning with a solution category and asking which features people want, research begins with a struggle and reconstructs how customers moved from a prior way to a new one.
How to define a useful job
A useful job statement names the situation, motivation and desired progress without embedding the company's solution. For example: when a high-wear component fails during daily commuting, help me restore dependable protection quickly so I can keep working without replacing everything.
Keep the level of abstraction practical. Carry a backpack is too solution-specific; manage my life is too broad. The right level reveals several competing solutions while still suggesting meaningful success criteria and design choices.
Separate functional, emotional and social dimensions without forcing every job to contain all three. Functional progress concerns what changes in the world. Emotional progress concerns how the person wants to feel. Social progress concerns how the person wants to be perceived or participate.
The forces that shape switching
A common JTBD interview model examines four forces. The push of the present situation makes the old way less acceptable. The pull of a new idea makes change attractive. Anxiety about the new solution creates resistance. Habit and attachment to the current way also resist movement.
These forces explain why stated interest does not always become choice. A promising product may have strong pull but lose because implementation anxiety is high. A frustrating existing tool may remain because habits, data and organizational routines make switching costly.
Marketing and product work can act on different forces: clarify the trigger, demonstrate the outcome, reduce onboarding risk, support migration or make the first experience easy. Manipulative urgency is not required; the job is to help suitable customers make an informed transition.
Circumstance
Locate the situation and trigger that make progress necessary now.
- What was happening?
- Why did the person act now rather than earlier?
Progress
Define the functional, emotional and social change the customer seeks.
- What should be different afterward?
- How will the customer judge success?
Forces
Understand what pushes and pulls a change and what creates anxiety or habit.
- What made the old way unacceptable?
- What made the new way attractive or risky?
Competition
Identify every solution customers consider for the same progress.
- What else could do the job?
- When is doing nothing good enough?
Design and test
Translate job evidence into an offer and validate whether it improves choice and outcomes.
- Which barriers should we remove?
- Which capabilities and proof matter?
How to conduct a JTBD interview
Recruit people who recently made, abandoned or seriously considered the relevant choice. Recent events produce richer timelines than general opinions. Include switchers from different alternatives, losses and people who remained with the old way.
Reconstruct the story chronologically. Ask about the first thought, passive looking, trigger, active search, alternatives, conversations, decision moment, purchase, first use and later evaluation. Request specific details: where the person was, what happened next and what evidence changed confidence.
Avoid pitching or asking what the person would buy in an imaginary future. The interview seeks causal evidence from actual behaviour. Follow contradictions with curiosity, distinguish recalled fact from interpretation and do not convert one vivid story into a market conclusion.
- Recent relevant choice or struggle
- Timeline reconstructed from first thought
- Trigger and prior workarounds identified
- Push, pull, anxiety and habit explored
- All alternatives and nonconsumption included
- Functional, emotional and social progress considered
- Success and disappointment examined
- Patterns compared across interviews
Synthesize jobs without inventing certainty
After interviews, code situations, triggers, desired outcomes, forces, alternatives and decision criteria. Look for recurring causal patterns, not merely repeated words. Two customers may describe different products but share a job; two similar customers may hire the same product for different jobs.
Separate evidence from hypotheses. A job map can organize learning, but it does not estimate market size or willingness to pay. Combine qualitative patterns with surveys, behavioural analysis, concept tests and commercial experiments.
Prioritize jobs using importance, dissatisfaction with current solutions, frequency or value of the circumstance, strategic fit and ability to reach customers. A frequent job with good alternatives may be less attractive than a narrower, high-stakes job poorly served today.
Jobs to Be Done example
The commuter example shows why the product category is not the job. The customer considers repair, replacement, borrowing and delay. The repairable bag wins only if it helps make dependable progress with acceptable price, trust and effort.
A commuter's backpack zip fails before an important work trip. The person has tolerated minor failure for months but now fears equipment damage and disruption.
Daily laptop travel, accumulated wear and an imminent trip create a high-stakes trigger. The old bag is no longer dependable enough.
Carry work equipment confidently every day and recover from wear without replacing the entire bag. Feel prepared and responsible rather than careless or wasteful.
Repeated failure pushes change and a repairable system pulls. Higher upfront price and doubt about future parts create anxiety; familiarity with cheap replacement creates habit.
Options include another inexpensive backpack, specialist luggage, a repair shop, temporary tape, borrowing a bag or delaying until after the trip.
The offer needs proven laptop protection, available replacement parts, a simple repair path and evidence that reduces anxiety about long-term support.
The job should explain the causal situation and desired progress. A broad ambition such as be productive is usually too abstract to guide design.
Use JTBD in product, marketing and service
In product strategy, jobs identify outcomes and barriers worth solving. They guide capability and experience choices without becoming a feature voting system. A team may address anxiety through proof or onboarding rather than adding product complexity.
In positioning, the job supplies relevant context, alternatives and value. Copy can recognize the trigger and desired progress using customer language, while evidence addresses switching concerns. Avoid using invented quotations or pretending every buyer shares one job.
In service design, the job can span before and after purchase. Teams can support setup, recovery, maintenance and switching, making the total solution more effective than the core product alone.
How to test a job-based strategy
Test whether the job predicts meaningful differences in choice and outcome. Compare conversion, adoption, time-to-value, retention and satisfaction among customers in the identified circumstance. Ask after use whether the solution delivered the progress and which alternative would be chosen next time.
Run message and concept experiments that isolate the job, barrier or proof, but avoid reading clicks as full validation. A job can attract attention while the product, price or delivery remains inadequate. Combine behavioural demand with successful use and viable economics.
Monitor circumstances and competition. New tools can do the same job differently, and changes in work or regulation can weaken the trigger. Job definitions should evolve when causal evidence changes.
Common JTBD mistakes
The first mistake is rewriting a feature as a job, such as manage replaceable zips. This preserves the solution and prevents discovery of competing ways to make progress. The second is making the job universal and motivational, such as live better, which cannot guide a trade-off.
Another mistake is interviewing only loyal customers. They explain current success but can hide barriers faced by noncustomers and losses. Include people using substitutes and those who decided not to act.
Finally, a job statement is not validation. Teams must still estimate the market, test willingness to change, build capabilities and evaluate outcomes. The framework improves the question; it does not remove uncertainty.
A useful job explains why a person acted in a circumstance and what progress made one solution preferable to every real alternative.
Frequently asked questions
What is a Job to Be Done?
It is the progress a customer seeks in a particular circumstance, including the outcome and relevant functional, emotional or social dimensions.
Who created Jobs to Be Done?
The modern field has several contributors and method traditions. Clayton Christensen and collaborators strongly popularized the hiring metaphor and job-based innovation perspective.
What are the four forces in JTBD?
Push of the current situation, pull of the new idea, anxiety about the new solution and habit or attachment to the present way.
How is JTBD different from a persona?
A persona describes a representative user or customer. JTBD explains the causal situation and progress driving a choice. One persona can have several jobs, and different people can share a job.
How many JTBD interviews are needed?
There is no universal number. Interview until important patterns are understood across relevant alternatives and additional interviews add little, then test those qualitative hypotheses with broader evidence.
Sources and further reading
- Harvard Business Review: Know Your Customers' Jobs to Be Done ↗Christensen, Hall, Dillon and Duncan on job-based demand and innovation
- Harvard Business School: Know Your Customers' Jobs to Be Done ↗Harvard Business School publication record for the 2016 article
- Strategyzer: The Value Proposition Canvas ↗Official tool connecting customer jobs with pains, gains and designed value
- Strategyzer: Capture Customer Jobs, Pains and Gains ↗Behaviour-focused customer-interview guidance from Strategyzer