Jobs to Be Done (JTBD) is a framework for understanding customer needs by focusing on the underlying "job" or outcome a customer is trying to achieve, rather than the specific product features they request. Pioneered by Clayton Christensen, JTBD reframes product thinking around customer motivations and desired progress.
Why It Matters for Product Managers
JTBD shifts the conversation from "what features should we build?" to "what problem is the customer actually trying to solve?" This perspective helps PMs avoid the trap of building features nobody uses. When you understand the job, you can design solutions that genuinely serve customer needs, even if they look different from what customers initially requested.
The framework is particularly powerful for identifying competitive threats. Your real competitors are not just similar products but anything a customer might "hire" to get the same job done.
The JTBD Format
A job statement follows a specific structure: "When [situation], I want to [motivation], so I can [expected outcome]." This format keeps the focus on the context, desire, and goal rather than a specific solution. Good job statements are solution-agnostic and stable over time.
Practical Example
Instead of saying "users want a dashboard," a JTBD lens reveals: "When I start my workday, I want to quickly see which metrics changed overnight, so I can decide where to focus my attention." This deeper understanding opens up solution possibilities beyond just a dashboard.
Related prompt: Jobs to Be Done Interview Script