PersonaRail
Persona based personalization for online stores

Jobs to Be Done Interviews: The Fastest Way to Build a Persona That Holds

Ask a buyer what they want and they will describe your product back to you. Ask what they were doing the day they bought it, what they compared it to, and what almost stopped them, and you will hear the job they hired it to do.

A jobs to be done interview does not ask a buyer what they want. It asks what happened. What were you doing the day you bought this, what were you using before, what did you compare it against, and what almost stopped you from buying. The answers describe the job the buyer hired the product to do, and the job is what a persona should be built on, not the buyer's age, income, or taste in fonts. The method comes from Clayton Christensen's work, and its central claim is that people do not buy products, they hire them to make progress in a specific situation. A persona built from demographics describes who the buyer is. A persona built from jobs describes what the buyer is trying to do, and the second one survives contact with reality because the job is stable while the demographics drift.

The four questions that do the work

The first question is about the trigger: what happened the day you decided to buy. The answer is usually a specific event, a broken product, a deadline, a recommendation from a friend, not a general desire. The trigger is the segment's entry point, and it decides the timing of every message you send them.

The second question is about the comparison set: what did you consider instead. The answer tells you who your real competitors are, and they are often not who you think. A buyer comparing your $80 tool against a $12 workaround is not comparing you against your category rival. They are comparing you against doing nothing, and your message has to beat doing nothing, not beat the rival.

The third question is about the near miss: what almost stopped you. The answer is your objection list, in the buyer's own words, and it is usually one thing: price, a missing feature, a doubt about quality, a shipping date. The fourth question is about the first use: what did you do with it first. The answer tells you what the onboarding should show, because the first use is the job in miniature.

Related reading on this site: PersonaRail and Exclusion Personas: Defining Who a Campaign Is Not For cover the neighbouring problems in more depth.

Five interviews beat fifty survey responses

A survey can tell you how many buyers share a trait. It cannot tell you why, and the why is the persona. Five interviews, done well, will surface the job, the trigger, the comparison set, and the objection, because each interview is a story with a beginning, a middle, and a decision. Fifty survey responses will give you a distribution of answers to questions you already thought to ask, which is useful for sizing a segment and useless for understanding it.

The interview is a conversation, not a questionnaire. Record it, transcribe it, and pull the exact phrases the buyer used, because those phrases are the copy. A persona that quotes the buyer's words for the objection will write better emails than a persona that paraphrases them into marketing language. The buyer's sentence, I almost did not buy it because I was not sure it would fit my car, is a headline. Your paraphrase, fit anxiety, is a label.

From interview to persona in one afternoon

After five interviews, the pattern is usually visible. Group the buyers by the job they described, not by who they are. Two buyers with different ages, incomes, and locations who hired the product for the same job belong in the same persona. Two buyers who look identical on paper but hired it for different jobs belong in different ones. That grouping is the persona, and it is the only grouping that predicts what they will buy next.

Write the persona as a job statement with the evidence attached: the trigger, the comparison set, the objection, and the first use, each with a quote. Then write the expiry date on it, 6 months out, and the name of the person who will re-validate it. A persona built this way is small, specific, and falsifiable, which is why it holds. A persona built from demographics is none of those things, which is why it decays.

Frequently asked questions

What is a jobs to be done interview?

An interview that asks what happened around a purchase, not what the buyer wants. What were you doing the day you bought it, what did you compare it against, and what almost stopped you. The answers describe the job the buyer hired the product to do.

How many interviews do you need to build a persona?

Five, done well. Five interviews will surface the job, the trigger, the comparison set, and the objection. Fifty survey responses will give you a distribution of answers to questions you already thought to ask, which sizes a segment but does not explain it.

Why build personas from jobs instead of demographics?

Because the job is stable while demographics drift. Two buyers with different ages and incomes who hired the product for the same job belong in the same persona. Two buyers who look identical on paper but hired it for different jobs belong in different ones.

What should a persona document contain?

A job statement with the evidence attached: the trigger, the comparison set, the objection, and the first use, each with a quote in the buyer's own words. Then an expiry date, 6 months out, and the name of the person who will re-validate it.

© 2026 PersonaRail · 447 Broadway, 2nd Floor #796, New York, NY 10013 · llms.txt