How to Prepare for Jobs To Be Done Interviews
- A Jobs To Be Done interview reconstructs one specific purchase as a timeline of events, not as a set of opinions about your product.
- Only interview people who actually bought. Buyers can describe the full path to a decision; shoppers who never bought cannot.
- Four forces decide every purchase: push and pull move the customer toward change, anxiety and habit hold them back.
- Ask when, where, and who questions instead of why questions, because why invites the customer to invent a tidy explanation after the fact.
- Roughly 10 to 12 interviews per job are enough for patterns to appear, and the debrief straight after each interview is where most of the insight is captured.
A Jobs To Be Done interview reconstructs the story of one real purchase in enough detail that you can see what caused it. Not what the customer likes about the product. What happened in their life that made them say, "today is the day."
Preparing well is most of the work. If you recruit the wrong people, write a rigid questionnaire, or skip the debrief, you get an hour of pleasant conversation and nothing you can act on. This guide covers the four forces behind every purchase, the timeline a buyer actually walks, who to interview, the six-step process, and the questions that get people to tell you the story instead of an opinion.
What is a Jobs To Be Done interview?
The premise of the framework is that people do not buy products, they hire them to make progress. The Clayton Christensen Institute puts it this way: "People don't simply buy or pick products or services; they pull them into their lives to make progress." Jobs To Be Done is the lens that reveals the circumstances driving people toward and away from that decision.
The framework has more than one parent, and it is worth being accurate about that. Tony Ulwick developed Outcome-Driven Innovation in the early 1990s and introduced the underlying idea to Clayton Christensen in 1999. Christensen turned it into a theory of innovation, set out most fully in Competing Against Luck (2016). Bob Moesta, founder and CEO of The Re-Wired Group and a fellow at the Christensen Institute, built the interview method that most practitioners use today, and defines a job as "the progress a person is trying to make in a struggling moment."
For a DTC brand, that makes the interview a causality tool. Analytics tells you what people did on the site. Surveys tell you what people say they prefer. Only the interview tells you which sequence of events produced the order, and that is what you need before you redesign a product page or launch a new line.
The distinction between correlation and causality is the whole point, and it is where most segmentation work goes wrong. As Juliana Jackson put it:
"The single biggest reason most marketing folks mess up customer segmentation: they segment based on correlation. For instance, I'm a female, 30, living in Romania, enjoying hip-hop music and urban fashion. Most people will take those attributes and 'tailor' an experience to sell me an urban fashion backpack. Why is that wrong? There is no causality for me to buy that backpack. Attributes like social demographics, interests, age, etc., can be correlated into associating a customer's interest in a product or a service, but they don't cause that customer to buy."
The four forces of progress
Take a pair of retired parents redecorating their daughter's old room as a guest room. The four forces look like this.
- Push of the situation. The room has been empty since their daughter moved out, and guests keep sleeping on the sofa. The push is the moment the current state becomes a complaint.
- Pull of the new solution. They start seeing bed frames and wardrobes they like, and imagine the finished room. The pull is the appeal of the outcome, not of the product.
- Anxiety of the new solution. Will the bed fit? Is the finish as good as it looks online? What happens if it arrives damaged? Anxiety shows up as a stream of questions about an alternative.
- Habit of the present. As they clear out their daughter's things they get sentimental and start asking whether they need to change anything at all. Habit is the pull of doing nothing.
Most brands spend their budget on pull, because pull is the easy one to advertise. The interview usually shows that the deals are lost on anxiety and habit instead, and those are cheaper to fix: a clearer returns policy, a size guide, a photograph of the product in a real room, a phone number.
Once you know which anxiety blocks the sale, test the fix rather than assuming it works.
Run the test in Omniconvert Explore →The JTBD timeline: how a purchase actually unfolds
The sales pipeline is drawn as a straight line because that is convenient for the seller. The demand side does not work that way. Your job in the interview is to place the customer on this timeline and find out what moved them from each stage to the next.
-
First thoughtThe customer thinks about doing something differently. It often starts with an offhand question or a story from a friend. Nothing is being shopped for yet.
-
Passive lookingThey notice things. Their language is still about the problem, not about products. This stage can last months and is invisible in your analytics.
-
The eventSomething happens that turns "someday" into "we should do something about this." A visit is booked, something breaks, a deadline appears. Finding this event is usually the single most valuable thing the interview produces.
-
Active lookingNow they compare solutions. Language switches from problem to product. Price is usually not the deciding factor yet.
-
DecidingAlternatives get weighed and trade-offs get made. Without time pressure, many people stop here indefinitely. This is where anxiety and habit do their damage.
-
Buying and first useThe order is placed, and the product either delivers the progress or does not. The first week decides whether this customer ever comes back.
Who to interview, and who to leave out
People who considered you and did not buy are a different research project. They can tell you where they stopped, but they cannot tell you what a completed decision looks like, and the story of a decision that never happened has no ending to reconstruct.
RFM segmentation is the practical way to build the list. An RFM analysis scores every customer on recency, frequency, and monetary value, and the customers scoring high on all three, the segment we call Soulmates, are the ones whose jobs you most want to understand. In the Customer Value Optimization model, growth comes from concentrating on the most valuable customers, so the interview list should over-represent them.
Balance that against variety. If all twelve interviews come from the same segment, the same age group, and the same city, the patterns you find will be real but narrow. Nexus by Omniconvert builds the RFM segments from your order data, so you can pick a spread of profiles from within the segments that matter rather than guessing from a spreadsheet.
The six-step JTBD process
-
Frame the questionDecide what you are trying to find out: what causes people to say "today is the day I need this." Write down every question you would like to ask, then find the one or two that would answer most of the others. Resist the researcher's trap of stuffing thirty questions into an hour; a long list produces short answers.
-
Set up the interviewsRecruit customers who made progress, meaning people who bought. Aim for a wide spread of ages, genders, locations, and order sizes, weighted toward your highest-value RFM segments. Interview recent buyers where you can, and offer a real incentive; you are asking for an hour of someone's attention.
-
Conduct the interviewsPlan for 45 to 60 minutes with two people on your side: one leading, one listening. Keep the customer talking about the progress they were trying to make rather than about your product's features. Treat the script as a map, not a questionnaire, and follow the story where it goes.
-
Find the patternsDebrief within the hour, for 30 to 45 minutes, while the story is still fresh. Argue about what you heard, and settle on the customer's own words rather than your paraphrase. Around 10 to 12 interviews are usually enough for patterns to repeat.
-
Detail the clustersGroup interviews that tell similar stories. Each cluster is a pathway by which people make progress, and each one gets described in the same terms: context, struggling moment, pushes and pulls, anxieties and habits, desired outcome, hire and fire criteria, trade-offs, and the baseline quality expected.
-
Prototype opportunitiesTurn each job into something you can ship and measure: a change to product page copy, a bundle, a guarantee that kills a specific anxiety, a new product. Most brands only ever look at the supply side. The clusters give you the demand side, which is where the unclaimed opportunities are.
Bob Moesta's interview technique borrows from investigative interviewing, and several of the moves feel odd until you try them. He teaches them in the CVO Course:
- Keep the script as a framework and let the dialogue run naturally.
- Listen actively for changes in tone; hesitation marks the interesting parts.
- Play confused on purpose to make the customer supply the full context.
- Play the story back in the wrong order, or slightly wrong, so the customer corrects you and adds detail.
Set expectations at the start. Tell the customer you want to understand the language people use around buying this kind of product, that it is closer to a documentary than a survey, and that some questions will sound strange.
Questions to ask in a JTBD interview
These are our own starting questions, not a fixed script. Use whichever ones the story calls for, and skip the rest.
- First thought. When did you first think about solving this? Where were you? What made you think about it that day? Had you thought about it before and let it go?
- Passive looking. What did you do about it back then, if anything? What did you notice that you had not noticed before? Who did you talk to about it?
- The event. What changed that made this urgent? Was there a date you were working toward? What would have happened if you had done nothing?
- Active looking. What else did you look at? What did you type into the search box? What did you almost buy, and what stopped you? Who else had a say?
- Anxieties. What worried you about ordering? What did you check before you bought? What would have made you abandon the order?
- Habits. What were you using before? What did you have to give up? What made it hard to let go of the old way?
- The purchase. Walk me through the day you ordered. What time was it, where were you, what device? How long between deciding and paying?
- First use. What happened when it arrived? What was the first week like? What did you tell other people about it? What has changed for you since?
Two habits carry most of the quality. Ask for the specific occasion rather than the general habit ("tell me about the last time" beats "what usually happens"). And when an answer sounds like a slogan, ask what happened just before, until you get back to an event.
How to debrief and cluster the interviews
Give every debrief file the same six sections so that clustering later is mechanical rather than interpretive.
- Setup: the context, who the customer is, what their life looked like before.
- Pushes: the problem or pain point that started the process.
- Pulls: what attracted them to the new solution.
- Habits: the resistance to change and what they had to give up.
- Anxieties: the questions and worries about the product.
- Observations: anything true and interesting that does not fit the other five.
Once the clusters are stable, each one should be readable as a job: a situation, a struggle, and the progress the customer wanted. The table below shows how to read each signal and what to do with it.
| Signal in the interview | What it reveals | What to do with it |
|---|---|---|
| The triggering event | When demand is created, not where it is captured | Time campaigns and lifecycle emails to the event, not to the calendar |
| Repeated anxiety | An unanswered question blocking the order | Answer it on the product page or in checkout, then A/B test the change |
| What they nearly bought instead | The real competitive set, which is rarely your assumed one | Rewrite comparison and category copy against the actual alternative |
| The customer's own words | The vocabulary the market uses for the problem | Use it in headlines, ads, search, and on-site navigation |
| The trade-off they accepted | Which attributes are negotiable and which are not | Protect the non-negotiables in product and pricing decisions |
| The first-week experience | Whether the job was completed after the sale | Fix onboarding and post-purchase, then watch repeat purchase rate |
Jobs To Be Done interviews are the third step of the Customer Value Optimization timeline, and they only pay off if the output leaves the research document. Every cluster should end as a hypothesis with an owner and a metric.
Frequently Asked Questions
A Jobs To Be Done interview is a qualitative interview with a customer who recently bought your product, designed to reconstruct the story of the purchase decision. Instead of asking what the customer thinks of the product, you rebuild the timeline of events that moved them from a first thought to a purchase, and the forces that pushed and pulled them along it. The output is the job the customer hired your product to do.
Jobs To Be Done has more than one origin. Tony Ulwick developed Outcome-Driven Innovation in the early 1990s and introduced the underlying idea to Clayton Christensen in 1999. Christensen popularized Jobs To Be Done as a theory of innovation, most fully in Competing Against Luck (2016). Bob Moesta, founder and CEO of The Re-Wired Group and a fellow at the Clayton Christensen Institute, developed the interview method used to uncover jobs, and defines a job as the progress a person is trying to make in a struggling moment.
Practitioners usually plan for roughly 10 to 12 interviews per job or per market you want to understand. Patterns tend to repeat well before that, and once two or three consecutive interviews produce nothing new, you have enough for a first round. Depth matters more than volume: five well-run interviews with real buyers beat fifty rushed ones.
Interview people who actually bought, because only they can describe the full path to a decision. Recent buyers are best, since they still remember the sequence of events. Cover a spread of profiles rather than one demographic, and include customers from your most valuable segments. RFM segmentation in Nexus by Omniconvert identifies those segments, so your recruiting list is based on real purchase behavior rather than a guess.
Plan for 45 to 60 minutes, with two people on your side: one leading the conversation and one listening and taking notes. Add 30 to 45 minutes immediately afterwards to debrief while the story is fresh. Anything shorter rarely gets past the rehearsed answer to the real sequence of events.
Ask questions that reconstruct events rather than collect opinions. Start with when the customer first thought about solving the problem, what happened that day, who else was involved, what they looked at and rejected, what nearly stopped them, and what the first week with the product was like. Ask when, where, and who questions, not why questions, because why invites the customer to invent a rationalization.
The four forces are the push of the situation (the problem or frustration with the current state), the pull of the new solution (the appeal of the outcome), the anxiety of the new solution (worry about the unknown), and the habit of the present (attachment to the current way of doing things). The first two promote change, the last two block it. A purchase happens when push and pull outweigh anxiety and habit.
A survey collects stated preferences at scale, which shows what correlates with a purchase. A JTBD interview reconstructs one purchase in detail, which shows what caused it. The two work together: use surveys and on-site polls in Omniconvert Explore to find where and when people hesitate, then use JTBD interviews to find out why the hesitation exists.
Pick one product and one question you genuinely cannot answer from your analytics. Pull a list of 12 recent buyers from your most valuable RFM segments, spread across ages, genders, and order sizes. Book 45 minutes with each, and block 45 more straight after each call for the debrief. Do not write a questionnaire; write the timeline and the four forces on one page, and use it as a map while the customer tells the story. After ten conversations you will have clusters, and after the clusters you will have jobs. Then the real work starts: turning each job into a change on the site, in the product page copy, or in the post-purchase experience, and testing whether it moves anything.
Find the customers worth interviewing
Nexus by Omniconvert segments your customer base with RFM analysis, so you know which customers carry the most value before you decide who to call. Build the interview list from real purchase behavior, then track whether the changes you make from the interviews move repeat purchase rate and customer lifetime value.