Jobs-to-Be-Done Interviews for B2B SaaS: Complete Guide

A practical guide to jobs-to-be-done interviews for B2B SaaS: how JTBD differs from ordinary customer interviews, how to run the switch interview, and the B2B

What Jobs-to-Be-Done Interviews Actually Are
JTBD vs Standard Customer Interviews: Key Differences
The Switch Interview: Structure and Question Flow
Running JTBD Interviews in a B2B SaaS Context: A Real Example
Common B2B JTBD Mistakes and How to Avoid Them
Synthesising JTBD Findings into Actionable Outputs
Frequently Asked Questions

What Jobs-to-Be-Done Interviews Actually Are

Most product teams already know what their users do. Jobs-to-be-done interviews are designed to uncover something harder to see: the progress a buyer is trying to make in their life or organisation — and why they decided to act on it now.

The JTBD framework treats the job, not the product feature or persona, as the fundamental unit of analysis. A job is the underlying need a person is trying to satisfy — the transition from a current situation (point A) to a desired one (point B). People do not buy products; they hire them to perform a job. Entirely different kinds of people can hire entirely different products to perform the same job, which is why personas built on demographics often mislead.

Jobs operate at three levels:

Functional jobs — the practical task to be accomplished (e.g. consolidate compliance data across subsidiaries before an audit).
Emotional jobs — how the buyer wants to feel, or stop feeling, as a result (e.g. confident rather than exposed).
Social jobs — how the buyer wants to be perceived by others in the organisation or market (e.g. seen as a credible, forward-thinking operations lead).

JTBD interviews are not usability tests. Usability testing asks whether someone can operate a product; JTBD interviews reconstruct why someone decided to buy one. They are also distinct from standard product discovery interviews. Discovery interviews typically surface feature ideas and pain points; JTBD interviews target the causal chain of a specific purchase decision. The difference matters because what people say they want in a discovery session often bears little resemblance to what actually drove them to act.

Two main schools have shaped JTBD in practice. Clayton Christensen’s approach, developed at Harvard, emphasises understanding the job as a unit of market segmentation — grouping customers by the progress they seek rather than by demographic or firmographic characteristics. Tony Ulwick’s Outcome-Driven Innovation approach operationalises jobs into measurable desired outcomes that guide product development. The schools disagree on some details of application, but they share the practitioner-relevant conviction that the job is the stable unit of need, and the product is one interchangeable solution.

For B2B SaaS teams, the additional dimension is organisational: the job often belongs to a business function or a regulatory obligation, not just to an individual. Our own research practice consistently shows that B2B buyers are motivated by a combination of needing to feel differently and needing to hit a concrete KPI or OKR. Both layers need capturing.

JTBD vs Standard Customer Interviews: Key Differences

The cleanest way to distinguish the two is this: standard customer interviews ask what people want; JTBD interviews reconstruct what people did and why.

Standard discovery interviews tend to be prospective and hypothetical. You ask a user what features would be useful, what frustrates them today, or what would make them switch. Respondents answer based on what feels plausible to them in the moment — not based on what actually drove past behaviour. The answers are subject to social desirability bias, faulty memory, and the natural tendency to request solutions rather than articulate problems.

JTBD interviews are retrospective and narrative. You anchor every question to a real, specific event — the last time the participant bought or switched to a product in your category. Because you are asking about something that happened, you get access to the actual forces that shaped the decision: the trigger, the emotional weight, the organisational dynamics, the fears that almost stopped it.

In B2B SaaS, this distinction is especially important because the buyer is rarely a single person. A buying committee typically includes an end user, a budget holder, a technical evaluator, and sometimes a compliance or procurement function. Each member of that committee has a different job. The operations manager who triggered the search has a different progress narrative than the finance director who approved the spend. Standard customer interviews, which usually recruit whoever is easiest to reach (often the end user), systematically miss the jobs that drove the commercial decision.

JTBD interviews avoid leading with product prompts. You do not ask “what do you think of our onboarding?” or “how does our tool compare to X?” You ask: “Walk me through the moment you first started thinking something needed to change.” The product enters the conversation only after the narrative has established the job.

Knowing when to use JTBD matters as much as knowing how. It is the right tool when you need to sharpen positioning, pricing, or messaging — outputs that require understanding why someone bought, not just what they use. It is also well-suited for understanding churn and competitive displacement. It is the wrong tool when you need to improve task performance within an existing product — for that, usability testing or behavioural analytics will serve you better. For those methods, see our guide on how to conduct user interviews.

The Switch Interview: Structure and Question Flow

The switch interview is the primary method for conducting JTBD research. It was developed by Bob Moesta and Chris Spiek, who worked with Clayton Christensen, and it is built around a model called the Four Forces.

