Jobs to Be Done (JTBD)
People don't buy products, they hire solutions to get a job done. Understand the job to be done, not the user profile.
Description
Jobs to Be Done (JTBD) is an innovation theory stating that customers do not buy products but "hire" them to accomplish a functional, emotional, or social job, making it possible to uncover true purchase motivations independent of demographic characteristics. Conceptualized by Tony Ulwick (Strategyn) as early as 1991 and popularized by Clayton Christensen (Harvard Business School) in The Innovator's Solution (2003) and then Competing Against Luck (2016), JTBD was further enriched on the practical side by Bob Moesta (The ReWired Group) with the Switch Interviews method. Your personas describe who the user is ("Marie, 34, CMO, Paris"), but when you launch a feature "for Marie," nobody uses it. Why? Because you segmented by demographic profile, not by what people are actually trying to accomplish. Jobs to Be Done reverses this logic with a powerful metaphor: nobody buys a drill; they hire "a hole in the wall to hang a picture before the in-laws visit tomorrow." The job blends three dimensions: functional (making the hole), emotional (not stressing out), and social (showing you are capable). It is the McDonald's milkshake case that best illustrates the framework's power. Clayton Christensen discovered that 40% of milkshakes were sold before 8:30 a.m., to solo commuters. The "job" was not "treat yourself to a dessert" but "fill a boring commute while having something filling." The real competitor was not Burger King; it was a banana or a bagel. By reframing the offering around the job (thicker, longer to drink), McDonald's multiplied sales by 7. Tony Ulwick's Outcome-Driven Innovation approach, built on JTBD, boasts an 86% success rate in new product development, five times the market average. JTBD does not replace personas; it complements them by revealing the deep motivations that demographics alone cannot capture.
Objectives
- Explore opportunities
- Identify problems
- Understand users
- Foster innovation
Used by
- -Intercom (central framework of their product strategy, detailed in their blog and their book Intercom on Jobs-to-be-Done)
- -Basecamp (Jason Fried uses JTBD for all product and marketing decisions at Basecamp and HEY)
- -McDonald's (Clayton Christensen's milkshake case study, 7x sales increase after reformulating around the job)
Advantages
- Reveals the real competition. Discover that your competitor is not Product X, but "doing nothing" or "Friday evening manual workaround".
- Non-incremental innovation. Find jobs poorly served by existing solutions and create new product categories (86% success rate with Ulwick's ODI).
- Marketing messages that resonate. "Accomplish [job] in [time]" systematically outperforms "Software for [persona]".
- Progress-based prioritization. Develop features that better accomplish the core job, not those "requested" the loudest in meetings.
Limitations
- Requires in-depth qualitative interviews. Impossible to discover jobs via a multiple-choice questionnaire. Count 10-15 Switch Interviews of 45-60 minutes.
- Steep learning curve. The first JTBD interviews are often botched. You need practice asking the right questions and digging into circumstances.
- Can seem abstract to stakeholders. Explaining "we build for the job, not for Marie age 34" requires change management.
- Does not replace user testing. JTBD reveals the "why", but you still need to validate the "how" with prototypes.
How to apply Jobs to Be Done (JTBD)
- 1
Identify "switch" moments through interviews
Do not ask "Why do you use our product?" (generic answer guaranteed). Ask: "Tell me about the last time you decided to use [product] for the first time." Dig into the precise moment of the switch: what was the situation just before? What pushed you to look for a solution that day? What else did you try before? Conduct 10-15 Switch Interviews of 45-60 minutes. Output: a list of triggering circumstances.
- 2
Map the job across 3 dimensions
For each interview, identify the three layers of the job. Functional: what concrete task? ("generate a monthly sales report"). Emotional: what desired feeling? ("stop stressing the night before the exec meeting"). Social: what projected image? ("come across as rigorous and data-driven"). Create a Job Statement: "When [situation], I want to [functional job], so that [emotional/social outcome]." Output: 5-10 job statements from the interviews.
- 3
Analyze the 4 Forces of Progress
For each documented switch, analyze four forces. Push: frustration with the current solution ("Excel crashes with 50k rows"). Pull: attraction toward your product ("impressive demo"). Habits: attachment to the old solution ("the whole team knows Excel"). Anxieties: fears about change ("afraid of losing my formulas"). If Push + Pull is greater than Habits + Anxieties, the switch happens. Output: a forces diagram for each identified job.
- 4
Identify the real competition
Ask: "Before using our product, how did you accomplish this job?" List all answers: direct competing product, manual solution (Excel, paper), delegation to someone else, or "doing nothing." Frequent surprise: your real competitor is not Startup Y, but "doing it manually on Friday evening." This revelation completely changes your positioning and messaging. Output: an expanded competition map with alternative solutions.
- 5
Prioritize jobs: frequent and underserved
Create a 2x2 matrix: Job Frequency (how many times per month people encounter it) x Current Satisfaction (how well existing solutions solve the job). Frequent and underserved jobs represent the maximum opportunity. This is the core principle of Tony Ulwick's Outcome-Driven Innovation. Focus your roadmap on these jobs. Output: prioritization matrix with top 3-5 jobs to target.
- 6
Design solutions that accomplish the job better
For each priority job, brainstorm: "How can we accomplish this job 10x better, faster, or more simply than current solutions?" Do not copy competitor features, reinvent the way to accomplish the job. Instead of adding "more Excel templates", create "auto-generated report in 1 click". Prototype 2-3 radically different approaches. Output: 2-3 prototypes that attack the job from new angles.
- 7
Write marketing messages in JTBD mode
Transform your job statements into user-facing messages. Instead of "Our software has 50 features", write "Generate your sales report in 10 minutes instead of 3 hours". Address anxieties: "Import your existing Excel formulas in 1 click". Compare against the real competition: "No more staying late on Friday evenings". Output: 3-5 job-oriented marketing messages, testable via A/B.
- 8
Measure the job success rate
Define metrics per job: time to accomplish the job (before vs. after your product), job success rate, post-job satisfaction (job-specific NPS). Track these metrics monthly. If the job success rate drops, re-interview users: new competition? Change in circumstances? Your product no longer adapts? Output: job success rate dashboard with alerts for significant drops.