Jobs-to-be-Done (JTBD) is a framework for understanding the progress a customer is trying to make in a particular situation. Instead of focusing only on a user’s demographic profile or requested feature, JTBD asks what they are trying to accomplish, what triggers the need, and what makes current solutions insufficient. SaaS teams use it to guide discovery, positioning, product design, and prioritization.
How the JTBD Framework Works
A job often includes a practical outcome and may also involve emotional or social needs. For example, a team might adopt project management software not simply to “use a board,” but to coordinate work, spot delays early, and feel confident that commitments will be met.
- Situation: What is happening when the need appears?
- Motivation: What progress does the customer want to make?
- Current workaround: How do they solve the problem today?
- Desired outcome: What would a successful solution make easier or better?
- Constraints: What limits their choices, such as time, budget, risk, or internal approval?
How to Use JTBD in SaaS
- Interview customers about real events. Ask about the last time they faced the problem, what prompted action, and what alternatives they considered.
- Look for patterns. Identify recurring situations and desired outcomes across interviews.
- Map existing solutions. Include spreadsheets, manual work, competing products, and doing nothing.
- Turn insights into product choices. Use the job to guide onboarding, workflows, messaging, and feature priorities.
- Validate the direction. Test whether the proposed improvement helps customers make progress and whether they adopt it.
JTBD vs. Related Concepts
| Concept | Main focus | Difference |
|---|---|---|
| Jobs-to-be-Done | Progress a customer seeks in a situation | Centers on motivation and desired outcomes |
| Buyer persona | Profile of a target buyer or user | Describes characteristics and context |
| Feature request | A proposed product capability | May be one solution to an underlying job |
| Product-market fit | How well a product meets a market need | Broader evidence of sustained value and demand |
Benefits of JTBD
- Helps teams avoid building features without understanding the problem.
- Reveals competition from non-software workarounds.
- Improves positioning by describing outcomes customers care about.
- Connects product decisions to real user situations and constraints.
Best Practices
Ask about past behavior
Specific stories about a recent decision are usually more informative than asking what someone might do in the future. Explore the trigger, steps, alternatives, and trade-offs.
Avoid jumping to a solution
When a customer asks for a feature, ask what they are trying to accomplish and why the current process falls short. The best solution may be simpler or different from the initial request.
Include the full buying context
In B2B SaaS, the user, buyer, administrator, and approver may have different jobs. Understand how their needs interact during evaluation, purchase, implementation, and ongoing use.
Keep insights connected to evidence
Document interview examples and distinguish recurring patterns from individual opinions. Validate findings through product usage, experiments, and follow-up research.
Common Mistakes
- Writing jobs as feature names instead of customer progress.
- Assuming every customer in a segment has the same motivation.
- Relying only on hypothetical survey responses.
- Using JTBD as a one-time workshop instead of an ongoing learning process.
- Ignoring adoption and outcomes after a product change.
Frequently Asked Questions
Is JTBD only for product teams?
No. Product, marketing, sales, customer success, and research teams can use it to understand why customers choose, adopt, or leave a solution.
How is a job different from a feature?
A job describes the progress the customer wants to make. A feature is one possible way to help them make that progress.
Can JTBD help with positioning?
Yes. It can help teams explain the situation they serve and the outcome they support, rather than listing capabilities without context.