"People don't want a quarter-inch drill. They want a quarter-inch hole." — Theodore Levitt, cited by Clayton Christensen
Activation Conditions and Trigger Words
- Direct invocation: "Use JTBD to analyze...", "Jobs to Be Done breakdown...", "What product do users hire to complete..."
- Semantic triggers: when users describe product design and ask "what users really need", "how to do needs analysis", "competitor definition is vague", "user personas have no explanatory power"
- Combined invocation: "First use JTBD to define the need space, then use design thinking to develop solutions"
Method Framework Overview
The core of JTBD is not asking "who the user is", but asking "what job the user hires this product to complete". Through five principles—users hire products, functional/emotional/social three-dimensional Jobs, competition comes not only from the same category, consumers are not user personas, and firing products—it fundamentally redefines needs analysis and innovation opportunities.
Core principles (3-7, each must be accompanied by ≥2 cross-domain pieces of evidence)
Principle 1: Users Hire a Product for a Job
One-sentence definition: Users do not buy products; they "hire" products to complete a specific task.
Cross-domain evidence:
- FMCG field: A fast-food chain discovered that morning commuters "hired" milkshakes to complete the Job of "making the long, boring commute interesting". A milkshake is more filling than a banana, more convenient to eat in the car than a donut, and provides a longer time-consuming experience than a breakfast bar (Source: Christensen, Milkshake Marketing, HBS working paper, 2007)
- Furniture retail field: What IKEA users really hire is not wooden boards and screws, but the Job of "immediately and cheaply setting up a livable space". Traditional furniture retailers are hired for "high-quality furniture for lifelong use" (Source: Christensen et al., Competing Against Luck, 2016, Ch.4)
Application method: When analyzing the needs of any product/service, first ask "in what situation and to complete what task did the user use this product", and do not start from product features.
Limitation: Some consumption decisions lack a clear "Job" motivation (such as impulse buying and addictive behavior), and in such cases JTBD's explanatory power declines.
Principle 2: Functional/Emotional/Social Three-Dimensional Job
One-sentence definition: Every Job includes a functional dimension (what is completed), an emotional dimension (how one feels), and a social dimension (how others see it).
Cross-domain evidence:
- Automotive industry: The functional dimension of an SUV is "safely transporting people and cargo", the emotional dimension is "a sense of driving control and safety", and the social dimension is "an identity signal of success, sportiness, and family orientation" (Source: Christensen, Hall, Dillon & Duncan, Competing Against Luck, 2016, Ch.5)
- Coffee consumption: Starbucks users' functional Job is "ingesting caffeine", the emotional Job is "having a moment of relaxation and control amid busyness", and the social Job is "displaying the cultural taste of an urban white-collar worker" (Source: Klement, When Coffee and Kale Compete, 2016, Ch.3)
Application method: When analyzing any product, list all three dimensions at the same time. The functional dimension answers "what was completed", the emotional dimension answers "how one feels during/after use", and the social dimension answers "how others see you using this product".
Limitation: In B2B scenarios, the social dimension may be simplified to "professional image"; when decision-makers and users are separated in enterprise procurement, the three dimensions need to be analyzed separately.
Principle 3: Competition does not come only from similar products
One-sentence definition: A product's competitors are anything that can accomplish the same Job, including "doing nothing."
Cross-domain evidence:
- Food service/FMCG: A milkshake's competitors are not other milkshakes, but bananas (too hungry), donuts (inconvenient to eat in the car), breakfast bars (eaten too quickly), and boredom itself (hiring nothing). All of these compete for the Job of "making the commute less boring" (Source: Christensen, Milkshake Marketing, HBS, 2007)
- Entertainment/Publishing: Kindle's competitors are not only paper books and tablets, but also "sleeping," "scrolling social media," and "listening to podcasts"—they compete for the Job of "what do I do with these 30 minutes before bed" (Source: Klement, When Coffee and Kale Compete, 2016, Ch.1)
How to apply: When defining your product's competition, list all solutions that can accomplish the same Job, including non-similar products, DIY solutions, and hiring "doing nothing."
: Over-expanding the boundaries of competition may lead to analysis that is too diffuse. It is necessary to lock onto the same Job definition rather than expanding arbitrarily.: Over-expanding the boundaries of competition may lead to analysis that is too diffuse. It is necessary to lock onto the same Job definition rather than expanding arbitrarily.
Principle 4: Consumers are not user personas
One-sentence definition: Demographic characteristics (age, gender, income) cannot predict purchasing behavior; the Job is the real driver.
Cross-domain evidence:
- FMCG: The same milkshake is "hired" in the morning by 35-55-year-old male commuters to pass the commute time, and in the afternoon by mothers with children to soothe their children and express the maternal love of "an occasional indulgence." The demographic profiles are completely different but they hire the same product—because they have different sides of the same Job (Source: Christensen, Milkshake Marketing, HBS, 2007)
- Photography: Kodak's user persona showed that "every family needs a camera," but the Job users truly wanted to accomplish was "recording and sharing life's moments." When mobile phones accomplished this Job better, no matter how precise the persona was, it failed to predict Kodak's decline (Source: Christensen, The Innovator's Solution, 2003, Ch.4)
How to apply: Abandon personas like "25-35-year-old white-collar workers in first-tier cities" and replace them with "people who want to accomplish [Job] in [situation]."
: In some industries (such as healthcare and insurance), demographic characteristics are still effective risk stratification tools, and JTBD should be a supplement rather than a complete replacement.: In some industries (such as healthcare and insurance), demographic characteristics are still effective risk stratification tools, and JTBD should be a supplement rather than a complete replacement.
Principle 5: Abandoning a product is "firing" it
One-sentence definition: When users do not buy your product, it is not "churn," but "firing" it because they have found a more capable substitute.
Cross-domain evidence:
- Mobile phone industry: Users fired BlackBerry and hired iPhone, not because BlackBerry was bad, but because iPhone was more capable at the Job of "integrating mobile work + personal entertainment." BlackBerry kept optimizing the keyboard—but the keyboard was not the core of the Job (Source: Christensen, The Innovator's Solution, 2003, Ch.3)
- Video rental: Users fired Blockbuster and DVD rental stores and hired Netflix streaming, because the Job of "starting to watch the movie I want at home immediately" was accomplished better by streaming. Blockbuster kept optimizing store locations—that was not the bottleneck of the Job (Source: Christensen et al., Competing Against Luck, 2016, Ch.6)
How to apply: When analyzing user churn, do not ask "why did they leave," but ask "what substitute did they hire to accomplish the same Job, and in what way was that substitute more competent."
Limitations: Users firing a product may also be due to external factors (such as price changes or channel disappearance), and not all churn has a "more competent substitute."
Operational Protocol (Agentic Protocol)
Step 1: Problem classification — determine whether this method applies to the current problem
Applicable signals:
- Product/service demand analysis, needing to understand why users buy/why they do not buy
- Competitive boundaries are blurred, requiring a redefinition of the competitive landscape
- User personas cannot explain behavior, requiring a new framework for understanding users
- Growth stagnation or user churn, requiring identification of root causes
Not applicable signals:
- Technical architecture or infrastructure selection (apply first principles)
- Pure operational efficiency optimization (apply Kaizen improvement)
- Commodity markets that are already highly standardized with no room for differentiation
- The core of the problem is pricing strategy or channel strategy rather than demand understanding
Output: Applicable / Not applicable (with reasons) / Partially applicable (with recommendations)
Step 2: JTBD-style research — research dimensions must be derived from the core principles; do not use generic "search for relevant information"
Research dimensions(each dimension must be traceable to a specific core principle):
-
Job identification: In what situations do users want to accomplish what specific task? What solution are they currently using to accomplish it?
- Source principle: Principle 1 (users hire products)
- Method of operation: Describe the specific situation (when, where, with whom, and what triggered the need), then distill a Job statement in a "verb + noun" structure. Do not replace it with "users need XX feature."
-
Three-dimensional deconstruction: What are the functional, emotional, and social dimensions of this Job?
- Source principle: Principle 2 (functional/emotional/social three-dimensional Job)
- Method of operation: Describe each of the three dimensions in one sentence. Use objective actions for the functional dimension, the user's self-perception for the emotional dimension, and "how others view the person using this solution" for the social dimension.
-
Competitive landscape: What solutions (including non-category products, DIY, and doing nothing) are competing for the same Job?
- Source principle: Principle 3 (competition does not come only from similar products)
- Method of operation: List all competing solutions and mark each solution's "competence" (the degree of match with the Job across the functional/emotional/social dimensions). Must include a competence analysis of the "hire nothing" solution.
-
Hiring and firing history: What solutions has the user hired in the past? Why were they fired? Why is the new solution being kept now?
- Source principle: Principle 5 (abandoning a product is "firing" it)
- Method of operation: Draw the user's timeline, marking the triggering event at each switching point and "in what way the old solution was no longer competent."
-
Job-driven population definition: Regroup users by "people who accomplish the same Job" rather than "people who are demographically similar."
- Source principle: Principle 4 (consumers are not user personas)
- Approach: List user groups that have different demographic characteristics but share the same Job, and compare their differences and commonalities. Outputting personas such as "the target users are 25-35 year old white-collar workers" is prohibited.
Prohibited: Using generic instructions such as "search for relevant information" and "fully understand the background". All research dimensions must be derived from core principles.
Step 3: JTBD-style output — formatted output based on the analysis results
Output format requirements:
- Job statement: One-sentence Job description (verb + noun + context)
- Three-dimensional analysis table: Scores for the functional, emotional, and social dimensions respectively (competence 1-5)
- Competitive landscape: List the competence matrix of all competing solutions
- Hire/fire timeline: Key turning points and trigger events
- Job-driven population grouping: User grouping by Job rather than by persona
- Opportunity gap: List all dimensions that current solutions fail to satisfy adequately
- Mark confidence level (high/medium/low), and clearly explain dimensions with insufficient information
Applicable/not applicable judgment
| Question type | Applicability | Explanation |
|---|---|---|
| New product requirement definition | High | The most core application scenario of JTBD, defining the requirement space starting from the Job |
| Competitive analysis and market positioning | High | Break category thinking and discover cross-category competitors |
| User churn reason analysis | High | The "fire" perspective directly locates the root cause of churn |
| Growth strategy formulation | High | Discover Job dimensions that are not adequately satisfied |
| Technology architecture selection | Low | JTBD analyzes the demand side, while technology selection is a supply-side issue; first principles are more suitable |
| Pricing strategy optimization | Medium | It can analyze how much users are willing to pay to complete the Job, but economic tools need to be combined |
| Standardized commodity market | Low | When the functional dimension is highly homogenized, JTBD has limited differentiation power; Five Forces analysis is more suitable |
Typical case library
Success cases
-
Milkshake marketing case(Food service/2007)
- Problem: A fast-food chain's milkshake sales stagnated, and all improvement attempts (thicker, more flavors, larger) had no effect
- Method application: Christensen's team observed purchasing behavior and found that 40% of milkshakes were bought alone in the morning. After in-depth interviews, they found that commuters "hired" the milkshake to complete the Job of "making the long, boring commute interesting without making a mess"
- Result: Improving the milkshake for this Job (thicker to extend drinking time, adding fruit pieces for variety, moving checkout forward to speed up the purchase process) significantly increased sales
- Source: Christensen, Milkshake Marketing, HBS working paper (2007); Competing Against Luck (2016), Ch.1
-
Snapchat replaces Facebook in the teen market(Social media/2012-2015)
- Problem: Facebook believed that teen attrition was because the product was not cool enough, and kept adding features
- Method application: From a JTBD perspective, teens hire Snapchat to do the job of "instant, evidence-free, low-pressure communication with friends," while Facebook does the job of "maintaining a permanent digital identity." The two jobs are completely different
- Result: Snapchat did not have to compete with Facebook on features, but instead became the leader of a completely different job
- Source: Klement, When Coffee and Kale Compete (2016), Ch.4; Christensen et al., Competing Against Luck (2016), Ch.7
-
Airbnb redefined travel accommodation(Travel/2008-2015)
- Problem: The traditional hotel industry competed from a "room" perspective—bigger rooms, more amenities, higher star ratings
- Method application: Airbnb understood that what users hire is not "a bed," but "a temporary place to experience the city like a local." This is a job that traditional hotels cannot do
- Result: Airbnb created an entirely new accommodation category and did not compete with hotels on star ratings and amenities
- Source: Christensen et al., Competing Against Luck (2016), Ch.8
Failure cases
-
Segway's miscalculation about the transportation revolution(Transportation/2001)
- Problem: Segway claimed it would change urban transportation, and venture capital supported this grand vision
- Misuse: It started from "cool two-wheel self-balancing technology," rather than from the "urban traveler's job." The user's job in urban travel is "convenient, low-cost travel from A to B," and Segway fell short of existing solutions on all three dimensions: cost ($5,000), convenience (cannot be taken on public transit), and social acceptance (strange looks from passersby)
- Lesson: Cool technology does not equal doing the user's job better. If the job itself is already satisfied well enough by existing solutions, the new technology must have an overwhelming advantage in competence
- Source: Christensen et al., Competing Against Luck (2016), Ch.3; Klement, When Coffee and Kale Compete (2016), Ch.5
-
Google Glass's consumer failure(Wearables/2013-2015)
- Problem: Google Glass designed a large number of features starting from "what wearable technology can do"
- Misuse: It never answered "what job does the consumer want a computer worn on the face to do?" People being filmed felt violated (negative score on the social dimension), and on the functional dimension phones could already accomplish most tasks, with no clear must-have job
- Lesson: If a product is not significantly more competent than existing solutions on at least one dimension, there is no reason for it to be "hired"
- Source: Ulwick, Jobs to Be Done: Theory to Practice (2016), Ch.2
Misuse detector (≥3 misuse patterns, must cover: method-problem mismatch, skipping key steps, complexity exceeding limits)
| Misuse signal | Detection logic | Warning message | Recommended action |
|---|---|---|---|
| Method-problem mismatch | The user uses JTBD to analyze technology selection, engineering architecture, or platform migration | "JTBD is a needs-understanding tool and is not suitable for technical decisions. For technology selection problems, it is recommended to use first principles to analyze from physical and cost constraints." | Recommended alternative method: first principles or TRIZ |
| Skip Job identification and design features directly | When describing the product, the user only lists features and does not mention user situations and Jobs | "JTBD must start with Job identification; features are solutions to Jobs, not the starting point. First answer: in what situation does the user need to complete what task?" | Guide back to the Job identification process in Step 2, Dimension 1 |
| Ignore emotional/social dimensions | The user analyzes only the functional dimension, and all analysis revolves around "what to complete" | "JTBD requires three-dimensional analysis. The current analysis lacks the emotional dimension (how users feel) and the social dimension (how others perceive them). Ignoring these two dimensions may miss core needs." | Add complete three-dimensional analysis |
| Equate Jobs with "functional requirements" | The user's Job statement contains only functional verbs (such as "send faster") and does not include situation and emotion | "A Job is not a list of functional requirements. Please rewrite it in the format 'In [situation], I want to [verb] so that [outcome]', ensuring it includes the situation and the user's desired outcome state." | Rewrite the Job in the format of situation + verb + desired outcome |
| Confirmation bias | The user only seeks evidence supporting the current solution hypothesis and does not seek counter-evidence on "why users do not hire" | "JTBD requires analyzing both hiring and firing. The current analysis lacks examination of 'what users fired' and 'why they did not hire us'." | Add firing analysis and competence analysis of "hiring nothing" |
Honest boundaries (≥3 specific limitations; empty phrases like "cannot replace professional advice" are prohibited)
-
JTBD does not analyze technical feasibility: JTBD reveals the Job space on the demand side and does not involve technical feasibility on the supply side. Discovering the Job of "making waiting time not boring" does not mean it can be technically achieved. It needs to be combined with technical feasibility analysis before entering solution design.
-
Mining latent needs depends on research quality: Users often cannot clearly express their Jobs, especially the emotional and social dimensions. If research stays only at questionnaires and shallow interviews, the analysis result is "garbage in, garbage out." Effective JTBD analysis requires observation methods, in-depth interviews, and user diary studies.
-
Jobs evolve over time, and snapshots expire: A user at age 25 may choose a shared bike when hiring "transportation tools," while at age 35 with children they hire the same type of Job to an SUV. If a JTBD snapshot is not updated regularly—especially when the social environment and technical conditions undergo major changes—it will become invalid.
-
Limited differentiation in standardized commodity markets: In markets where the functional dimension is completely homogenized (such as tap water and basic electricity), the emotional and social dimensions of three-dimensional analysis also have limited differentiation, and JTBD does not provide valuable differentiated insights.
-
A single Job perspective may miss systemic needs: JTBD focuses on a single Job, but users often run multiple related Jobs at the same time. For example, "find a place to eat lunch" and "use the lunch break to socialize" are two related but different Jobs. Analyzing only one may miss innovation opportunities in the intersection area.
Research sources (the proportion of primary sources must be >50%)
| # | Source | Type | Primary/Secondary | Weight |
|---|---|---|---|---|
| 1 | Christensen, The Innovator's Solution (2003), Ch.3-4 | Work | Primary | High |
| 2 | Christensen, Hall, Dillon & Duncan, Competing Against Luck (2016) | Book | Primary | High |
| 3 | Christensen, Milkshake Marketing, HBS working paper (2007) | Working Paper | Primary | High |
| 4 | Ulwick, Jobs to Be Done: Theory to Practice (2016) | Book | Primary | High |
| 5 | Christensen, Cook & Hall, Marketing Malpractice, HBR (2005) | Paper | Primary | High |
| 6 | Klement, When Coffee and Kale Compete (2016) | Book | Primary | Medium |
| 7 | Moesta, Demand-Side Sales 101 (2020) | Book | Primary | Medium |
| 8 | Intercom, Intercom on Jobs to Be Done (2016) | Book | Secondary | Low |
This Skill was generated by Forge Skill — Forging Thinking Tools Generated