Method
A short sprint to run and synthesize JTBD-style interviews focused on pushes, pulls, anxieties, and habits.
Choose this if
This method works when understanding purchase and behavior change drivers.
Pack = one session you can run now. Workspace = a saved thread for method choice, planning, and shareable outputs.
What Workspace helps you carry forward
Artifact preview
JTBD force map
Understand needs · High
Decide fit before you spend session time.
Room fit check
Best when the team needs to understand what progress people are trying to make and what actually causes them to switch, hesitate, or stay put. This room has enough of the right conditions for the method to hold without extra ceremony.
Primary risk: Interviewers lead participants toward neat job statements that were never really lived.
The core facilitation flow, with enough structure to run the method confidently in the room.
Standard setup for Mixed in remote delivery.
Total planned time: 124 min
What happens
Select recent switchers, non-adopters, or churned users.
Facilitator does
Select people who have recently made a real switch decision relevant to the question — someone who adopted your product recently or recently churned. Hypothetical adopters or long-established users have rationalised their behavior too heavily. The most useful JTBD interviews come from people still close to the actual decision moment.
Participants do
Name specific individuals or recruitment criteria for people who made a real switch decision recently — adopted, churned, or moved from a competitor. Hypothetical adopters or people who have used the product for years have rationalised their behavior too heavily to provide useful force data.
Output / signal of success
A cohort definition is agreed: the specific switch context (adopted, churned, switched from competitor), the recency requirement (decision made within the last 3–6 months), and a minimum viable cohort size (3–5 people for directional signal, 8–12 for pattern confidence).
Watch for
Cohort consists of long-term users who can no longer recall the original switch context.
Recovery tip
If the team can only access long-term users, ask: "Can we identify anyone who joined in the last 6 months?" or "Is there anyone who tried the product and didn't continue?" Recent switchers are the minimum viable cohort. If none are accessible, the method cannot produce its core output — consider Interview Discussion Guide Workshop for a broader research approach instead.
What happens
Probe timeline, triggers, alternatives, and outcomes.
Facilitator does
Start with the specific past event — 'Tell me about the moment you decided to change' — and follow the narrative backward to the push-and-pull forces. Stay conversational and follow every 'why' until you reach a force, not a feature preference. Never ask what they would do in the future.
Participants do
Follow the narrative backward in time — not forward into hypotheticals. When the participant mentions a trigger or a moment of dissatisfaction, ask: "Can you walk me through what happened?" Stay in the past tense throughout. "What would you do if..." questions produce rationalized responses, not force data.
Output / signal of success
Each interview has produced a timeline of the switch decision: the push (what made the status quo unacceptable), the pull (what made the new option attractive), anxieties (what created hesitation), and inertia (what nearly stopped the switch). The timeline is specific to events, not to general attitudes.
Watch for
Interviewer pivots to hypothetical future questions when the past narrative becomes difficult.
Recovery tip
When an interviewer drifts into hypothetical questions ("what would make you more likely to..."), stop the playback. Read the question aloud and ask: "Is this asking about something that happened or something that might happen?" If the latter, reframe it: "Tell me about the last time you felt [X]. What did you do?"
What happens
Map push, pull, anxiety, and habit themes.
Facilitator does
Map each interview into the four-force framework — pushes, pulls, anxieties, and inertia — using direct participant language rather than team interpretation. Hold a separate synthesis session per interview before combining across the cohort. Forces appearing consistently across interviews are the signal; unique forces are context.
Participants do
Map forces using direct participant language — quotes, not paraphrases. "The old tool made me feel stupid every time I used it" is a push. "Customers generally experience friction with legacy tools" is a team interpretation. The force map should contain the participant's words, not the team's summary.
Output / signal of success
The four-force map (pushes, pulls, anxieties, inertia) is populated with direct quotes from 3+ participants. Forces appearing in multiple interviews are marked as patterns. Forces appearing in only one interview are marked as individual signals, not patterns.
Watch for
Forces are paraphrased into team language rather than anchored to participant quotes.
Recovery tip
For any force written in the team's language rather than the participant's, ask: "Can you quote the participant directly?" If nobody can, the force needs to be reclassified as a team inference and marked accordingly.
What happens
Prioritize opportunity areas and messaging hypotheses.
Facilitator does
Identify which forces the team can reduce, amplify, or introduce through product, service, or messaging changes. Ask: "Which current plan elements address the highest-frequency forces?" For forces appearing in multiple interviews with no current response in the plan, name those explicitly as discovery or design priorities.
Participants do
Connect each force to a specific product, messaging, or service decision — not to a feature. "The anxiety around data export should inform the onboarding messaging" is a decision. "We should build better export tooling" is a solution brief that skips the strategic question.
Output / signal of success
Each major force (appearing in 3+ interviews) is connected to a current plan element or flagged as a planning gap. The session closes with a prioritised list of forces the plan does not yet address.
Watch for
Force translation jumps directly to features rather than to the underlying product strategy.
Recovery tip
For any force that jumps directly to a feature solution, ask: "What specifically is the user unable to do, believe, or feel confidently because of this force?" Write the gap, not the solution. The gap is the brief for the next design or messaging decision.
Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.
Access to 3–8 people who have made a real switch decision relevant to the question — recent adopters, churned users, or competitors' customers who switched to or away from the product — within the last 6 months. Without this cohort, the sprint produces opinion data from long-term users, not force data from people close to a real decision moment.
Recruit criteria
Optional
Interview guide
Optional
Recording consent process
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.
Synthesis board
Optional
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.
Synthesis board
Required
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.
JTBD interview guide
Keep the output usable, then use the recovery guidance when the room starts drifting.
What this does not produce
JTBD interview sprints produce force patterns from a small cohort of people who made a real switch decision recently. They do not represent the full customer base, and patterns from 5–8 interviews should be treated as directional signal, not statistical evidence. High-frequency forces identify what to investigate further, not what to build.
Failure mode
Why it happens
Teams use the JTBD framework but apply survey-style questions: "How important is price to you?" "What features do you value most?" These questions produce stated preferences, not behavioral forces. The pushes and pulls that actually drove the switch decision live in the narrative of a specific event — they can't be accessed through general preference questions.
Recover now
If this happens, stop the current interview. Redirect to the specific event: "Tell me about the moment you decided to make the change. Where were you? What had just happened?" The narrative reconstruction is the method — without it, the interview produces opinion data, not force data.
Prevent next time
Next time, before the sprint begins, model the opening question for all interviewers: "Tell me about the moment you decided to [switch/adopt/leave]. Take me back to that specific day." Practice the opening until every interviewer can deliver it naturally.
Failure mode
Why it happens
During synthesis, teams translate participant quotes into the language of their internal frameworks and product categories. "I was terrified I'd lose all my data in the migration" becomes "migration anxiety" — which sounds like a finding but has lost the specificity and emotional weight of the original. The force map becomes a vocabulary exercise rather than an evidence map.
Recover now
If this happens, go back to the original interview notes. For each force on the map, find the direct quote that anchors it. Replace the paraphrase with the quote on the force map. If no quote can be found, the force is a team inference, not a finding.
Prevent next time
Next time, during synthesis, mandate that each force must be anchored to a direct quote before it goes on the map. "Migration anxiety" is a category label. "I spent two weeks running parallel systems because I was scared of losing client history" is the force.
Failure mode
Why it happens
The session produces a rich force map, and participants — most of whom are product people — immediately connect forces to feature ideas. "Anxiety about support quality" becomes "we need a better help centre." The strategic question — why does support quality anxiety exist and what would remove it — is skipped in favor of the familiar solution frame.
Recover now
If this happens, for each feature idea that surfaces during translation, ask: "What is the specific user capability or belief that this feature is supposed to create? Is there a less expensive way to address the same force?" The feature may be right — but it should be one answer to a clearly articulated gap, not the default response to a named force.
Prevent next time
Next time, run the translation step in two explicit phases: first, name the gap or belief each force implies; second, identify the options for addressing that gap. Keep the phases separate so solutions don't arrive before the strategic framing is complete.
Change the shape of the session only after the fit and runbook are clear.
Standard variant for Mixed in remote delivery. Waypoint is adapting timing, facilitation emphasis, prep, and recovery guidance here, but the room still needs final tailoring to the exact stakes and participants.
Use this after you have checked the fit and know you want to carry the method forward.
The pack is the fastest way to run this now. Use the links below when you need prep, sharing, or a saved reference point.
Guides
The book's consistent push toward concrete behaviour, decision context, and evidence over opinion directly explains why JTBD-style interviewing produces more defensible signal than general discovery conversations.
Open this when you want stronger rationale before choosing the method or taking it into the workspace.
A practical argument for doing just enough structured user research to make decisions defensible — without turning discovery into a slow, academic exercise.
Sources and references used in this method page.
Ulwick outcome-driven innovation resources.
Foundational interview and qualitative research guidance.
Reviewed 2026-02-27 by Discovery Waypoint Editorial Team