Customers don't buy products—they hire them to get jobs done. Understanding this distinction transforms how you discover opportunities, prioritize features, and position your product. The Jobs-to-be-Done (JTBD) framework shifts focus from demographics and personas to the fundamental motivations driving customer behavior.
What is Jobs-to-be-Done?
Jobs-to-be-Done is a theory of customer motivation developed by Clayton Christensen and refined by practitioners like Bob Moesta and Alan Klement. The core insight: people "hire" products to make progress in their lives.
The famous example:
A fast-food chain wanted to improve milkshake sales. Traditional research focused on demographics: Who buys milkshakes? What do they want in a milkshake?
JTBD research asked different questions: What job are customers hiring the milkshake to do?
They discovered: Early-morning commuters hired milkshakes to make their boring commute more interesting and keep them full until lunch. The "job" wasn't "provide nutrition" or "taste good"—it was "make my commute less boring while keeping me satisfied."
This insight led to different improvements than demographic research would have suggested.
The JTBD Structure
A well-formed job statement follows this pattern:
"When [situation], I want to [motivation], so I can [desired outcome]."
Examples:
Slack:
"When I need to coordinate with my team quickly, I want to send instant messages in organized channels, so I can keep projects moving without endless email threads."
Uber:
"When I need to get somewhere and don't have a car readily available, I want reliable transportation at the push of a button, so I can arrive on time without the hassle of calling cabs or parking."
Grammarly:
"When I'm writing important communications, I want to catch errors and improve clarity, so I can look professional and be understood clearly."
Notice each statement includes:
- Situation - The context triggering the need
- Motivation - What they're trying to accomplish
- Outcome - The ultimate goal or progress they're seeking
Why Jobs-to-be-Done Matters for Product Teams
Traditional market research focuses on customer attributes: demographics, psychographics, behaviors. JTBD focuses on circumstances and motivations.
Traditional approach:
"Our target customer is a 35-year-old marketing manager at a mid-sized B2B company."
JTBD approach:
"When a marketing manager needs to prove campaign ROI to executives who don't understand marketing metrics, they want simplified reporting dashboards, so they can secure budget for next quarter."
The JTBD approach immediately suggests product direction. The demographic approach doesn't.
Benefits of JTBD thinking:
- Better opportunity identification - Focus on underserved jobs, not crowded demographics
- Clearer competitive landscape - Compete against anything hired for the same job, not just direct alternatives
- More effective positioning - Communicate how you help customers make progress
- Informed feature prioritization - Build what helps customers get their job done better
- Reduced feature bloat - Say no to features unrelated to the core job
Conducting Jobs-to-be-Done Research
JTBD research looks different from traditional customer interviews. You're not asking "What features do you want?" You're investigating the circumstances that led to their hiring or switching decisions.
The Switch Interview
The most powerful JTBD research method is the "switch interview"—interviewing customers about their decision to start using your product (or a competitor's).
The timeline:
- First thought - When did they first think about finding a solution?
- Passive looking - What triggered active searching?
- Active looking - What did they evaluate? What were they looking for?
- Decision - What made them choose your product?
- First use - What happened when they first used it?
- Ongoing use - How has their usage evolved?
Key questions:
About the struggle:
- "Tell me about the circumstances when you realized you needed something like this."
- "What were you trying to accomplish?"
- "What was frustrating about your old approach?"
- "Why did you start looking right then, instead of earlier or later?"
About alternatives:
- "What else did you consider?"
- "What did you try before finding this product?"
- "Why didn't those work?"
About anxieties:
- "What almost stopped you from buying?"
- "What were you worried might go wrong?"
- "What would have happened if you'd done nothing?"
About the decision:
- "What made you finally choose this product over others?"
- "What was the moment you knew it was the right choice?"
The Forces of Progress Framework
Bob Moesta's "Forces Diagram" illustrates the tensions customers experience when considering a switch:
Forces pushing toward change:
- Push of the situation - Pain with the current state
- Pull of the new solution - Attraction to your product
Forces resisting change:
- Anxiety of the new solution - Fear the new thing won't work
- Habit of the present - Comfort with current situation, even if imperfect
Change happens when (Push + Pull) > (Anxiety + Habit).
Understanding these forces helps you:
- Amplify push - Clearly articulate the cost of inaction
- Increase pull - Better communicate your solution's benefits
- Reduce anxiety - Offer trials, guarantees, testimonials, onboarding help
- Overcome habit - Make switching easy, provide migration tools
Non-Consumption Interviews
Sometimes the most valuable insights come from people who have the job but haven't hired any solution yet—"non-consumers."
Questions for non-consumers:
- "How do you currently handle [job]?"
- "What's keeping you from using a [product category] solution?"
- "What would have to be true for you to start using one?"
- "What worries you about products like this?"
Non-consumers reveal adoption barriers and unmet needs that existing customers have already overcome.
From Jobs to Product Strategy
Job Mapping
Break the high-level job into stages. This reveals opportunities at each step.
Example: The job of "Get dinner on the table for my family"
Stages:
- Decide what to make
- Check what ingredients I have
- Make a shopping list
- Buy ingredients
- Prepare the meal
- Serve and eat
- Clean up
Questions for each stage:
- What makes this step difficult?
- Where do customers struggle or get stuck?
- What would make this faster, easier, or more reliable?
Different products serve different stages. Blue Apron serves stages 1-4. DoorDash serves stages 1-6. Dishwashers serve stage 7.
Opportunities exist at underserved stages or in making transitions between stages smoother.
Identifying Job Outcomes
For each job, identify the outcome metrics customers use to measure success.
The job: "Get to work on time"
Desired outcomes:
- Minimize time spent in traffic
- Increase predictability of arrival time
- Minimize stress during commute
- Minimize cost of transportation
- Maximize comfort while traveling
Different customers weight these outcomes differently. Some optimize for speed, others for cost, others for comfort. This creates market segmentation based on priorities, not demographics.
Competition Through a JTBD Lens
Who's your real competition? Everyone hired for the same job.
Traditional view:
Netflix competes with Hulu, Disney+, and HBO Max.
JTBD view:
Netflix competes with anything people hire to "unwind and be entertained after work"—YouTube, TikTok, video games, books, going to bars, or just going to bed early.
This broader view reveals non-obvious competitors and opportunities. When you understand the true job, you can position against all alternatives, not just direct competitors.
Applying JTBD to Product Decisions
Feature Prioritization
Evaluate feature ideas against the core job:
Questions:
- Does this help customers get the job done better/faster/cheaper?
- Does this address an underserved outcome?
- Does this reduce anxiety about adopting our solution?
Features unrelated to the core job are distractions. This framework helps you say no with confidence.
Onboarding Design
Map your onboarding to job stages:
- Reduce anxiety - "Other customers like you succeeded"
- Overcome habits - "Here's how to migrate from your old tool"
- Show quick progress - "You've completed your first [core job]"
- Build new habits - "Do this weekly to get the best results"
Effective onboarding optimization addresses all forces of progress.
Marketing and Positioning
Position your product around the job, not features:
Feature-focused (weak):
"Project management software with Gantt charts, kanban boards, and time tracking."
Job-focused (strong):
"Keep projects on track when your team is scattered across time zones and tools."
The job-focused message immediately resonates with people experiencing that struggle.
Integrating JTBD with Other Frameworks
JTBD complements other product discovery methods:
- Opportunity Solution Trees - Jobs become high-level opportunities; job outcomes become sub-opportunities
- Continuous Discovery - Run JTBD switch interviews as part of your weekly customer conversations
- Personas - Create personas based on job priorities, not demographics
- User Stories - Reframe as "When [situation], I want to [accomplish job], so I can [achieve outcome]"
Common JTBD Mistakes
Confusing jobs with solutions
"I need a CRM" is a solution. "I need to track my sales conversations so I don't lose deals to poor follow-up" is a job.
Defining jobs too narrowly
"Send invoices" is a task. "Get paid on time for my work" is a job. Go higher-level to find innovation opportunities.
Stopping at functional jobs
Jobs have emotional and social dimensions too. "Look professional to clients" is as important as "complete the task efficiently."
Ignoring context
The same person has different jobs in different contexts. A smartphone serves different jobs during a commute, at work, and on vacation.
Forcing all feedback into JTBD format
Not every insight needs to be a job statement. JTBD is a lens, not a requirement.
Advanced JTBD Techniques
Job Hierarchies
Jobs nest within larger jobs:
High-level job: Feel confident in my professional appearance
→ Mid-level job: Maintain good hair/grooming
→ Low-level job: Get a haircut that looks professional
Different products serve different levels. Understanding the hierarchy reveals where you fit and where you might expand.
Job Sequencing
Jobs often form sequences:
- Learn about [topic]
- Evaluate [solutions]
- Get approval to buy
- Implement
- Train team
- Measure results
B2B products often need to support the entire sequence, not just one job.
Job Evolution
As customers' situations change, their jobs evolve:
New user job: "Get started quickly without getting overwhelmed"
Power user job: "Optimize my workflow to handle 10x the volume"
Team lead job: "Ensure my team uses the tool consistently and effectively"
Your product may need to serve all three jobs across the customer lifecycle.
Uncover the jobs your customers are hiring you for. Pelin.ai analyzes conversations across support, sales, and feedback channels to reveal customer motivations and opportunity patterns. Request a free trial and discover what jobs you're really being hired to do.