Jobs to Be Done Interviews: How to Uncover What Really Drives Customer Decisions

Why JTBD interviews work when feature questions fail

Most customer interviews stay at the surface. You ask what people want, what they like, or which features matter most, and you get tidy answers that sound useful but rarely explain real behavior.

That is not because customers are being evasive. It is because people are generally bad at predicting future behavior and simplifying past decisions into neat explanations. A founder hears, “We need better reporting.” A PM hears, “Integrations are important.” A researcher hears, “Ease of use matters.” All of that may be true, but none of it explains why someone changed tools last month, delayed a purchase for six weeks, or kept limping along with a spreadsheet for a year.

Jobs to Be Done interviews are different. They focus on a specific decision someone already made: adopting a product, switching from another tool, adding a new tool to an existing stack, or deciding not to move forward. The goal is to reconstruct that decision in detail.

Instead of asking for opinions, you trace:

what changed
what triggered action
what alternatives were considered
who influenced the decision
what nearly stopped the purchase
why the timing finally felt right

That makes JTBD especially useful when you need to understand:

product adoption
switching behavior
stalled evaluations
churn and reverse switching
why a category suddenly becomes relevant
why a segment that says it has the problem still does not buy

If you need a refresher on when interviews are the right tool in the first place, see When to Use Surveys vs Interviews for Product Decisions.

What a JTBD interview is actually trying to uncover

A JTBD interview is not about extracting a single polished job statement and calling it done. In practice, you are trying to explain movement: why a person changed from the status quo to a new solution.

A good interview helps you identify:

the struggling moment that made the current situation feel untenable
the timeline from first friction to final decision
the alternatives the customer considered, including “do nothing”
the tradeoffs they made to justify change
the forces that pushed and pulled them toward adoption
the habits and anxieties that slowed the decision down

A simple way to structure your analysis is with the four forces model:

Force	What it means	What to listen for
Push	What made the current situation painful	frustration, inefficiency, risk, missed goals, visible failures
Pull	What made the new solution attractive	promised outcomes, ease, speed, confidence, fit with future plans
Habit	What kept them in the old way	inertia, workarounds, existing tools, routines, internal dependencies
Anxiety	What made the new solution feel risky	implementation concerns, cost, trust, switching effort, stakeholder resistance

These forces explain why customers do not switch the moment they notice a problem. They switch when push and pull become strong enough to overcome habit and anxiety.

That distinction matters in practice. A team may hate its current workflow for months, but still not buy because migration feels risky, procurement is slow, or the workaround is “good enough” for one more quarter.

Who to recruit for JTBD interviews

The best participants are people who made the decision recently enough to remember it clearly. In most cases, that means interviewing customers who switched or adopted within the last 30 to 90 days. After that, memory gets compressed and people start telling a clean story instead of the real one.

Prioritize these groups:

new customers who recently chose your product
customers who considered you but chose another option
recent churned customers if you want to understand reverse switching
buyers and strong evaluators, not just end users, when purchase decisions are complex
teams that actively tried to solve the problem, even if they ultimately stayed put

A few recruiting notes that save time:

If your sales cycle is short, bias toward the last 30 to 60 days.
If your sales cycle is long, 90 days may still be acceptable, but ask for calendar anchors like quarter-end, budget planning, or a specific project kickoff.
In B2B, recruit for the decision role you need. The admin user, team manager, procurement lead, and executive sponsor may each tell a different part of the story.
If you are studying non-adoption, recruit people who reached a meaningful evaluation stage. “Visited the website once” is usually not enough.

Avoid interviewing long-time loyal customers for switch interviews. They can tell you about usage and retention, but they are usually poor sources for the original decision story.

If recruitment is the hard part, Recruiting Research Participants in 2026: Best Practices, Screeners, and Incentives covers how to screen for the right recency and decision context.

How many interviews you need

For one segment, 8 to 12 strong interviews is usually enough to reveal repeated patterns in struggling moments, comparison criteria, and decision tradeoffs. If you have distinct segments with meaningfully different buying contexts, treat them separately.

For example:

self-serve SMB buyers
enterprise buyers with procurement
users switching from spreadsheets
users switching from direct competitors
founder-led buying versus team-led buying
first-time category buyers versus experienced buyers

Do not mix these together and assume one job story fits all. JTBD patterns are highly sensitive to context.

A practical rule: if the buying process, alternatives, or stakes differ, split the segment.

A practical 30–45 minute JTBD interview structure

The biggest mistake in JTBD interviews is jumping straight to needs, preferences, or feature requests. Start with the timeline instead.

Here is a practical structure:

Time	Interview section	Goal
5 min	Set context	Confirm what they chose, when, what they used before, and who was involved
10 min	Reconstruct the struggling moment	Find the first event that made change feel necessary
10 min	Explore the search and comparison process	Understand alternatives, criteria, workarounds, and objections
10 min	Get to the decision point	Learn why they moved when they did and what nearly blocked the decision
5–10 min	Reflect on outcomes and remaining doubts	Capture expected value, realized value, and unresolved anxieties

