Overview
Jobs to Be Done and Design Thinking are two of the most influential approaches in product development. Both put the customer at the center. Both aim to build products people actually want. But they start from different premises, use different methods, and produce different outputs.
JTBD asks: "What progress is the customer trying to make?" Design Thinking asks: "How can we deeply understand and creatively solve the customer's problem?" The distinction matters because the approach you choose shapes what you learn, what you build, and how you prioritize.
Quick Comparison
| Dimension | Jobs to Be Done | Design Thinking |
|---|---|---|
| Core question | What job is the customer hiring this product to do? | How might we solve this human problem? |
| Origin | Clayton Christensen, Tony Ulwick (business strategy) | IDEO, Stanford d.school (design practice) |
| Primary method | Switch interviews, outcome mapping | Empathy research, rapid prototyping, testing |
| Output | Job map, desired outcomes, underserved segments | Personas, prototypes, validated solutions |
| Scope | Strategy and positioning | Solution design and validation |
| Data type | Qualitative interviews (structured) | Mixed: observation, interviews, prototype feedback |
| Team involvement | PM and researcher led | Cross-functional (design, engineering, PM) |
| Best for | Knowing what to build and for whom | Knowing how to build it and what form it takes |
Jobs to Be Done: What It Does
JTBD starts from the premise that customers do not buy products. They hire products to make progress in a specific situation. The classic example: people do not buy a quarter-inch drill because they want a drill. They buy it because they want a quarter-inch hole. JTBD goes further: they want the hole because they want to hang a shelf, and they want the shelf because they want to organize their office so they can think clearly.
The Method
JTBD practitioners conduct "switch interviews" with recent customers. The goal is to understand the timeline of events that led someone to switch from their old solution to the new one. What was the situation? What was the struggle? What pushed them to look for alternatives? What pulled them toward this product? What anxieties held them back?
This produces a job statement: "When [situation], I want to [progress], so I can [outcome]." From there, teams map desired outcomes and identify which ones are underserved by current solutions.
Strengths
- Reveals the real motivation behind purchase decisions, not just stated preferences
- Produces durable strategic insights. Jobs are stable even as technology changes
- Clarifies competitive framing. Your competitor is whatever the customer was doing before, not just similar products
- Directly informs positioning, messaging, and roadmap priorities
Weaknesses
- Does not produce solutions. JTBD tells you what to solve, not how
- Interview technique is hard to learn. Poor interviewers get surface-level answers
- Can feel abstract to engineering teams who want wireframes and specs
- Less useful for products where the job is well understood and the challenge is execution quality
Design Thinking: What It Does
Design Thinking is a structured process for creative problem-solving. It moves through five phases: Empathize, Define, Ideate, Prototype, and Test. The process is iterative. Teams cycle back to earlier phases as they learn from prototypes and user feedback.
The Method
The Empathize phase involves observing and interviewing users to understand their context, needs, and emotions. Define synthesizes research into a clear problem statement. Ideate generates a wide range of potential solutions through brainstorming and structured creativity exercises. Prototype turns the best ideas into quick, testable artifacts. Test puts prototypes in front of users to gather feedback.
The user research guide covers research methods that feed into both the Empathize and Test phases.
Strengths
- Produces tangible prototypes that teams can test with real users before committing to a build
- Cross-functional format breaks silos. Engineers, designers, and PMs create together
- Diverge-then-converge structure prevents teams from jumping to the first solution
- Works at any fidelity, from paper sketches to clickable prototypes
Weaknesses
- Can produce solutions that feel creative but do not map to actual customer demand
- Workshop-heavy process can feel performative if not connected to real user data
- Requires facilitation skill. Poorly run ideation sessions produce predictable, safe ideas
- The "empathy" framing can lead teams to project their own feelings onto users rather than observing behavior
Different Entry Points
The most important distinction between JTBD and Design Thinking is where they enter the product development process.
JTBD enters at strategy. Before you decide what to build, JTBD helps you understand what progress customers are trying to make. It operates upstream of solution design. The output is a clear understanding of demand: these are the jobs, these are the outcomes, and these are the segments where current solutions fall short.
Design Thinking enters at solution design. Once you have a problem to solve (from JTBD, from customer feedback, from business goals), Design Thinking helps you explore how to solve it. It operates at the point where strategy meets execution.
This means they are not competing approaches. They are complementary phases. JTBD tells you the "what" and "for whom." Design Thinking tells you the "how."
When Each Approach Is Stronger
JTBD is stronger when:
- You are entering a new market and need to understand latent demand
- Your product has stalled and you need to understand why customers switch to competitors
- You need to align the team on which customer problems matter most
- Positioning and messaging are unclear, and you need a customer-driven foundation
- You want to identify product discovery priorities before investing in solution work
Design Thinking is stronger when:
- The problem is well-defined and you need creative solutions
- You need to design complex workflows or interactions where usability matters
- Cross-functional alignment is weak and you need a shared process for collaboration
- You want to validate ideas cheaply before committing engineering resources
- The user experience is the product differentiator
Combining Both Approaches
The most effective product teams use JTBD and Design Thinking as sequential phases in their discovery process.
Phase 1: JTBD research (2-4 weeks). Conduct 10-15 switch interviews with recent customers and churned users. Map the jobs, outcomes, and underserved segments. Identify which jobs to target.
Phase 2: Problem framing. Translate the top JTBD insights into Design Thinking problem statements. "How might we help [segment] achieve [underserved outcome] when [situation]?" This bridges the strategic output of JTBD into the creative process of Design Thinking.
Phase 3: Design Thinking sprints (1-2 weeks per cycle). Run ideation, prototyping, and testing focused on the JTBD-informed problem statements. Test prototypes with the same customer segments you identified in Phase 1.
Phase 4: Validate and prioritize. Use the RICE framework or weighted scoring to rank validated solutions for the roadmap.
This workflow prevents the two most common failure modes: building solutions to problems nobody has (skipping JTBD) and understanding problems perfectly but never converging on a buildable solution (skipping Design Thinking).
Common Mistakes
Treating JTBD interviews like feature requests. The goal is to uncover the situation and motivation, not to ask "what features do you want?" Switch interviews focus on past behavior (what did you do?) rather than hypothetical preferences (what would you want?).
Running Design Thinking workshops without real user input. Ideation without empathy research produces ideas that reflect the team's assumptions, not customer needs. The Empathize phase is not optional. It is the foundation.
Using JTBD for UX decisions. JTBD reveals what job to solve but says nothing about interface design, interaction patterns, or visual hierarchy. That is Design Thinking's domain.
Skipping the Define phase in Design Thinking. Teams often rush from empathy research to ideation without synthesizing findings into a clear problem statement. This produces scattered solutions that do not converge on a real need.
The Verdict
JTBD and Design Thinking are not interchangeable, and choosing between them is often the wrong framing. JTBD gives you strategic clarity about what customers need and why. Design Thinking gives you a structured process for creating and testing solutions. Use JTBD to identify the right problem. Use Design Thinking to find the right solution. Teams that practice both build products that are both strategically grounded and well-designed.