The four forces describe the competing pressures on any buyer at the moment of switching:

Push — the dissatisfaction or pressure in the current situation that makes staying feel untenable.
Pull — the appeal of the new solution and the imagined better situation it promises.
Anxiety — the fears and uncertainties that slow or block the switch (implementation risk, contract terms, internal resistance).
Habits — the inertia of existing tools, processes, and behaviours that make the old situation comfortable despite its problems.

Push and pull accelerate a switch. Anxiety and habit resist it. Understanding all four — and how they interacted for a specific buyer — gives you a far richer basis for messaging and positioning than any feature comparison.

The question arc follows the buyer’s journey chronologically:

First thought: “When did you first get the sense that your current situation wasn’t working?” — This surfaces the push and the inciting event.
Passive looking: “Did you start paying more attention to alternatives around that time, even if you weren’t actively searching?” — This reveals early pull and the gap between trigger and action.
Active looking: “When did you actually start evaluating options? What did that look like?” — This maps the buying committee dynamics and the criteria they used.
Decision moment: “Walk me back to the day you decided to go with [the new solution]. What happened that day or that week?” — This anchors the narrative to a real event rather than a reconstructed rationale.
First use: “What happened the first time you used it? Was there a moment where you felt certain you’d made the right call — or the wrong one?” — This connects the job to early value realisation.

The most important single probing technique is the phrase: “Walk me back to the day you decided.” It short-circuits rationalisation and forces the participant back into the concrete experience of the decision. Follow it with silence. The answer is almost always more specific — and more useful — than what came before.

In B2B SaaS, you need to map the organisational dimension explicitly. During the session, ask: who first raised the need? Who ran the evaluation? Who had final sign-off? Each person may have had a different job, a different push, and a different anxiety. If you only speak to the end user, you will reconstruct only part of the decision.

For session logistics: allow 60–75 minutes per interview. Shorter sessions rarely give you time to excavate the full timeline. Aim for 6–10 participants who are recent buyers or recent switchers — ideally within the last 3–6 months, while the decision is still vivid. Recruiting the right participants is one of the most common failure points; our guide on recruiting B2B interview participants covers the practicalities.

Running JTBD Interviews in a B2B SaaS Context: A Real Example

In a JTBD study for a mid-market B2B SaaS company operating in a compliance-adjacent space, the product team came to us with a clear hypothesis: customers were switching to them because a competitor had degraded their product quality. The team expected the interviews to confirm this and generate material for a competitive displacement campaign.

The first mistake happened before a single interview was conducted: the team’s customer success function had suggested participants, and nearly all of them were power users who had been on the platform for over a year. They were not recent buyers. They could tell us what they valued about the product, but their memory of the original purchase decision was thin and heavily reconstructed. The switch timeline surfaced almost nothing about push or anxiety — only settled satisfaction.

We corrected course by re-recruiting. Working from CRM data, we identified accounts that had signed in the previous four months and contacted them directly with a neutral framing — not “we want your feedback on our product” but “we’re researching how companies in your sector approach decisions around [the category].” This framing, which does not prime the participant to evaluate the product, is important for getting honest narrative rather than managed impressions.

The revised interviews told a different story. The dominant trigger was not dissatisfaction with a competitor’s features. Across the majority of sessions, the switch had been set in motion by an external audit or a near-miss compliance event — something that made a previously tolerable situation suddenly feel unacceptable. The push was acute and organisational, not gradual and individual. The job, it turned out, was not “find better reporting software.” It was “make sure we are never exposed like that again.”

This reframing had consequences far beyond the product roadmap. Messaging was rewritten to lead with risk reduction and audit readiness rather than feature depth. Onboarding was restructured to surface compliance-related capabilities in the first session, because that was what new customers were most anxious to validate. Sales received a new question to ask early in discovery: “Has there been an audit or a compliance review in the last twelve months?” A yes answer had become a strong leading indicator of a motivated buyer. See our product research hub for related methods that complement this kind of study.

Common B2B JTBD Mistakes and How to Avoid Them

Recruiting heavy users instead of recent buyers. This is the most damaging error, because it is invisible in the output. Long-tenure users can tell you what they love; they cannot reliably tell you what caused them to switch. Recruit people who made the decision in the last 3–6 months.

Asking hypothetical questions. “What would make you switch providers?” is a discovery question masquerading as a JTBD question. It asks people to speculate. JTBD asks people to narrate. Replace every hypothetical with a past-tense anchor: “Think back to when you first started looking. What was happening at that point?”

