In product management, one of the biggest traps we fall into is thinking in terms of features, not outcomes. We obsess over “what” to build instead of asking “why” our users need it in the first place. This is where the Jobs to Be Done (JTBD) framework becomes a game-changer.
JTBD flips the script by focusing not on demographics, personas, or product specs—but on the job your customer is trying to accomplish. Simply put, people don’t buy products; they “hire” them to get a job done.
What Is Jobs to Be Done?
The concept was popularized by Clayton Christensen, who famously explained: “People don’t want a quarter-inch drill. They want a quarter-inch hole.”
That’s the essence of JTBD. Customers bring your product into their lives to solve a specific problem or achieve a desired outcome. The focus shifts from what the product does, to why it matters in their context.
For example:
- Customers don’t buy a fitness app just to track steps—they buy it to feel healthier, more confident, or to stay accountable.
- A project management tool isn’t just about task lists—it’s about helping teams feel organized, in control, and successful.
When you think like this, your roadmap and priorities become much clearer.
Why JTBD Matters in Product Management
- Cuts through feature bloat
Instead of cramming in “nice-to-have” features, JTBD ensures you’re building only what truly helps users succeed. - Improves alignment
It gives a common language for product, design, engineering, and even marketing. Everyone is rallying around the customer’s job, not isolated requirements. - Reveals unmet needs
By mapping out the jobs customers struggle to complete today, you uncover gaps where your product can add real value. - Enables differentiation
Competitors may offer similar features, but if you understand the emotional and functional jobs better, you can stand out.
Types of Jobs
Not all jobs are the same. JTBD typically breaks down into three categories:
- Functional Jobs: The core task the customer wants done. (E.g., “schedule meetings without back-and-forth emails.”)
- Emotional Jobs: How the customer wants to feel. (E.g., “feel confident that I’m not missing meetings.”)
- Social Jobs: How the customer wants to be perceived. (E.g., “be seen as organized and reliable by my team.”)
Great products address all three.
How to Apply JTBD
Here’s a practical process you can use:
1. Conduct Interviews
Talk to customers about the situations where they turned to your product—or a competitor’s. Don’t ask “What features do you want?” Instead, ask:
- What problem were you trying to solve?
- What alternatives did you consider?
- What pushed you to make a switch?
2. Map the Job
Frame jobs in this format:
When [situation], I want to [motivation], so I can [expected outcome].
Example:
“When I’m working remotely, I want to quickly see my team’s availability so I can schedule meetings without friction.”
3. Identify Struggles
Look for points of friction in how customers currently get the job done. That’s where opportunities live.
4. Prioritize Solutions
Focus your roadmap on the most critical jobs. Build features that directly remove friction or enhance outcomes.
5. Validate Continuously
Jobs evolve. As your customers’ context changes, revisit interviews and keep refining your understanding.
Real-World Example
Think about how Spotify applies JTBD. It’s not just “play music.” Their jobs include:
- Functional: “Help me discover new songs I’ll enjoy.”
- Emotional: “Make me feel energized during a workout.”
- Social: “Let me share playlists that reflect my personality.”
By addressing all three dimensions, Spotify became far more than a music player—it became part of people’s daily routines.
Bringing It All Together
JTBD isn’t about replacing personas or roadmaps; it’s about enriching them. It pushes us to ask deeper questions:
- Why does this feature matter?
- What job are we really being hired to do?
- How will success feel to the customer?
As product managers, we’re not just building software—we’re helping people make progress in their lives. JTBD is a framework that keeps us grounded in that mission.
Final Thought
Next time you’re debating a feature request, pause and ask: What job is the customer trying to get done here? If you can answer that clearly, you’ll make better decisions, cut through the noise, and build products that customers truly can’t live without.