Skip to content
JTBD · 9 min read · By Yury

How to Run a JTBD Interview: Complete Script With Questions

A step-by-step guide to running effective Jobs-to-be-Done interviews. Includes the exact questions to ask, what to listen for, and a ready-to-use script.

Most customer interviews fail to uncover real insights. You ask “What features do you want?” and get a wish list that doesn’t tell you anything about why customers actually buy.

JTBD interviews are different. Instead of asking about features, you’re reconstructing the story of how someone went from “I have a problem” to “I chose this solution.” That story reveals the job they hired your product to do.

Here’s exactly how to run one.

The Core Principle: You’re Telling a Story

A JTBD interview isn’t a survey. You’re not collecting data points. You’re asking the customer to walk you through a specific moment in time—the timeline from first thought to purchase decision.

Your goal: Reconstruct the story of their switch in vivid detail.

The story has five chapters:

  1. First thought — When did you first realize you needed something?
  2. The trigger — What event pushed you from passive browsing to active searching?
  3. The search — How did you look for solutions? What did you consider?
  4. The decision — What made you choose this specific solution?
  5. The outcome — What changed after you started using it?

Before the Interview

Who to Interview

Interview recent customers—people who signed up or purchased in the last 30-90 days. Their memory is fresh, and they haven’t yet forgotten the emotions of the switch.

Avoid:

  • Power users who’ve been with you for years (they’ll rationalize)
  • People who are still in a free trial (they haven’t committed)
  • Customers acquired through unusual channels (referrals with social pressure, enterprise deals with long sales cycles)

How to Recruit

Email subject lines that work:

  • “Quick question about why you signed up”
  • “15 minutes to help us improve?”
  • “Can I learn about your experience?”

Offer something small: a $25 gift card, a free month, early access to a feature. But honestly, many customers will talk to you for free—people like sharing their stories.

Set Expectations

When scheduling, tell them:

  • It will take 20-30 minutes
  • You want to hear about their experience before and after they found you
  • There are no right or wrong answers
  • You’re not selling anything

The Interview Script

Opening (2 minutes)

Start casual. Build rapport.

“Thanks for taking the time. I’m not going to try to sell you anything—I’m just trying to understand how people like you find and use [product].

I’d like to hear the story of how you went from first thinking about [solving this problem] to actually signing up for [product]. We’ll go through it like a timeline.

There are no right or wrong answers. I might ask you to slow down or go back to certain moments—just trying to capture the details.”

Chapter 1: First Thought (5 minutes)

Goal: Find the seed of the job. When did they first realize the status quo wasn’t working?

Questions:

“Think back to when you first started thinking about [category/problem area]. Can you remember when that was?”

Wait for them to anchor in a specific time. Don’t accept “I’ve always needed something like this.”

“What was going on in your life/work at that time? What made you start thinking about this?”

“Before you had [product], how were you handling this?”

“What was frustrating about that approach?”

What you’re listening for:

  • Specific circumstances (“We had just hired three new people and…”)
  • Emotional language (“I was so frustrated because…”)
  • The first hint that the old way wasn’t working

Chapter 2: The Trigger (5 minutes)

Goal: Find the passive-to-active switch. What pushed them from “this is annoying” to “I need to fix this now”?

Questions:

“You said you’d been dealing with [problem] for a while. What happened that made you actually start looking for a solution?”

“Was there a specific moment or event? Walk me through that day.”

“Before that moment, what was stopping you from looking for something new?”

What you’re listening for:

  • The specific event that broke the camel’s back
  • The stakes: what would happen if they didn’t solve this?
  • Emotional intensity: frustration, embarrassment, fear

Chapter 3: The Search (5 minutes)

Goal: Understand how they evaluated options and what alternatives they considered.

Questions:

“Once you decided to look for a solution, how did you start?”

“What did you search for? Can you remember any specific terms?”

“What solutions did you consider? Walk me through each one.”

For each alternative:

“What did you like about [alternative]?” “What made you not go with it?”

“Did you consider doing nothing—just sticking with what you had?”

What you’re listening for:

  • The actual competitive set (often surprising)
  • Criteria they used to evaluate
  • Deal-breakers that eliminated options
  • Whether “do nothing” was a real option

Chapter 4: The Decision (5 minutes)

Goal: Understand what tipped them toward your solution specifically.

Questions:

“So you ended up choosing [product]. What made you go with it over the other options?”

“Was there anything that almost stopped you from signing up?”

