An example of a jobs-to-be-done analysis for a B2B product: a revenue operations tool discovers through customer interviews that buyers hire it primarily to eliminate the job of manually reconciling CRM data across multiple sales tools — not for reporting, which was what the product team assumed. This discovery reorients the roadmap from dashboard features to data integration depth.
Jobs-to-be-done (JTBD) analysis often surprises the teams that run it. You think customers buy your product for one reason; they tell you it's another. This gap — between the job the product team assumed and the job customers actually hired the product for — is where the most valuable roadmap insights live.
This guide walks through a complete JTBD analysis for a B2B product, from interview methodology to job mapping to roadmap translation.
What Jobs-to-Be-Done Means for B2B Products
In consumer products, JTBD is often framed around emotional and social jobs: people hire a protein shake to feel disciplined, not just to consume protein. In B2B, the emotional dimension is still real — people hire a project management tool partly to feel in control and reduce anxiety — but the functional job is more dominant and more actionable.
The JTBD framework for B2B focuses on:
- Functional jobs: What task is the buyer trying to get done?
- Emotional jobs: How does the buyer want to feel while doing it?
- Social jobs: How does the buyer want to be perceived by their team or leadership?
- Switch jobs: What was the buyer using before, and why did they switch?
The B2B JTBD Interview Methodology
H3: Who to Interview
For a B2B JTBD analysis, interview three distinct groups:
- Recent buyers (purchased in the last 90 days): still remember the buying trigger
- Power users (high engagement, long tenure): know what the product actually does well
- Churned customers (left in the last 6 months): know what the product failed to do
Target 5–7 interviews per group, for 15–21 total.
H3: The Switch Interview Framework
The most revealing JTBD interviews are "switch interviews" — conversations focused on the moment the customer decided to buy. According to Lenny Rachitsky's writing on customer discovery, the switch moment is "the most information-dense 10 minutes of a customer's relationship with your product. They had a trigger, they searched for alternatives, they made a choice. Understanding all three is what JTBD analysis is for."
Switch interview script structure:
- "Take me back to the moment you decided to look for a solution. What was happening?"
- "What had you tried before that wasn't working?"
- "Who else was involved in the decision? What were they worried about?"
- "When you were evaluating options, what was the one thing that made you choose us over the alternatives?"
- "Six months in, what are you actually using the product for? Is it what you expected?"
The Switch Interview Pattern in Practice
Interview excerpt (anonymized, revenue operations tool):
"We had a new CRO who came in and immediately asked for pipeline accuracy data. We couldn't give it to him with any confidence because our Salesforce data was a disaster — half the reps weren't updating it consistently. We looked at a few tools, but what sold us on [product] was that it didn't require rep behavior change. It captured data automatically."
JTBD extraction from this interview:
- Functional job: Get accurate pipeline data without changing rep workflow
- Emotional job: Feel confident presenting data to executive leadership
- Social job: Appear data-driven and credible to the new CRO
- Switch trigger: New leadership with higher data expectations
Building the Job Map
After 15–21 interviews, synthesize findings into a job map — a structured summary of the jobs customers hire the product to do, ranked by frequency and business criticality.
H3: Job Map Template
| Job | Frequency (% of interviews) | Business Criticality | Current Satisfaction | |-----|---------------------------|---------------------|---------------------| | Eliminate manual CRM reconciliation | 82% | High | Medium | | Provide executive pipeline reporting | 71% | High | Low | | Identify deal risk early | 65% | High | Low | | Onboard new reps faster | 41% | Medium | Medium | | Reduce time spent on forecast calls | 38% | Medium | High |
The highest-priority jobs are those with high frequency AND high business criticality AND low current satisfaction. These represent the biggest gaps between what customers need and what the product currently delivers.
H3: The Roadmap Translation
According to Shreyas Doshi on Lenny's Podcast, the most common mistake in translating JTBD findings to roadmaps is building features directly from job statements without asking "what specifically makes this job hard?" The job is the destination; the feature is one possible path. "Customers tell you what they're trying to accomplish. Your job as PM is to figure out the smallest change to the product that makes that job dramatically easier — not to build everything the job seems to imply."
For each high-priority job:
- "What makes this job hard today?" (barriers)
- "What would completing this job dramatically better look like?" (outcome)
- "What's the smallest product change that would remove the biggest barrier?" (feature hypothesis)
Worked Example: Full JTBD Analysis
Context
Product: B2B project management tool for software engineering teams Research: 18 switch interviews with buyers who purchased in last 90 days
Job Map Findings
| Job | Frequency | Criticality | Satisfaction | |-----|-----------|-------------|-------------| | Know which engineers are blocked without asking | 78% | High | Low | | Predict delivery risk 2+ weeks in advance | 72% | High | Low | | Reduce standup prep time for engineering managers | 61% | Medium | High | | Show progress to non-technical stakeholders | 56% | High | Low | | Identify which PRs are bottlenecking deployment | 44% | Medium | Medium |
Roadmap Implication
The top two jobs — knowing who is blocked and predicting delivery risk — both have high criticality and low satisfaction. The product team assumed the primary job was standup prep (which has high satisfaction, medium criticality). The JTBD analysis reveals the winning jobs are predictive risk visibility, not retrospective status.
According to Gibson Biddle on Lenny's Podcast, the best product decisions he witnessed at Netflix consistently came from teams who had separated "what we built" from "what customers hired it for." "The reporting features got built because engineers wanted to build them. The actual job customers hired the product for was reducing the anxiety of not knowing whether something was on track. Those are different products."
FAQ
Q: What is an example of a jobs-to-be-done analysis for a B2B product? A: A revenue operations tool conducts switch interviews and discovers customers hired it to eliminate manual CRM reconciliation without changing rep behavior — not for reporting as the team assumed. This reorients the roadmap from dashboards to data integration depth.
Q: What is the JTBD switch interview methodology? A: Interviews focused on the moment a customer decided to buy, covering the trigger event, what they tried before, who else was involved in the decision, what made them choose this product, and what they are actually using it for now.
Q: How do you translate JTBD findings into a product roadmap? A: Build a job map ranking jobs by frequency and business criticality. Prioritize jobs with high frequency, high criticality, and low current satisfaction. For each, identify the specific barrier making the job hard and the smallest product change that removes it.
Q: Who should you interview for a B2B JTBD analysis? A: Three groups — recent buyers who remember the switch trigger, power users who know what the product actually does well, and churned customers who know what it failed to do. Five to seven interviews per group for 15 to 21 total.
Q: What is the difference between JTBD and user personas? A: Personas describe who the customer is. JTBD describes what they are trying to accomplish and why they hired your product to do it. Personas are static; jobs are contextual and predict behavior more accurately than demographic attributes.
HowTo: Run a Jobs-to-Be-Done Analysis for a B2B Product
- Identify three interview groups: recent buyers who remember the switch trigger, power users with high engagement, and churned customers who can articulate why the product failed their job
- Conduct 5 to 7 switch interviews per group using the switch interview framework covering the trigger event, prior alternatives, decision factors, and actual current usage
- Extract from each interview the functional job, emotional job, social job, and switch trigger using direct quotes where possible
- Build a job map ranking all identified jobs by frequency across interviews, business criticality, and current product satisfaction
- Identify the highest-priority jobs as those with high frequency and high criticality but low current satisfaction — these represent the biggest product gaps
- For each high-priority job identify the specific barrier making it hard today and hypothesize the smallest product change that would remove that barrier