JTBD Interview: Map the Job, Ignore the Persona
A JTBD interview reconstructs when a user fires one solution and hires another for progress. Use it to discover causal forces, not preferences. The footgun is profiling demographics instead of the struggle that triggered change.
Why it exists
Traditional user research often sorts people into personas or asks them to predict future behavior, which produces unreliable wishlists. JTBD theory assumes that people do not buy products; they hire them to make progress in specific circumstances. The interview exists to uncover that causal story so teams build for the job instead of the demographic.
The mental model
Think of a JTBD interview as a crime-scene reconstruction rather than a preference survey. You are not asking what someone likes; you are asking what changed in their life that caused them to stop using one solution and start using another. The job is the progress they were trying to make, not the tool they used.
How it works
The interviewer maps a switching timeline. Start with the purchase or adoption moment, then work backward to the first thought that something was wrong with the old way. Probe for the struggling moment, the criteria they used to evaluate alternatives, and the anxieties that almost blocked them. Keep questions concrete and focused on the story, not hypotheticals. If the participant starts predicting what they might do in the future, redirect to what they actually did.
When to use it
Use this method when you are exploring a new market, diagnosing why a product is not gaining traction, or understanding the true competitor set, which often includes DIY spreadsheets and manual workarounds rather than direct rivals. It is especially powerful for innovation work where existing category boundaries are misleading.
When not to use it
Do not use a JTBD interview when you need usability feedback on an existing interface, quick validation of a color scheme, or quantitative proof of market size. It is also a poor fit if your team is not ready to act on qualitative narratives, because the output is a set of forces and timelines, not a prioritized feature list.
One canonical example
A team building project management software might interview a user who recently switched from a spreadsheet to their tool. Instead of asking about the user's role or desired features, they reconstruct the day a deadline was missed because the spreadsheet version was overwritten. That struggling moment reveals the job was not organizing tasks; it was maintaining a single source of truth under time pressure. The team realizes their real competition is not other PM tools but the inertia of shared documents.
Interview question
In a JTBD interview, a participant begins speculating about how they might use the solution six months from now. What should the interviewer do?
- a.Record the ideas as a prioritized feature list
- b.Redirect to the concrete story of what they actually did in the pastCorrect
- c.Ask about their role and team size to add demographic context
- d.Explore the scenario to capture emerging requirements
Why? this is the answer
JTBD interviews reconstruct actual switching timelines to uncover causal forces, so the interviewer must redirect speculation toward concrete past actions. Exploring future scenarios produces unreliable wishlists, while demographic questions commit the exact persona-profiling mistake the method is designed to avoid.
Just read this? Test yourself on what you have been reading.
- #ux research
- #jtbd
- #user interviews
- #product strategy
- #qualitative research
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux research — each one lists the topics its interview covers.
See open roles