Jobs to Be Done (JTBD) is a framework that explains customer behavior through the "job" they are trying to accomplish, not the product they use. People do not buy products. They hire products to make progress in their lives. Understanding the job reveals opportunities that feature-level thinking misses.
The Core Concept
When someone buys a drill, they do not want a drill. They want a hole. When someone buys a CRM, they do not want contact management. They want to close more deals with less effort. The "job" is the progress the customer is trying to make in a specific circumstance.
A job statement follows this format: "When [situation], I want to [motivation], so I can [expected outcome]." Example: "When I am preparing for a board meeting, I want to quickly see which features drove the most revenue, so I can justify next quarter's product investment."
Functional, Emotional, and Social Jobs
Most products address functional jobs (get a task done). But purchasing decisions are driven by emotional and social jobs too:
Functional: "Help me track feature requests in one place." This is what the product literally does.
Emotional: "Make me feel in control of a chaotic backlog." This is why the user feels relief when using the product.
Social: "Help me look competent when presenting priorities to executives." This is the external perception the user gains.
Products that address all three job types win against products that only solve the functional job. The user persona builder can help you map these three dimensions for each target user.
How to Discover Jobs
Switch interviews. Interview recent customers about the moment they decided to switch to your product (or a competitor's). Ask what triggered the search, what alternatives they considered, and what made them choose. This reveals the job in context.
Timeline mapping. Walk backward from the purchase decision. What was the first thought? What pushed them to act? What pulled them toward a specific solution? What anxieties almost stopped them?
Observation. Watch customers use your product (or competitors' products) in their natural environment. What workarounds do they create? Workarounds are unmet jobs. The OST Builder helps structure the opportunities you discover into a visual tree.
Applying JTBD to Prioritization
Once you have identified the key jobs, prioritize them by importance and satisfaction (similar to opportunity scoring). Jobs that are highly important but poorly served are your biggest opportunities.
Feed those jobs into your RICE scoring as the "impact" component. A feature that directly addresses an underserved job with high importance scores higher than a feature that addresses a well-served job.
The prioritization guide covers how to integrate JTBD insights into your scoring process.
Common Mistakes
Making jobs too broad. "Manage my product" is not a job. It is a category. Good jobs are specific and situational. "Quickly see which features are blocking a major customer renewal" is actionable.
Confusing jobs with solutions. "I want a Gantt chart" is a solution, not a job. "I want to see how a delay in one workstream affects the launch date" is the job. Always ask "why?" until you reach the underlying progress the customer seeks.