If you only have 20 to 25 minutes, do not try to cover everything. Prioritize:

the old situation
the trigger
the search process
the final decision moment

That sequence will usually produce more useful insight than a broad but shallow conversation.

How to open the interview so people tell the real story

A warm opening matters. If the participant thinks you are looking for praise, complaints, or feature ideas, they will often skip straight to conclusions.

A better setup sounds like this:

I’m not evaluating your satisfaction today. I’m trying to understand the story of how you decided to make a change. I may ask very specific questions about timing, what happened first, and what else you considered, because the sequence is what helps us learn.

That framing does three things:

it reduces the pressure to be “helpful” in a generic way
it gives you permission to ask detailed follow-ups
it signals that real events matter more than polished opinions

Example JTBD interview questions by stage

The best JTBD questions are specific, time-bound, and anchored in real events.

1. Start with the switch

You need a concrete decision to investigate.

Ask:

What did you decide to start using, and when?
What were you using before that?
Was this a replacement, an addition, or a brand-new process?
Who was involved in the decision?
How long had the old setup been in place?

This gives you the boundaries of the story.

2. Find the struggling moment

This is the point where the old way stopped feeling acceptable. It is often more revealing than the final purchase itself.

Ask:

When did you first realize the old way was no longer working well enough?
What happened that day or that week?
What was frustrating about the situation?
What were you trying to get done at the time?
Who felt the pain most directly?
Why didn’t you make a change earlier?

Listen for concrete incidents, not abstract dissatisfaction. Good answers sound like:

“We missed a client deadline because reporting broke.”
“The team doubled and our handoff process collapsed.”
“I spent every Monday morning fixing spreadsheet errors.”
“Our CFO asked for a number we could not produce quickly.”
“We had a security review coming up and our workaround suddenly looked risky.”

Those are much more useful than “we wanted something more scalable.”

3. Trace the timeline forward

Once you have the trigger, move through the process step by step.

Ask:

After that happened, what did you do next?
Did you try to patch the problem before looking for something new?
What workaround did you try first?
When did you decide the workaround was not enough?
What other options did you consider?
How did those options compare in your mind?
What nearly kept you with the old solution?

This is where habit shows up. Many customers do not switch because the old tool is good; they stay because a workaround is easier than change.

4. Understand pull and anxiety

Now get specific about what drew them in and what made them hesitate.

Ask:

What made this option stand out from the others?
What did you hope it would help you do better?
What concerns did you have before committing?
What felt risky about switching?
Who needed to be convinced?
What would have made you walk away?
What proof or reassurance helped you move forward?

Pull is often tied to a better future state. Anxiety is often tied to effort, trust, and downside risk.

5. Get to the decision point

A lot of interviews identify the problem but never explain the moment of commitment. Do not skip this.

Ask:

Why did you decide to move forward then, instead of waiting?
Was there a deadline, event, or internal trigger that forced the decision?
What finally made the decision feel justified?
Did anyone push back? What resolved that?
At the moment you said yes, what mattered most?

This is often where timing becomes clear. The reason someone buys is rarely just “better features.” It is often “the old process failed at the worst possible time and we needed confidence fast.”

6. End with outcomes, not satisfaction scores

You are not closing a support ticket. You are checking whether the job they hired the product for is being fulfilled.

Ask:

What has improved since you made the switch?
What is still harder than you expected?
What has not changed as much as you hoped?
If this product disappeared tomorrow, what would be hardest to replace?
Looking back, what mattered most in your decision?

If you want a broader interview design checklist, How to Write a User Interview Guide That Produces Better Insights is a useful companion.

Follow-up prompts that make interviews much better

The difference between an average JTBD interview and a strong one is usually in the follow-up.

Use prompts like:

“Can you walk me through that step by step?”
“What happened right before that?”
“What did you do after that?”
“How did you decide that was not good enough?”
“What made that feel urgent?”
“Who else was involved at that point?”
“Can you give me a specific example?”
“What were you worried would go wrong?”
“What would you have done if this option had not existed?”

These prompts help you get from summary statements to usable evidence.

What good evidence sounds like

JTBD interviews are strongest when the transcript contains observable details, not just opinions.

Compare these two answers:

Weak evidence:
“We needed something more robust.”

Strong evidence:
“We were onboarding three new client accounts a week, and our spreadsheet process broke every time two people edited it at once. I spent Friday afternoons reconciling errors.”

The second answer gives you:

the context
the trigger
the scale of the problem
the cost of the old workflow
a clue about what “robust” actually means

That is what makes findings actionable for PMs, researchers, and founders.

How to identify push, pull, habit, and anxiety in transcripts

After the interviews, do not jump straight to personas or feature lists. First, code the evidence into the four forces.

A simple way to do this is to highlight verbatim statements and sort them by force:

