Jobs-to-Be-Done (JTBD)
Jobs-to-be-done says that people don't buy products — they 'hire' products to do a specific job for them. When you buy a drill, the job isn't 'have a drill' — it's 'have a hole in the wall.' Understanding the actual job changes how you design and market the product.
Jobs-to-Be-Done (JTBD) is a theory of customer motivation developed by Clayton Christensen that reframes product development around the underlying job a customer is trying to accomplish, rather than their demographic profile or stated product preferences.
Core premise:Customers don't buy products; they hire them to make progress in a specific situation. Understanding the "job" — the circumstance that triggers the hire, the desired outcome, and the competing alternatives (including non-consumption and workarounds) — produces more durable product insights than demographic persona analysis.
The JTBD interview structure focuses on the 'moment of hire': What triggered the customer to start looking for a solution? What alternatives did they consider? What specific outcome were they trying to achieve? What were they willing to give up to get it?
Functional vs. social vs. emotional jobs:Most purchases involve functional (outcome-focused), social (status-focused), and emotional (feeling-focused) dimensions. A comprehensive JTBD analysis surfaces all three.
Application in product development:JTBD reframes feature development. Instead of "what features should we add?" ask "what new jobs could we help customers accomplish, or what existing jobs could we help them do better?"
Key Takeaways
- JTBD focuses on the situation and desired progress, not the customer demographic profile
- The 'moment of hire' — what triggered the search for a solution — is the most revealing interview question
- Non-consumption (doing nothing) and workarounds are always part of the competitive set in JTBD analysis
- JTBD analysis often reveals that competitors are different from who product teams assumed
Common Questions
How is JTBD different from traditional user stories?
Traditional user stories describe feature requests ('as a user, I want...'). JTBD describes desired progress ('when I am [in this situation], I want to make progress toward [this outcome], so that [this result]'). JTBD focuses on outcomes, not solutions.
Can JTBD be used for B2B products?
Absolutely — JTBD is particularly powerful in B2B because B2B purchases often involve complex organizational jobs (political, process, and outcome jobs) alongside functional ones. JTBD helps untangle all three.