Core Idea
Definition
Jobs to Be Done is a framework that analyzes customer behavior in terms of the functional, emotional, and situational progress the customer is trying to achieve.
In Plain English
People do not really want your product. They want help making progress on something that matters to them.
Framework Structure
Components
Flow
Understand the situation -> Identify the progress sought -> Study current alternatives -> Design around the job to be done
How to Apply
- 1.Study the customer's situation rather than starting with your product
- 2.Identify what progress the customer is trying to make
- 3.Look at the alternatives currently being hired for that job
- 4.Understand the switching forces that push or resist change
- 5.Design positioning, product, and messaging around the job rather than the feature list
When to Use
- •Product strategy and positioning
- •Understanding customer demand more deeply
- •Finding substitutes you may have overlooked
- •Designing differentiated solutions
- •Any context where category labels are obscuring the real customer need
When NOT to Use
- •When the problem is purely internal and not customer-facing
- •When the job framing becomes too abstract to guide product choices
- •When the team confuses stated preference with actual situational behavior
- •When technical or operational constraints dominate more than customer progress
Example
Problem
A team wants to understand why users choose a lightweight note-taking app over a more powerful platform.
Application
- 1.Study the specific moments when users choose one tool over another
- 2.Identify the job as quick externalization and retrieval under low friction
- 3.Notice that more features can actually make the job worse in that context
- 4.Shape the product around the progress need rather than around maximal capability
Conclusion
The team sees demand more clearly because it is anchored in user progress instead of product category assumptions.
Takeaway
JTBD is powerful when it helps you see what people are truly hiring a solution to do.
Common Mistakes
- •Describing the job as a feature request instead of a progress need
- •Ignoring emotional and contextual dimensions of the job
- •Assuming direct competitors are the only alternatives
- •Relying on generic personas instead of concrete situations
- •Using JTBD language without changing the design or positioning choices
How to Practice
situation first interview
Ask customers about a specific moment of switching or choosing, not just general preferences.
alternative scan
List all the ways the customer currently gets the job done, including non-obvious substitutes.
progress language
Rewrite your value proposition in terms of the progress the user is making.
Related Cognitive Biases
feature fixation
Teams often overfocus on features and underfocus on the actual progress customers seek.
category blindness
Competitors can be missed when they come from different categories but solve the same job.
false consensus effect
Builders may assume users value the same things they value.
Related Frameworks
Related Skills
Variants & Extensions
Typical Failure Modes
- •Feature reframing only
- •Context loss
- •Substitute blindness
Further Reading
- Competing Against Luck by Clayton M. Christensen, Taddy Hall, Karen Dillon, and David S. Duncan
- The Four Steps to the Epiphany by Steve Blank
- The Innovator's Dilemma by Clayton M. Christensen