Jobs-to-Be-Done Interviews: The Timeline Interview and Job Statements
How to run a JTBD timeline interview step by step and turn the transcripts into job statements, with sample questions and the mistakes to avoid.
A Jobs-to-Be-Done (JTBD) interview reconstructs one real decision, from the first moment someone thought "this isn't working any more" to the day they started using something new. You then turn the patterns across interviews into job statements: "When [situation], I want to [motivation], so I can [outcome]." This page covers exactly that: how to run the timeline interview and how to get from transcripts to job statements.
For the framework itself (its history, the two schools and well-known examples), read the Jobs to Be Done framework guide. For a full switch interview question bank and a ready template, see switch interviews.
If you're a founder with a handful of customers and no researcher, start this week: pick 8 to 12 people who signed up or left recently, run the timeline below with each one, and write job statements from what repeats. Koji's Jobs to Be Done Interviews template gives you the questions to start from.

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
| Dimension | Traditional User Interview | JTBD Interview |
|---|---|---|
| Focus | Current experience with a product or process | The decision to adopt or switch |
| Timeframe | Present and recent past | The full decision timeline (first thought to adoption) |
| Key question | "What's your experience with X?" | "Walk me through how you came to use X." |
| Output | Pain points, needs, workflows | Causal forces driving and resisting change |
| Best for | Improving existing experiences | Product strategy, positioning, new product development |
Photo by Maria Fernanda Pissioli on Unsplash
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:
-
Push of the current situation — What's going wrong? What frustration is building? This is the dissatisfaction that creates openness to change.
-
Pull of the new solution — What's attracting them toward the alternative? What promise does it hold?
-
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?"
-
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
All three groups are in your CRM: import them into Koji so each person gets a personalised link, the interviewer greets them by name, and the report is already split by the alternative they came from. Churned customers often speak more freely on the generic anonymous link. For switchers in a market you have no list for, such as buyers who moved between two competitors, open Panel recruit and Koji finds them across 130+ countries at a price you approve first.

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:
- The core job statement. "When I [situation], I want to [motivation], so I can [expected outcome]."
- The trigger events that push people out of the status quo.
- The hiring criteria — what people actually evaluate when choosing a solution.
- The anxiety barriers that prevent or delay adoption.
- 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 report groups open answers into themes with the quotes behind each one, so you start coding from clusters of similar triggers and criteria rather than from raw transcripts. Checking each theme against the four forces is still your job.
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.
Related Resources
- Jobs to Be Done framework: the full framework, its two schools and examples
- Switch interviews: the switch interview question bank and template
- Thematic analysis guide: code transcripts for the four forces
- Structured questions guide: add scale or choice questions next to the timeline
- User interview guide: foundational interview skills
- Writing interview questions: craft better questions for any interview type
Further reading on the blog
- The Complete Guide to Jobs-to-Be-Done Interviews (JTBD Framework 2026) — Jobs-to-be-done interviews reveal why customers really switch to — or away from — your product. This complete guide covers the JTBD framewor
- The Product Manager's Guide to Customer Discovery with AI (2026) — Most PMs know they should talk to customers — but scheduling, note-taking, and analysis eat the clock. Here’s how to run faster, deeper cust
Related Articles
Choosing a Methodology
An overview of every research methodology Koji supports and when to use each one.
Customer Discovery Interviews: The Complete Guide
Learn how to conduct customer discovery interviews to validate your product ideas before building. Covers Steve Blank methodology, question frameworks, sample sizes, and common mistakes.
How to Identify and Validate Customer Pain Points Through Research
A complete guide to discovering the real problems customers face — using AI interviews, structured questions, and proven frameworks to surface pain points that drive product decisions.
Empathy Interviews: Questions, Structure, and How to Run Them
An empathy interview goes deeper than a typical user interview — it surfaces the feelings, values, and mental models behind behavior. This guide explains how to structure and run empathy interviews that reveal what customers really experience.
Ideal Customer Profile (ICP): Definition, Template, and How to Build One with AI Interviews (2026)
A complete guide to building an Ideal Customer Profile — definition, B2B and B2C templates, ICP vs persona, real examples, and how to validate your ICP with Koji's AI interviewer in days, not months.
Implied Warranty Research: Testing What Ordinary Purpose and As Is Actually Mean to Buyers
You are liable for goods being fit for their ordinary purpose, and the ordinary purpose is defined by what your customers actually do. Here is how to measure a warranty you never wrote, and the notice rule that quietly kills most claims before you hear them.
Job Stories vs User Stories: Which Format Should Your Team Use?
A practical comparison of job stories and user stories — the two dominant formats for capturing what software needs to do. Includes when each format wins, how to convert one to the other, and how to source job stories directly from customer interviews.
MCP Workflow Guide for Founders & GTM Teams
How founders and go-to-market teams use Koji MCP with Claude to validate markets, qualify leads through research conversations, and build evidence-based positioning — all without hiring a dedicated researcher.
Outcome-Driven Innovation (ODI): The Ulwick Method for Identifying Unmet Customer Needs
A practical guide to Anthony Ulwick's Outcome-Driven Innovation methodology — how to capture desired outcome statements, prioritize unmet needs, and turn JTBD theory into a measurable roadmap.
How to Validate Product-Market Fit Through Qualitative Interviews
Learn how to design and run customer interviews specifically focused on measuring and moving your product-market fit score.
Startup Idea Validation: How to Test Your Idea with Customer Interviews
A research-backed guide to validating startup ideas through customer interviews — before you write a line of code.
Switch Interviews: The JTBD Method for Understanding Why Customers Buy (and Leave)
Switch interviews uncover the four forces of progress that cause customers to switch from one product to another. Learn the Bob Moesta playbook and how to run switch interviews with AI at scale.
The Definitive Guide to User Interviews
Everything you need to plan, conduct, and analyze user interviews that produce actionable research insights.
How to Create Research-Backed User Personas from Customer Interviews
Learn how to build accurate user personas using qualitative interviews rather than assumptions. Includes a step-by-step process for recruiting, interviewing, clustering, and maintaining personas.
Work-as-Imagined vs Work-as-Done: Why Process Interviews Describe a Job Nobody Does (2026)
What work-as-imagined, work-as-prescribed, work-as-disclosed and work-as-done mean for user research, why the gap exists, and interview techniques that get closer to how work really happens.
How to Write Great Interview Questions
Learn to craft open-ended, neutral interview questions that surface genuine user insights instead of confirmation bias.
Interview Sample Size Research: What the Saturation Studies Found
The evidence behind interview sample sizes: what Guest (2006), Namey (2016), Hennink (2017) and Creswell found about saturation, and how far each applies to product research.