{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-04-26T00:11:37.352Z"},"content":[{"type":"blog","id":"93339d9e-badc-48de-ab50-d4681a06a9ae","slug":"jobs-to-be-done-interview-guide-2026","title":"The Complete Guide to Jobs-to-Be-Done Interviews (JTBD Framework 2026)","url":"https://www.koji.so/blog/jobs-to-be-done-interview-guide-2026","summary":"Jobs-to-be-done interviews reveal why customers really switch to — or away from — your product. This complete guide covers the JTBD framework, switch interview technique, question templates, and how to run JTBD research at scale with AI.","content":"# The Complete Guide to Jobs-to-Be-Done Interviews (JTBD Framework 2026)\n\nMost customer research asks the wrong question.\n\nIt asks: \"What features do you want?\" or \"How satisfied are you?\" These questions generate noise. They produce polite, optimistic answers that have no predictive value for product decisions.\n\nThe Jobs-to-Be-Done (JTBD) framework asks a different question entirely: **What job is the customer hiring your product to do?**\n\nThis reframe changes everything. And JTBD interviews — specifically the \"switch interview\" technique — are the most reliable method for answering it.\n\nThis guide explains the full JTBD approach, gives you a proven interview structure, and shows how modern teams are running JTBD research 10x faster using AI-moderated interviews.\n\n---\n\n## What Is the Jobs-to-Be-Done Framework?\n\nJTBD was developed by Harvard Business School professor Clayton Christensen and refined by Tony Ulwick (Outcome-Driven Innovation) and Bob Moesta (switch interviews). The core insight: customers do not buy products — they **hire** products to make progress in their lives.\n\nWhen someone buys a project management tool, they are not buying features. They are hiring a solution to the job \"help me look competent in front of my manager\" or \"eliminate the anxiety of missed deadlines.\" Understanding the actual job — functional, emotional, and social — is what drives product-market fit.\n\nThe JTBD framework demonstrates an **86% innovation success rate**, compared to just 17% for traditional feature-driven approaches. That gap exists because JTBD research reveals demand rather than just preferences.\n\n### The Three Layers of Every Job\n\n- **Functional job:** The practical task the customer is trying to accomplish (\"I need to track which tasks are done\")\n- **Emotional job:** How they want to feel while doing it (\"I want to feel in control and calm\")\n- **Social job:** How they want to be perceived (\"I want my team to see me as organized and reliable\")\n\nMost products optimize for functional jobs. The teams that win optimize for all three.\n\n---\n\n## Why JTBD Interviews Are Different\n\nA standard user interview asks about opinions, preferences, and hypothetical future behavior: \"Would you use X feature?\" \"How would you rate this on a scale of 1–10?\"\n\nHypothetical questions produce hypothetical answers — and hypothetical answers do not predict real purchasing behavior.\n\nJTBD interviews focus on **specific past events**: the moment a customer switched from one solution to another. This is called the **switch interview** (or switch event interview), and it is the most reliable method for understanding what actually drives behavior.\n\nThe logic: if you want to understand why someone hired your product, the most accurate data point is the specific moment they made that decision — and the full context surrounding it.\n\n---\n\n## The Switch Interview: Core Technique\n\nBob Moesta, who refined the switch interview at the Rewired Group, teaches that every purchase involves four forces:\n\n1. **Push:** What frustration with the old solution pushed them to consider switching?\n2. **Pull:** What attracted them to the new solution?\n3. **Anxiety:** What hesitation or fear almost stopped them from switching?\n4. **Habit:** What inertia from the old solution almost kept them stuck?\n\nA JTBD interview systematically explores all four forces around a specific switching event. Done well, 10–15 switch interviews reveal the vast majority of actionable patterns in your customer base.\n\n---\n\n## JTBD Interview Structure: The Full Question Framework\n\n### Phase 1: Timeline Anchoring (5–10 minutes)\n\nBegin by grounding the interview in a specific event — not opinions about the present.\n\n- \"Think back to the last time you started using [product/solution]. When was that approximately?\"\n- \"Walk me through what was going on in your work/life around that time.\"\n- \"What was the trigger that made you start thinking there was a problem to solve?\"\n- \"What were you using before?\"\n\nThe goal is to establish a clear timeline: what existed before, what triggered the first thought, what happened next.\n\n### Phase 2: Mapping the Push (10–15 minutes)\n\nExplore the frustrations and limitations of the previous solution:\n\n- \"What was getting frustrating about [previous solution]?\"\n- \"Was there a specific moment when you thought — I need to find something different?\"\n- \"Tell me what happened that day. What were you trying to do?\"\n- \"What workarounds were you using to deal with the limitations?\"\n- \"How long had those frustrations been building?\"\n\nProbing tip: When they describe a frustration, always ask \"And then what happened?\" to trace the causal chain.\n\n### Phase 3: The First Thought (5–10 minutes)\n\nIdentify the moment awareness of the new solution began:\n\n- \"When did you first hear about [product/solution]?\"\n- \"What made you pay attention to it at that moment specifically?\"\n- \"Had you heard of it before but ignored it? What was different this time?\"\n- \"Did someone recommend it to you? What did they say?\"\n\n### Phase 4: The Consideration Journey (10–15 minutes)\n\nUnderstand the evaluation process and anxiety forces:\n\n- \"What else did you look at when you were evaluating your options?\"\n- \"What made you keep [product] in consideration vs. eliminating others?\"\n- \"What was your biggest concern or hesitation about [product]?\"\n- \"What almost stopped you from going with it?\"\n- \"How did you get over that concern?\"\n\n### Phase 5: The Decision Moment (5–10 minutes)\n\nNail down the specific decision event:\n\n- \"Walk me through the moment you decided to go with [product].\"\n- \"Who else was involved in the decision?\"\n- \"Was there a specific thing that tipped you over the line?\"\n- \"How did you feel after you decided?\"\n\n### Phase 6: Early Use and Validation (5–10 minutes)\n\nUnderstand what success looks like after switching:\n\n- \"What happened in the first few days of using it?\"\n- \"Was there a moment when you knew you had made the right choice?\"\n- \"What do you now use it for that you could not do before?\"\n- \"What is still not perfect?\"\n\n---\n\n## JTBD Interview Best Practices\n\n### 1. Interview switchers, not just current users\n\nYour happiest long-term customers have forgotten why they switched. The most valuable JTBD interviews come from:\n- **Recent switchers-in:** Customers who started using your product in the last 30–90 days\n- **Switchers-out:** Former customers who left for a competitor\n- **Non-switchers:** People who evaluated your product and chose not to switch\n\nAll three reveal different forces. Most teams only talk to the first group and miss the most valuable data.\n\n### 2. Focus on past events, never hypotheticals\n\nThe most common mistake in JTBD interviews is asking \"what would you do if...\" or \"would you use a feature that...\". These questions produce confabulated answers — the participant constructs a plausible response based on what sounds reasonable, not on real behavior.\n\nEvery question should be anchored in something that actually happened: \"Tell me about a time when...\" or \"Walk me through the moment you...\"\n\n### 3. Follow the energy\n\nIn a JTBD interview, the most emotionally charged moments are the most data-rich. When a participant's voice changes, when they lean in, when they say \"actually, this is the thing that really got me...\" — that is where you probe deeper.\n\nDo not rush to the next question. Sit with the discomfort of silence. Ask: \"Tell me more about that.\"\n\n### 4. Run 10–15 interviews per segment\n\nJTBD researchers consistently find that 10–15 switch interviews within a defined customer segment reveal the dominant patterns. After 10, you will start hearing the same push/pull forces repeatedly. That repetition is signal.\n\nFor different customer segments — enterprise vs. SMB, different use cases, different geographies — run a separate set of 10–15 interviews per segment.\n\n### 5. Record and analyze for forces, not features\n\nWhen analyzing JTBD interviews, resist the temptation to extract feature requests. Instead, build a **forces map** for each interview:\n\n- What push forces were present?\n- What pull forces attracted them?\n- What anxieties did they express?\n- What habits did they have to overcome?\n\nAggregate across interviews to find which forces appear most frequently. These are your product strategy inputs.\n\n---\n\n## Running JTBD Interviews at Scale with AI\n\nThe traditional limitation of JTBD research is the same as all qualitative research: it does not scale well. Conducting 15 switch interviews manually — recruiting, scheduling, recording, transcribing, analyzing — takes 3–6 weeks and requires a skilled interviewer.\n\n**Koji** solves the scaling problem for JTBD research specifically:\n\n**Structured + open-ended in the same session:** Koji supports all 6 question types — including open_ended questions that prompt AI follow-up probing, and scale/choice questions that benchmark quantitative measures across respondents. This means you can run a JTBD timeline exploration (fully conversational) alongside a satisfaction scale and a single_choice question about the previous solution — all in one study.\n\n**AI probing that goes deeper:** Koji's AI interviewer is trained to follow up on unexpected answers rather than mechanically moving to the next question. When a participant mentions a surprising frustration, the AI probes: \"Can you tell me more about that?\" This replicates the most valuable part of human JTBD interviewing — following the energy — at scale.\n\n**Voice interviews for natural recall:** Spoken interviews consistently produce richer narrative data than written responses, particularly for timeline and emotional recall. Koji's voice interview mode conducts natural spoken conversations, making it ideal for the timeline-heavy structure of JTBD switch interviews.\n\n**Automatic forces analysis:** Instead of manually building a forces map from 15 transcripts, Koji's automatic thematic analysis identifies recurring patterns across all responses — push forces, pull factors, anxieties, and habits — and surfaces them in a shareable report.\n\n**From question to insight in hours, not weeks:** With Koji, you can send a JTBD interview study to recent customers, collect 15–20 switch interviews within 48–72 hours, and have a synthesized report ready for your product team by end of week.\n\n---\n\n## JTBD Question Templates: Ready to Use\n\nHere are template questions you can adapt for a Koji JTBD study:\n\n**Timeline anchor (open_ended):**\n\"Think back to when you first started using [product/solution]. What was going on in your work at that time that made you start looking for something new?\"\n\n**Push exploration (open_ended):**\n\"What was getting most frustrating about what you were using before? Walk me through a specific moment when that frustration hit you.\"\n\n**Pull identification (open_ended):**\n\"What was the main thing that made you decide to try [product]? What were you hoping it would do for you?\"\n\n**Anxiety probe (open_ended):**\n\"What was your biggest concern or hesitation before you committed? What almost stopped you?\"\n\n**Previous solution (single_choice):**\n\"What were you using to solve this problem before [product]?\"\nOptions: [Competitor A, Competitor B, Spreadsheets, Nothing, Built in-house, Other]\n\n**Switch timeline (scale):**\n\"How long had you been thinking about switching before you actually made the decision?\"\nScale: 1 (Same week) to 5 (More than a year)\n\n**Satisfaction after switching (scale):**\n\"How well does [product] do the job you hired it to do?\"\nScale: 1 (Not at all) to 10 (Perfectly)\n\n**Key outcome (yes_no):**\n\"Would you say that switching solved the core problem you were experiencing?\"\n\n---\n\n## Common JTBD Mistakes to Avoid\n\n**Mistake 1: Asking about features instead of jobs**\nAsking \"what features do you use most?\" confuses usage with the underlying job. A customer might use the reporting feature most — but the job they hired the product for is \"give me credibility in executive meetings.\"\n\n**Mistake 2: Interviewing your biggest fans**\nLong-term loyal customers make poor JTBD interview subjects. They have rationalized their decision and forgotten the push forces. Recent switchers-in and switchers-out are where the real insight lives.\n\n**Mistake 3: Stopping at the functional job**\nFunctional jobs (\"I need to track tasks\") are table stakes. The emotional and social jobs are where differentiation lives. Always ask: \"How did you want to feel when this was working?\" and \"How did you want to be seen by your team/manager/clients?\"\n\n**Mistake 4: Running too few interviews**\nFive interviews is not enough. Patterns in JTBD research become clear at 10–15 interviews per segment. Teams that run 5 interviews and call it JTBD research are drawing conclusions from statistical noise.\n\n---\n\n## JTBD Research Output: What You Should Produce\n\nA well-executed JTBD study produces three deliverables:\n\n1. **Forces map:** A summary of push, pull, anxiety, and habit forces across all interviews, with frequency counts and representative quotes\n2. **Job statement:** A one-sentence articulation of the core functional, emotional, and social job your product is hired to do\n3. **Opportunity gaps:** Moments in the switch journey where customers experienced friction that your product (or a new feature) could address\n\nKoji's report generation automatically surfaces the themes and quotes needed to build the forces map — dramatically reducing the synthesis time from days to minutes.\n\n---\n\n## Getting Started with JTBD Research Today\n\nJTBD interviews are the most reliable method for understanding what customers actually want — not what they say they want in a survey, but the real forces that drive real behavior.\n\nThe best place to start: identify 10 customers who joined in the last 60 days and 5 who recently churned. Set up a Koji voice interview study with a JTBD timeline structure. Run it for 48 hours. You will have more actionable product insight than a year of NPS scores.\n\n**[Start your first JTBD study on Koji — free at koji.so](https://koji.so)** — 10 free credits on signup, no research expertise required.\n\nFor more on customer interview methodology, explore the guide to [How to Write User Interview Questions That Get Real Answers](/blog/how-to-write-user-interview-questions) and [How to Analyze Customer Interview Data](/blog/how-to-analyze-customer-interview-data).\n\n---\n\n## Frequently Asked Questions\n\n**What is a Jobs-to-Be-Done interview?**\n\nA JTBD interview — specifically a switch interview — is a one-on-one conversation that maps the exact sequence of events, emotions, and forces that led a customer to hire (or fire) a product. Rather than asking about opinions or hypothetical features, it focuses on a specific past switching event to reveal the real motivations behind behavior.\n\n**How many JTBD interviews do you need?**\n\nFor a defined customer segment, 10–15 switch interviews typically reveal the dominant patterns. After 10 interviews, you will start hearing the same push and pull forces repeated. For different segments — enterprise vs. SMB, different use cases — run a separate set of 10–15 per segment.\n\n**What is the difference between JTBD and user interviews?**\n\nStandard user interviews ask about preferences, opinions, and hypothetical behavior. JTBD interviews (specifically switch interviews) focus exclusively on past switching events — the specific moment a customer decided to change solutions — and explore the four forces: push, pull, anxiety, and habit. This produces more predictive insights about purchasing behavior.\n\n**Can you run JTBD interviews with AI?**\n\nYes. AI-moderated interview platforms like Koji can conduct JTBD-structured switch interviews at scale, with probing follow-up questions on unexpected answers, voice interview support for natural timeline recall, and automatic synthesis of push/pull/anxiety/habit forces across all responses. This makes it feasible to run 15–20 JTBD interviews in 48 hours rather than 3–6 weeks.\n\n**What is the JTBD innovation success rate?**\n\nResearch using the Jobs-to-Be-Done framework shows an 86% innovation success rate, compared to approximately 17% for traditional feature-driven product development approaches. The difference comes from targeting demand (specific jobs customers need done) rather than preferences (features customers say they want).\n\n**Who created the Jobs-to-Be-Done framework?**\n\nJTBD was developed by Harvard Business School professor Clayton Christensen and refined by Tony Ulwick (Outcome-Driven Innovation) and Bob Moesta (switch interview technique at the Rewired Group). The framework has been adopted by companies including Apple, Google, and Intercom as a core product research methodology.","category":"Tutorial","lastModified":"2026-04-25T19:13:48.274746+00:00","metaTitle":"Jobs-to-Be-Done Interview Guide: JTBD Framework & Questions (2026)","metaDescription":"The complete guide to JTBD switch interviews. Learn the framework, question templates, and how to run jobs-to-be-done research at scale with AI — from question to insight in hours.","keywords":["jobs to be done","JTBD","switch interview","customer research","product discovery","JTBD framework","customer interviews","Clayton Christensen","Bob Moesta","user research methodology"],"faqItems":[{"answer":"A JTBD interview — specifically a switch interview — maps the exact sequence of events, emotions, and forces that led a customer to hire or fire a product. Rather than asking about opinions or hypothetical features, it focuses on a specific past switching event to reveal real motivations behind behavior.","question":"What is a Jobs-to-Be-Done interview?"},{"answer":"For a defined customer segment, 10-15 switch interviews typically reveal the dominant patterns. After 10 interviews, you will start hearing the same push and pull forces repeated. For different segments, run a separate set of 10-15 per segment.","question":"How many JTBD interviews do you need?"},{"answer":"Standard user interviews ask about preferences and hypothetical behavior. JTBD switch interviews focus exclusively on the specific moment a customer decided to change solutions, exploring push, pull, anxiety, and habit forces — producing far more predictive insights about purchasing behavior.","question":"What is the difference between JTBD and user interviews?"},{"answer":"Yes. AI-moderated platforms like Koji conduct JTBD-structured switch interviews at scale, with probing follow-up questions, voice interview support for natural timeline recall, and automatic synthesis of push/pull/anxiety/habit forces across all responses — making 15-20 JTBD interviews feasible in 48 hours.","question":"Can you run JTBD interviews with AI?"},{"answer":"Research using the JTBD framework shows an 86% innovation success rate, compared to approximately 17% for traditional feature-driven product development. The difference comes from targeting specific jobs customers need done rather than preferences they say they want.","question":"What is the JTBD innovation success rate?"},{"answer":"JTBD was developed by Clayton Christensen at Harvard Business School and refined by Tony Ulwick (Outcome-Driven Innovation) and Bob Moesta (switch interview technique). It has been adopted by Apple, Google, and Intercom as a core product research methodology.","question":"Who created the Jobs-to-Be-Done framework?"}]}],"pagination":{"total":1,"returned":1,"offset":0}}