Interviewing only the end user. In B2B SaaS, the end user is often the last person to influence the commercial decision. If procurement required a security review, if IT had to approve an integration, if finance approved the budget on condition of a specific ROI case — those people have jobs too. Speak to at least two roles in the buying committee, particularly in higher-value deals.

Conflating the job with the feature request. A participant who says “I needed better reporting” is not describing a job — they are proposing a solution. Push back with: “Tell me about a moment when that reporting gap caused a problem. What were the consequences?” The job lives in the consequence, not the feature.

Stopping at functional jobs. The anxieties that delay or derail a switch are often emotional or social: fear of looking foolish if the implementation fails, reluctance to tell a team that their familiar tool is being replaced, concern about losing influence over a process that is being automated. If you only code functional needs, you will miss the forces that most reliably predict whether a switch happens at all.

Analysing interviews in isolation. One interview contains a story; the pattern across 8–10 interviews contains an insight. Resist the temptation to circulate a single compelling interview before synthesis is complete. Frequency and consistency across sessions are what validate a finding.

Skipping the bridge to pricing and positioning. JTBD findings that live in a research repository do not improve revenue. Jobs research maps directly to pricing (which job segments are willing to pay more, and why) and to messaging (which push and pull forces resonate with which buyer). This connection to commercial outputs is explored further in our guide to pricing research for B2B SaaS.

Synthesising JTBD Findings into Actionable Outputs

Analysis begins with a forces board: a shared canvas — digital or physical — with four columns for push, pull, anxiety, and habit. Every significant quote from every interview is placed in the relevant column. Once all sessions are complete, patterns become visible: which pushes appear in seven out of ten interviews, which anxieties cluster around specific buyer roles, which habits proved most resistant.

From this canvas, write job statements in the canonical form:

When [situation], I want to [motivation], so I can [outcome].

The situation grounds the job in a real context. The motivation is directional — it describes the progress the buyer wants to make. The outcome is the measurable or experiential change they are seeking. A good job statement is specific enough to be actionable and general enough to encompass multiple personas.

Map the resulting jobs to three outputs, in parallel:

Messaging pillars — which push forces and pulls should lead your positioning, and for which buyer role.
Onboarding flows — which jobs need to be satisfied in the first session to reduce early anxiety and reduce churn.
Sales enablement — which trigger events should prompt outreach, and which discovery questions surface motivated buyers.

Resist the temptation to prioritise jobs based on who said them most forcefully. A single vocal stakeholder who names a job loudly can distort a findings debrief. Prioritise by frequency and intensity across the full interview set.

Finally, present findings as a narrative, not a slide deck of bullet points. Walk your stakeholders through the timeline of a composite buyer: the trigger event, the passive awareness, the moment of commitment, the first-use anxiety. Preserve the emotional texture. A list of jobs flattens the human experience that makes JTBD findings credible and memorable. For guidance on translating research into organisational action, see our post on insight to impact.

Frequently Asked Questions

How many JTBD interviews do I need for B2B SaaS?

Six to ten interviews with recent buyers or switchers is typically sufficient to saturate the main forces. You will often notice the dominant push and pull patterns emerging by the fifth or sixth session. In B2B, prioritise breadth across roles in the buying committee — a champion user, a budget holder, and a technical evaluator — over simply increasing the volume of individual end-user interviews.

Can I run JTBD interviews with churned customers?

Yes, and churned accounts are particularly valuable because the push forces are strong and recent. The participant has already made the switch away from you, so the anxieties and habits that kept them have been overcome and can be examined clearly. Recruiting them requires careful, neutral framing — focus on understanding their category decision, not on soliciting product feedback or implying they made the wrong choice. Pair churn interviews with win interviews to get a complete picture of where your jobs positioning is and is not landing.

What is the difference between a JTBD interview and a win-loss interview?

Win-loss interviews focus on competitive dynamics and the outcome of a specific deal — why the buyer chose you over a named competitor, or vice versa. JTBD interviews reconstruct the entire causal chain of the buyer’s progress narrative, including the period before any specific vendor was considered. Win-loss answers the question: why us versus them? JTBD answers the question: why change at all, and why now? The methods complement each other. JTBD gives you the upstream trigger; win-loss gives you the downstream comparison.

Do I need special software to analyse JTBD interviews?

No dedicated tool is required. Most teams work effectively with a shared spreadsheet or an affinity board — digital tools such as Miro or FigJam work well for clustering quotes under the four forces. Dedicated research repositories can help at scale, particularly when findings need to be accessible across product, marketing, and sales teams over time. But the quality of JTBD analysis depends on the rigour of the coding process and the discipline of cross-session synthesis, not on the sophistication of the software.

About Glasgow Research — Glasgow Research helps B2B SaaS teams turn customer and market research into product decisions. Work with us.