“Did you have any concerns? What were they?”

“Did anyone else influence this decision? Boss, team, partner?”

“How did you justify the cost/time investment?”

What you’re listening for:

  • The “hiring criteria”—what job did they specifically hire you for?
  • Anxieties and risks they perceived
  • Who else was involved (stakeholders, influencers)
  • How they overcame objections (their own or others’)

Chapter 5: The Outcome (5 minutes)

Goal: Understand the progress they’ve made since using your product.

Questions:

“Now that you’ve been using [product], how is your life/work different?”

“What can you do now that you couldn’t before?”

“Has it solved the problem you originally had?”

“If [product] disappeared tomorrow, what would you do?”

What you’re listening for:

  • The actual job being done (sometimes different from what they expected)
  • Emotional payoff (relief, confidence, pride)
  • How sticky the solution is

Closing (2 minutes)

“This has been really helpful. Is there anything else about your experience you think I should know?”

“Any questions for me?”

Thank them genuinely. Send the gift card promptly.

What to Listen For

Good Signs

Emotional language:

  • “I was so frustrated…”
  • “It was embarrassing when…”
  • “I finally felt like…”
  • “It was a relief to…”

Specific details:

  • “On Tuesday at 3pm…”
  • “My boss said…”
  • “I remember googling…”

Stories, not features:

  • “I needed to…” (not “I wanted a feature that…”)
  • “The situation was…” (not “I prefer products that…”)

Red Flags

Generic statements:

  • “I always need tools like this”
  • “Everyone in my industry uses this”

Feature talk:

  • “I wanted something with good reporting”
  • “The dashboard looked nice”

Hypotheticals:

  • “I would usually…”
  • “Typically I need…”

When you hear red flags, redirect:

“Can you give me a specific example? Walk me through an actual time this happened.”

After the Interview

Debrief Immediately

Within 30 minutes of the interview, write down:

  • The core job (one sentence)
  • The trigger event
  • Key competitors considered
  • The hiring criteria
  • Standout quotes

Synthesize Across Interviews

After 8-12 interviews, patterns emerge:

  • 2-3 main jobs surface repeatedly
  • Common triggers become clear
  • The real competitive set reveals itself
  • Hiring criteria converge

Look for:

  • Clusters: Which jobs keep coming up?
  • Surprises: What competitors or criteria did you not expect?
  • Emotional peaks: Which parts of the story have the most energy?

JTBD Interview Cheat Sheet

Print this for your interviews:

OPENING
- Build rapport, set expectations
- "Tell me the story of how you found [product]"

FIRST THOUGHT
- When did you first think about this?
- What was going on at that time?
- How were you handling it before?

TRIGGER
- What made you start actively looking?
- What was the specific moment?
- What were the stakes?

SEARCH
- How did you search?
- What did you consider?
- Why not [alternative]?

DECISION
- What made you choose us?
- What almost stopped you?
- Who else was involved?

OUTCOME
- How is life different now?
- What can you do now?
- What would you do if this disappeared?

LISTEN FOR
✅ Emotional language
✅ Specific moments
✅ Stories, not features

REDIRECT IF
❌ Generic statements
❌ Feature requests
❌ Hypotheticals
→ "Give me a specific example"

Common Mistakes

1. Asking about features

Don’t ask “What features made you choose us?” Ask “What were you trying to accomplish?”

2. Not going deep enough

When they say “I needed better reporting,” ask “Tell me about a specific time you needed a report and the old way didn’t work.”

3. Leading the witness

Don’t say “So you must have been frustrated with the slow load times, right?” Ask open-ended questions and let them tell you what mattered.

4. Interviewing the wrong people

Recent buyers with fresh memories. Not power users who’ve forgotten why they switched.

5. Stopping too soon

One interview isn’t enough. Patterns emerge after 8-12 interviews. You need enough data points to see what repeats.

From Interviews to Strategy

Raw interviews are valuable, but the real power comes from synthesis. After conducting your interviews:

  1. Extract job statements using our JTBD Statement Builder
  2. Identify the primary job most customers hire you for
  3. Map the competitive set based on what alternatives they considered
  4. Define hiring criteria based on what made them choose you
  5. Build personas around the jobs, not just demographics

Next steps:

Related Posts

Turn JTBD insights into product specs

Rock-n-Roll takes your customer research and turns it into structured documentation: strategy briefs, solution blueprints, and builder-ready implementation plans.

Start your free project