What Is the Jobs-to-Be-Done Framework? Definition, Examples & How to Apply It
The Jobs-to-Be-Done (JTBD) framework is a theory of customer motivation that explains why people buy and use products in terms of the underlying “job” they are trying to accomplish. Developed by Clayton Christensen and popularized through his research on disruptive innovation, JTBD posits that customers don’t buy products for their features — they “hire” products to help them make progress in specific circumstances.
The key insight is that understanding the job — the underlying goal a customer is trying to achieve — is more durable, more actionable, and more predictive of product success than understanding the customer’s demographic profile or their stated feature preferences.
The Core Concept: The “Job”
In the JTBD framework, a “job” is not a task but a deeper goal or aspiration — the progress a person is trying to make in a specific situation. Jobs have three dimensions:
- Functional — The practical outcome the person wants to achieve (“I need to communicate this decision to my team efficiently”)
- Social — How the person wants to be perceived by others (“I want my team to see me as decisive and well-organized”)
- Emotional — How the person wants to feel (“I want to feel confident that nothing is falling through the cracks”)
A complete JTBD statement captures the situation, the motivation, and the desired outcome: “When I am [situation], I want to [motivation] so that [expected outcome].”
The Famous Milkshake Example
One of the most cited illustrations of JTBD comes from Christensen’s research on McDonald’s milkshakes. The research team found that many milkshakes were sold in the morning to commuters. When they investigated why, they discovered the job these customers were hiring the milkshake to do: making a long, boring commute more bearable while providing enough sustenance to stave off hunger until lunch.
The competitor was not other milkshakes — it was bananas, bagels, and breakfast sandwiches. Understanding the job revealed a completely different set of competitors and a completely different design brief (the milkshake needed to be thick enough to last the commute, engaging enough to not be boring) than understanding the product category or the customer demographic would have produced.
JTBD vs. Traditional Persona-Based Thinking
Traditional persona-based design focuses on who the customer is: their demographic profile, preferences, and behaviors. JTBD focuses on what the customer is trying to accomplish in a specific situation.
| Persona-Based | JTBD-Based | |
|---|---|---|
| Focus | Who the customer is | What the customer is trying to accomplish |
| Unit of Analysis | The person | The situation and goal |
| Question | What do people like this want? | What progress is this person trying to make? |
| Competitor Definition | Products in the same category | Anything that addresses the same job |
JTBD doesn’t replace personas — it complements them by adding a crucial motivational layer.
How to Conduct JTBD Research
JTBD Interviews
The primary research method. Unlike standard user interviews that ask “what features do you want?”, JTBD interviews explore the circumstances and motivations behind purchase and use decisions:
- What were you trying to accomplish when you first looked for this type of solution?
- Walk me through the moment you decided you needed to find something different.
- What were you doing before you found this product?
- What would you have done if this product didn’t exist?
Timeline of Purchase Analysis
JTBD research often maps the customer’s journey from first awareness of a problem to the purchase decision — revealing the “passive looking” and “active looking” phases, the triggering event, and the decision criteria that drove the final choice.
Applying JTBD in Product Development
For feature prioritization: Frame potential features as solutions to specific jobs. Prioritize features that address the most important, most underserved jobs.
For positioning: Lead with the job, not the feature. Customers respond to messages that acknowledge their situation and goal; features are only relevant as proof that the product can deliver the job.
For competitive analysis: Identify all the products and approaches that compete to do the same job — not just products in the same category.
For innovation: Look for jobs that are important and underserved. The opportunity is not in building a better version of existing products, but in finding jobs that nothing serves well.
Key Takeaways
The Jobs-to-Be-Done framework is one of the most powerful lenses in product management for understanding why customers behave the way they do. By shifting focus from what products are to what they help people accomplish, JTBD produces more empathetic product thinking, more compelling positioning, and more defensible prioritization decisions. The best product strategies are built on a deep understanding of the jobs customers are trying to do — and the confidence that the product does those jobs better than any alternative.