One of the biggest mistakes in product management is focusing too much on features instead of outcomes. Customers don’t “buy” products—they hire them to do a job in their lives. This is the essence of the Jobs-to-Be-Done (JTBD) framework, a powerful way to understand customer needs and design products that truly deliver value.
What is Jobs-to-Be-Done?
JTBD is a framework that shifts the focus from demographics and personas to the actual job a customer is trying to accomplish.
- Customers don’t want a drill; they want a hole in the wall.
- They don’t want streaming subscriptions; they want entertainment on demand.
- They don’t want a project management app; they want to feel in control of work and deadlines.
The key is recognizing that the “job” represents progress customers seek, not the product itself.
Why JTBD Matters
- Moves Beyond Features: Instead of feature-chasing, you solve real problems.
- Uncovers Hidden Needs: Customers often can’t articulate solutions, but they can describe struggles.
- Guides Innovation: Jobs stay stable over time, even if technology changes.
- Sharpens Positioning: Framing around jobs clarifies why customers should choose you.
How to Apply JTBD in Product Management
1. Conduct Customer Interviews
Go beyond “What do you want?” Instead, ask:
- What problem were you trying to solve?
- What alternatives did you consider?
- What frustrations did you face?
This uncovers the context behind decisions.
2. Identify Functional, Emotional, and Social Jobs
- Functional: The practical task (e.g., “order groceries quickly”).
- Emotional: How the customer wants to feel (e.g., “reduce stress of meal planning”).
- Social: How they want to be perceived (e.g., “be seen as a good provider”).
Great products deliver across all three.
3. Map Out Job Stories
Instead of writing features as “As a user, I want…”, try:
“When I [situation], I want to [motivation], so I can [desired outcome].”
Example: “When I’m commuting, I want to listen to short podcasts so I can make use of my time effectively.”
4. Translate Jobs into Opportunities
Ask:
- Are customers underserved by current solutions?
- Are there pain points in existing workflows?
- Can you make the job faster, cheaper, or more delightful?
Real-World Examples
- Spotify: Customers don’t hire it for “music access.” The job is “curated, mood-based listening anywhere.”
- Slack: Not about “chat features.” The job is “make team communication effortless and centralized.”
- Duolingo: Customers don’t want “language lessons.” They want “to feel confident speaking a new language daily.”
Avoiding Pitfalls
- Don’t confuse jobs with personas. Different demographics may share the same job.
- Don’t treat jobs as static. Technology, culture, and context can shift how jobs are solved.
- Don’t focus only on functional jobs. Emotional and social aspects often drive adoption.
Final Thoughts
JTBD pushes product managers to ask a deeper question: What progress is my customer trying to make? By answering that, you stop chasing shiny features and start building products that customers actually stick with—because they’re the right fit for the job.
Products win not when they have the most features, but when they get hired again and again for the job that matters most.