Force	Example customer language
Push	“We were spending two hours every week fixing reporting errors.”
Pull	“This seemed like the fastest way to get the team on one workflow.”
Habit	“We already had a spreadsheet everyone knew how to use.”
Anxiety	“I worried migration would create more work than it saved.”

Then ask:

Which pushes appear repeatedly across interviews?
Which pulls actually closed the deal?
Which habits delayed action the longest?
Which anxieties needed to be resolved before purchase?
Which forces differ by segment or buyer type?
Which claims from your marketing show up nowhere in the decision story?

This gives you a much better foundation for product and messaging decisions than a list of requested features. Features matter, but usually as evidence for a force. A dashboard is not the reason someone buys. Faster reporting, less manual work, and fewer executive surprises are.

A simple analysis workflow you can use with a small team

You do not need a massive repository or a formal JTBD consultancy process to get value from this work.

A practical workflow:

Write a one-paragraph timeline summary for each interview.
Include old situation, trigger, search process, decision point, and outcome.
Pull verbatims into the four forces.
Keep the customer’s words intact as long as possible.
Cluster repeated patterns.
Group similar pushes, pulls, habits, and anxieties across interviews.
Mark differences by segment.
Do not flatten enterprise and self-serve stories into one narrative.
Translate patterns into decisions.
Ask what should change in messaging, onboarding, sales enablement, or product prioritization.

A lightweight spreadsheet or whiteboard is enough for many teams, as long as the evidence stays tied to real quotes and timelines.

How to turn JTBD findings into decisions

A strong JTBD study should produce outputs that a product, research, or go-to-market team can actually use.

1. Hiring criteria

What conditions must be true for customers to choose your product?

These often include:

urgency level
team size or growth stage
workflow complexity
integration requirements
compliance or reporting pressure
the presence of a failed workaround
a triggering event such as hiring, expansion, or executive scrutiny

This helps PMs and founders distinguish between “interested” prospects and customers who are actually in motion.

2. Messaging inputs

Your positioning should speak to the push and pull while reducing the main anxieties.

If customers switch because manual coordination breaks under growth, say that clearly. If they hesitate because migration feels risky, do not just promise power. Show the path to a safe transition.

Useful messaging questions include:

What pain is urgent enough to act on?
What outcome feels worth the switch?
What proof reduces perceived risk?
What language do customers naturally use to describe the old problem?

3. Product priorities

JTBD findings often change what “priority” means.

For example:

If habit is strong, onboarding and migration may matter more than new features.
If anxiety is high, trust signals, implementation support, and clearer setup flows may have more impact than expanding capability.
If push is weak, the issue may be market timing rather than product depth.
If pull is strong but adoption stalls, the bottleneck may be procurement, stakeholder buy-in, or unclear ROI.

4. Sales and research follow-through

JTBD work is especially valuable when it changes how teams continue learning.

You might update:

sales discovery questions
qualification criteria
win-loss interview prompts
onboarding surveys
lifecycle research plans

That is often where the value compounds.

A grounded example

Imagine you are researching why operations teams adopt a workflow tool.

A shallow interview might produce this conclusion:

customers want automation
integrations matter
ease of use is important

A JTBD interview might reveal something more useful:

The team had grown from 4 to 11 people in six months.
Work was being tracked across Slack, spreadsheets, and email.
A client escalation exposed that nobody owned a critical handoff.
The manager first tried a spreadsheet template and a weekly check-in.
That workaround held for about a month, then failed again during a busy period.
They evaluated three tools.
Your product won because setup looked fast enough to roll out before the next client onboarding wave.
The biggest hesitation was whether the team would actually adopt it.
A template, migration support, and a short pilot reduced that anxiety.

That story gives you concrete action:

message to growing teams whose coordination is breaking
emphasize speed to first workflow, not just feature breadth
invest in templates and rollout support
equip sales to ask about recent breakdowns, not generic process pain

That is the difference between insight and a list of themes.

Common JTBD interview mistakes

A few errors will weaken the study quickly:

Interviewing the wrong people. Recent switchers are far more useful than long-time users.
Asking hypothetical questions. Focus on what happened, not what they think they might do.
Leading with your framework. Do not ask, “What pushed you?” Ask for the story and code the forces later.
Skipping the timeline. Without sequence, you lose causality.
Treating all customers as one segment. Different contexts create different jobs and different forces.
Stopping at pain points. Pain matters, but so do timing, alternatives, and risk.
Confusing requested features with buying criteria. A requested feature may be a proxy for speed, confidence, or control.
Ignoring non-buyers. Lost deals and stalled evaluations often reveal anxieties your current customers already overcame.

The core principle to remember

JTBD interviews are not about collecting better opinions. They are about explaining behavior.

The most valuable insight usually comes from reconstructing the messy path between an unsatisfying present and a committed decision. If you can identify the struggling moment, map the timeline, and separate push, pull, habit, and anxiety, you will understand far more than what customers say they want.

You will understand what actually gets them to change.