Jobs-to-Be-Done Interview Guide

When a customer buys your product, they're not buying the product itself. They're hiring it to make progress in their life. That deceptively simple idea is the foundation of the Jobs-to-Be-Done (JTBD) framework, and it changes how you approach user research.

JTBD interviews are specifically designed to uncover the causal mechanism behind product adoption and switching decisions. This guide covers the theory, interview techniques, and practical steps to run your own JTBD studies.

What Is Jobs-to-Be-Done?

The JTBD framework originated from the work of Clayton Christensen at Harvard Business School, building on Theodore Levitt's famous insight that customers don't want a quarter-inch drill — they want a quarter-inch hole. Tony Ulwick further developed the framework into Outcome-Driven Innovation, providing a structured methodology for identifying underserved customer needs.

The central premise: people don't buy products — they hire them to get a job done. A "job" is the progress someone is trying to make in a particular circumstance. Understanding the job gives you a much more durable foundation for product strategy than demographic profiles or feature wishlists.

According to Christensen, over 95% of new products fail because companies focus on improving products along dimensions customers don't care about, rather than understanding the job the customer is trying to do.

JTBD vs. Traditional User Interviews

Both approaches are valuable, and they complement each other. Traditional interviews (covered in our user interview guide) are better for understanding ongoing experience. JTBD interviews excel at understanding the decision to adopt.

The Four Forces of Progress

JTBD theory identifies four forces that act on every switching decision:

1. Push of the current situation — What's going wrong? What frustration is building? This is the dissatisfaction that creates openness to change.

2. Pull of the new solution — What's attracting them toward the alternative? What promise does it hold?

3. Anxiety of the new solution — What fears or uncertainties hold them back? "What if it doesn't work? What if I lose my data? What if it's too hard to learn?"

4. Habit of the present — What's comfortable about the status quo? "It's not great, but I know how to use it. All my stuff is there."

For someone to switch, the combined strength of Push + Pull must outweigh Anxiety + Habit. Your JTBD interviews should uncover all four forces.

The Timeline Interview Technique

The timeline interview is the signature JTBD method. It reconstructs the entire decision journey — from the first moment something triggered the thought of change, through evaluation and deliberation, to the actual purchase or adoption.

Structure of a Timeline Interview

1. Start at the purchase moment and work backward.

"You mentioned you started using [product] about [timeframe] ago. Can you take me back to that moment — what was happening when you signed up?"

Then keep asking: "And before that?" "What led to that?" "When did you first start thinking about this?"

2. Map the key moments:

• First thought: When did the idea of changing first enter their mind? What triggered it?
• Passive looking: When did they start noticing alternatives without actively searching?
• Active looking: When did they start deliberately evaluating options?
• Decision: What tipped them over the edge to actually commit?
• First use: What was the onboarding experience like? Did it deliver on the promise?

3. For each moment, explore:

• What were you doing? Where were you?
• Who else was involved in the decision?
• What were you feeling?
• What alternatives did you consider?
• What almost stopped you?

Sample Timeline Interview Questions

• "Take me back to when you first started thinking about finding a new way to handle [job]. What was going on?"
• "How long did you know about [product] before you actually tried it?"
• "Was there a specific moment when you went from thinking about it to actually doing something about it?"
• "What other options did you look at? Why did those not work out?"
• "Was there a point where you almost didn't switch? What almost held you back?"
• "When you first started using [product], did it do what you expected?"

The Switch Interview Technique

The switch interview is a more focused variant that zeroes in on customers who recently switched from a competitor or alternative solution. Research from the Rewired Group suggests that interviewing customers within 90 days of their switching decision produces the most reliable recall of the forces at play.

Who to Interview

• Recent new customers who switched from a known competitor
• Recent new customers who switched from a DIY or manual process
• Recent churned customers who switched away from your product

Sample Switch Interview Questions

Exploring the push:

• "What was the thing that finally made you say 'enough' with your old approach?"
• "How long had that been bothering you before you decided to do something about it?"

Exploring the pull:

• "When you first heard about [new solution], what specifically caught your attention?"
• "What did you hope would change by switching?"

Exploring anxiety:

• "What concerns did you have about switching? What was the biggest risk?"
• "Was there anything that almost stopped you from making the change?"

Exploring habit:

• "What was good enough about your old approach that you stuck with it as long as you did?"
• "What's the thing you miss most, if anything, about how you used to do it?"

Analyzing JTBD Interviews

After conducting 8–12 JTBD interviews, you'll analyze the data to identify:

1. The core job statement. "When I [situation], I want to [motivation], so I can [expected outcome]."
2. The trigger events that push people out of the status quo.
3. The hiring criteria — what people actually evaluate when choosing a solution.
4. The anxiety barriers that prevent or delay adoption.
5. Competing solutions — including "do nothing," which is often the biggest competitor.

You can apply thematic analysis to your JTBD interview data, coding for the four forces across all interviews and looking for patterns in triggers, criteria, and barriers.

Koji's AI analysis can help accelerate this process by identifying the four forces across your interview transcripts and clustering similar trigger events and hiring criteria — giving you a structured view of your JTBD data.

Writing Job Statements

A well-formed job statement follows this format:

"When [situation/trigger], I want to [progress/motivation], so I can [desired outcome]."

Examples:

• "When I'm onboarding a new team member, I want to give them context on past decisions, so they can contribute meaningfully within their first week."
• "When my quarterly report is due, I want to pull together data from multiple tools, so I can show stakeholders the impact of our work."

Good job statements are solution-agnostic — they describe the progress people want to make without specifying how.

Common JTBD Interview Mistakes

• Starting with the product instead of the situation. Don't ask "Why did you choose us?" Start with the circumstance that triggered the search.
• Accepting vague answers. "It was better" is not enough. Probe for specifics: "Better in what way? Can you give me an example?"
• Ignoring the emotional dimension. JTBD decisions are driven by both functional and emotional progress. "How did that make you feel?" is a critical probe.
• Only interviewing happy customers. Churned customers and people who almost-but-didn't switch offer equally valuable data about the forces at play.

Further Reading

• User Interview Guide — foundational interview skills
• Writing Interview Questions — craft better questions for any interview type
• Choosing a Methodology — decide whether JTBD is right for your research goal