Jobs to be done (JTBD): definition and examples
Jobs to be done (JTBD) is a way of understanding customers through the progress they are trying to make in a given situation, rather than through their attributes. In this view, customers “hire” a product to get a job done and switch as soon as something else does it better. Clayton Christensen popularized the idea, and Tony Ulwick and Bob Moesta developed it further with different methods.
Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.
Why it matters for a PM
JTBD helps a PM see the real competition, which includes spreadsheets, habits and doing nothing, and describe needs without locking them into a solution. It provides a stable language for discovery, positioning and the roadmap, because a job changes far more slowly than the technologies serving it.
Example
A carpooling app team believes it sells “a cheaper ride.” Interviews about real recent trips show that the main job is “getting to work on time without depending on an unreliable train.” The product then highlights driver punctuality and backup options rather than price.
Key points
- A job is phrased without a solution: verb, object and context (“cook a healthy dinner in twenty minutes after work”).
- It has functional, emotional and social dimensions.
- Interviews focus on a recent purchase or switch, retraced step by step.
- The job story format, “When… I want to… so I can…”, puts the situation first.
Common mistakes
- Phrasing the job as a product feature.
- Defining jobs too vague to guide any decision.
- Presenting JTBD as a single method when several schools coexist.
Go further with Module
The courses and lessons that cover this concept: