Jobs to Be Done (JTBD)
A framework arguing that customers don't buy products — they hire products to do a specific job in their lives; understanding the job reveals the true competitive set.
What Is Jobs to Be Done (JTBD)?
Jobs to Be Done (JTBD) is a framework pioneered by Clayton Christensen arguing that customers "hire" products to make progress on a specific job in their lives. The famous example: people don't buy a quarter-inch drill bit — they hire it to make a quarter-inch hole. Understanding the underlying job reveals competitive dynamics that product categorization obscures.
Also Known As
- Product teams: job stories, customer job mapping
- Strategy teams: outcome-based segmentation
- Research teams: jobs interviews, switch interviews
- Marketing teams: motivation-based targeting
How It Works
A milkshake chain studied why people bought milkshakes. The surprising finding: morning commuters "hired" milkshakes to make a boring drive more interesting while keeping them full until lunch — competing not against other desserts but against bagels, bananas, and donuts. Afternoon buyers hired milkshakes as a treat for a child after school, where the job was different (indulgence, parent-child bonding). Two entirely different jobs, same product — and redesigning the morning shake (thicker, with chunks to last longer) meaningfully grew morning sales.
Best Practices
- Do conduct switch interviews — ask customers what they were doing before buying your product and what triggered the switch.
- Do define the job as a desired progress, not as a demographic.
- Do identify functional, emotional, and social dimensions of the job. Most jobs have all three.
- Don't define the job at the product level ("the customer wants to use our software"). That's not a job.
- Don't assume one product = one job. The same product often serves multiple jobs for different customers.
Common Mistakes
- Confusing features with jobs. "Better UX" is not a job; "get my weekly report done before the Monday meeting" is.
- Doing JTBD research with leading questions. "Why did you buy our product?" biases the answer; "Walk me through what you were doing before you bought" doesn't.
Industry Context
JTBD is most useful in SaaS and consumer products where buyer motivations are complex and competitive sets are ambiguous. It's less useful in pure commodity markets where the job is trivially obvious. In B2B, JTBD interviews often reveal that the "product competitor" mental model is wrong — the real competition is a spreadsheet, a manual process, or an internal tool.
The Behavioral Science Connection
JTBD reframes customer behavior in terms of goals and context rather than attributes and demographics — consistent with construal level theory. It acknowledges that the same person "hires" different products in different contexts, which demographic segmentation misses entirely.
Key Takeaway
Your competition isn't what you think it is. Your real competition is whatever the customer was doing before they found you. Switch interviews reveal that truth; feature comparisons don't.