Jobs to Be Done (JTBD) is a way to understand why people choose, use, or replace a product in a particular situation. It focuses on the progress someone is trying to make, the context around that need, and the alternatives they consider. It helps teams investigate demand without assuming that a feature list explains the purchase.
What a “job” means
A job is not necessarily a task a customer performs inside a product. It can include a functional outcome, such as preparing a reliable report, as well as emotional or social outcomes, such as feeling confident in a decision or presenting work credibly to colleagues. The circumstances and constraints matter: the same person may choose differently when the timing, stakes, or available alternatives change.
A simple job statement
One useful format is: “When [situation], I want to [make progress], so I can [desired outcome].” Treat it as a research prompt, not a universal template. A statement should describe a real circumstance and outcome rather than smuggle in a preferred product or solution.
For example: “When several teams need the same campaign status, I want one dependable view of progress so I can spot a blocked handoff before launch.” This is more useful for exploration than “I need a dashboard,” because it leaves room to learn whether a dashboard, a workflow change, or another solution fits the job.
Research questions that reveal context
- What happened that made the person look for a change?
- How did they handle the situation before, and what was frustrating or sufficient?
- Which alternatives did they consider, including doing nothing?
- Who else influenced the decision or had to adopt the change?
- What risks, constraints, or trade-offs shaped the choice?
- How did the person decide that the outcome was successful?
Ask for a recent example and let the person describe the sequence in their own words. Avoid leading questions such as “Would this feature save time?” or “Do you like our solution?” Those invite agreement without revealing what happened, what mattered, or what would cause a different choice.
Apply JTBD to a product or marketing decision
Compare interviews across situations, identify recurring triggers and desired outcomes, and note meaningful differences between segments. Then test whether the current product, message, and buying experience help people make that progress. JTBD can inform product requirements, positioning, onboarding, and campaign content, but it does not tell a team the answer without evidence.
Combine the lens with a broader market research process and a clear value proposition. Research can reveal the job and alternatives; the value proposition explains why an offer is a credible choice for a particular buyer.
Common JTBD mistakes
- Writing the job as a feature request instead of a desired outcome.
- Assuming every customer hires a product for the same reason.
- Interviewing only current successful customers and missing people who chose another option.
- Confusing a memorable quote with evidence about how common a need is.
- Using a framework label without changing the research or decision process.
JTBD is most useful when it leads to better questions about context, alternatives, and progress. Keep the underlying observations visible, test patterns with additional evidence, and revisit the job when customer behavior or market conditions change.
How did this article land?
Choose one reaction. You can change it anytime.