'Discover what customers truly need by analyzing the "job" they hire your product to do.
Jobs to Be Done Framework
Framework for discovering innovation based on a fundamental truth: customers don't buy products -- they "hire" them to do a specific job in their lives.
Core Principle
Job to Be Done = the progress a customer wants to make in specific circumstances.
Key elements of the definition:
- Progress (not goal, not solution) -- the customer wants to move from the current state to a better one
- Circumstances -- context determines the job, not customer attributes (demographics are useless)
- Hiring/Firing -- the customer actively chooses a product for the "job"
Scoring
Goal: 10/10. Rate product strategy or positioning 0-10 against the principles below. Always state the current score and the specific improvements needed to reach 10/10.
Three Dimensions of Every Job
Every job has three inseparable dimensions -- omitting any means failure:
| Dimension |
Question |
Example (milkshake) |
| Functional |
What does the customer need to do? |
Occupy myself during a boring commute |
| Emotional |
How do they want to feel? |
Have a small treat for myself |
| Social |
How do they want to be perceived? |
As a sensible parent (not buying donuts) |
Framework
1. The Job Statement
Core concept: A job statement captures the progress a customer seeks in a specific circumstance, in a structured format separating context, desired progress, and expected outcome.
Why it works: Forcing teams to articulate the job in the customer's language and circumstances prevents solution-first thinking and grounds innovation in real human progress.
Key insights:
- Format: "When [circumstances], I want to [progress], so I can [outcome]"
- Circumstances matter more than demographics -- the same person has different jobs in different situations
- A well-written job statement never mentions your product or any specific solution
- Jobs are stable over time; solutions change but the underlying job persists
Product applications:
| Context |
Application |
Example |
| New product ideation |
Define the job before brainstorming features |
"When I'm commuting alone, I want something to occupy me and satisfy hunger, so I'm not hungry until lunch" |
| Feature prioritization |
Evaluate whether a feature serves the core job |
Features that advance the stated job beat nice-to-haves |
| Positioning & messaging |
Ready to use wondelai-jobs-to-be-done?