An Interview Is Not a Pitch With a Question Mark
The worst customer interview is a sales call wearing a lab coat.
You’ve heard one. Maybe you’ve run one. “So, would you use a tool that did X?” The customer, who is a decent person, says “Sure, probably.” Everyone leaves happy. Nobody learned anything. The persona built from that conversation is fiction with footnotes.
Rob Fitzpatrick wrote a whole book about this failure — The Mom Test — and its rules fit on an index card: talk about their life, not your idea. Ask about specifics in the past, not opinions about the future. Talk less. Listen more. Questions that follow these rules get honest answers even from your own mother, who loves you and would otherwise lie to protect your feelings.
Every question below passes that test. They’re about the person across the table: their Tuesday, their goals, their duct-tape workarounds, their last purchase, their words. Your product doesn’t come up. That’s the point. You’re not here to validate. You’re here to understand a real person well enough to serve them — which is the entire reason personas exist.
How to Use This Bank
A question bank is a pantry, not a menu. Nobody eats everything.
Pick ten to twelve questions for a 30–45 minute conversation — two or three per theme, weighted toward whatever decision your personas need to inform. Then hold the list loosely. Nielsen Norman Group calls this the semi-structured interview: a plan you’re willing to abandon the moment the person says something more interesting than your next question. They usually do.
Three logistics that matter more than they sound:
- Record it. With permission. Your memory will flatten their words into your words, and their words are half the value.
- Interview in pairs. One asks, one takes notes. The asker’s job is eye contact, not typing.
- Save five minutes for the closer. “What should I have asked that I didn’t?” It out-performs half the prepared list.
The pocket card
Six questions to carry into any interview. Cut out. Keep honest.
- Walk me through yesterday.
- What are you on the hook for this quarter?
- Tell me about the last time this slowed you down.
- What have you cobbled together to cope?
- Who else was involved in that decision?
- What should I have asked that I didn’t?
Ask why. Then wait.
Theme 1: Context & Day-in-the-Life
You can’t understand the problem until you’ve seen the Tuesday it lives in.
Start here because it’s easy to answer and impossible to fake. Nobody rehearses a description of their ordinary day. And your product — whatever it is — will live inside that ordinary day, competing with meetings, Slack, and lunch. Context questions tell you what you’re really up against.
Follow-up craft: “the last time” beats the hypothetical. When an answer drifts into generalities (“I usually…”, “we normally…”), pull it back to a specific event: “Tell me about the last time that happened.” Generalities are self-image. Specifics are behavior. Personas are built from behavior.
Theme 2: Goals & Motivations
People don’t buy products. They hire them to move a goal forward.
Goals are the engine of every useful persona. Not feature wishes — the deeper stuff: what this person is measured on, what they’re building toward, what “winning” means this quarter and this career. If you know the goal, you can predict the behavior. (This is the core idea behind jobs-to-be-done, and it pairs beautifully with persona work.)
Follow-up craft: the five whys. Borrowed from Taiichi Ohno’s factory floor at Toyota, where asking “why” five times traced a blown fuse back to a missing strainer. It works the same on goals. “I want better reporting.” Why? “So I can see pipeline weekly.” Why weekly? “Because the board asks.” Why does that worry you? Now you’re somewhere real. Five is not a magic number. Stop when you hit rock.
Theme 3: Frustrations & Workarounds
The workaround is the confession. Find the duct tape and you’ve found the demand.
People will tell you they’re “fine” with their current process all day long. But if they’ve built a spreadsheet, hired an intern, or set a weekly reminder to compensate — they’re not fine. They’re already paying for a solution. In time, in error, in patience. Frustration questions find the pain; workaround questions prove it’s real.
Follow-up craft: silence. Steve Portigal, whose Interviewing Users is the standard text on this craft, teaches interviewers to get comfortable with the pause. Ask the question. Then stop. Count to five in your head if you must. The first answer is the polished one; the thing they say to fill the silence is the true one. Amateurs fill pauses. Professionals collect them.
Theme 4: Buying & Decision Process
Nobody remembers what they might buy. Everybody remembers what they did buy.
So don’t ask about the future. Ask about the last real purchase in your category — the trigger, the shortlist, the people in the room, the near-miss. Past purchases are the only reliable data about future ones. This theme matters double if you sell to teams, where the user and the buyer are different people with different questions.
Follow-up craft: follow the money and the calendar. Vague enthusiasm is free; budgets and dates are not. When someone says a problem “really matters,” ask what it’s cost them and when they last tried to fix it. If the answer is “nothing” and “never,” you’ve learned something important too. Write it down with a straight face.
Theme 5: Language & Worldview
Steal their words. Yours are worse.
Every field has a dialect. Your customers describe their problem in words that are not your feature names, search in phrases that are not your category, and trust sources that are not your blog. Capture the dialect verbatim and your persona hands copy to marketing, search terms to SEO, and a voice to every writer on the team. Paraphrase it and the value evaporates.
Follow-up craft: capture, don’t translate. When a phrase surprises you, write it down exactly. Erika Hall’s Just Enough Research puts the first rule of user research bluntly: never ask anyone what they want. Ask what they do, and keep their words intact while they tell you. The quote at the top of a great persona — the one the whole team remembers — comes from this theme.
Questions to Burn
Some questions produce answers. These produce noise.
“Would you use a tool that…?” Hypothetical. People are generous with their imaginary time and imaginary money. The yes means nothing. Ask what they did last time instead.
“Do you like it?” Compliment-fishing. Decent people say yes to your face. The data arrives later, as churn.
“How much would you pay for this?” Unanchored guessing. Ask what they pay today — in subscriptions, salaries, and lost hours — and do your own math.
“Don’t you find the current process frustrating?” A leading question smuggles its answer in. You’ll get agreement, not information.
The pattern behind all four: they ask the customer to do your job — to design, to price, to validate. That’s not their job. Their job is to tell you the truth about their life. Yours is to listen hard enough to deserve it.
From Answers to Personas
Eight good interviews will bury you in notes. That’s the plan working.
Now synthesize. Cluster what you heard by behavior and goal — not demographics — and turn each cluster into a named, concrete persona. We’ve written the full playbook for that step in how to create a user persona, and if you want to widen the evidence beyond interviews — surveys, analytics, support tickets — see persona research methods. A ready-made structure is in our free persona template.
Or skip the blank page entirely. Build a persona right now — free, no signup — and pour your interview notes straight into it while the voices are still fresh.
Interviews done? Don’t let them cool.
Turn today’s conversations into a persona your team can use tomorrow.
Build a persona right now — free, no signup →Frequently Asked Questions
What questions should I ask in a user persona interview?+
Ask about their life, not your product. Cover five themes: daily context (“walk me through yesterday”), goals (“what are you on the hook for”), frustrations (“tell me about the last time this slowed you down”), buying process (“who else was involved”), and language (“how would you describe this to a colleague”). Anchor everything in specific past events.
How many questions do you need for a persona interview?+
Prepare ten to twelve for a 30–45 minute session — and expect to ask fewer. Pick two or three per theme, then spend the saved time on follow-ups: why, tell me more, what happened next. The script is a safety net, not a track.
What is the Mom Test in customer interviews?+
Rob Fitzpatrick’s rule set for honest customer conversations: talk about their life instead of your idea, ask about past specifics instead of future opinions, and talk less while listening more. Questions that pass produce useful data even from someone who loves you and wants to be nice.
What questions should you avoid in a persona interview?+
Hypotheticals (“would you use…”), compliment-fishing (“do you like…”), unanchored pricing (“how much would you pay…”), and leading questions that contain their own answer. Each one gets a polite, inaccurate response. Replace it with a question about a specific past event.
How long should a persona interview take?+
Thirty to forty-five minutes. Shorter gets only rehearsed answers; longer and both sides fade. Record with permission, interview in pairs when possible, and keep five minutes for the closer: “What should I have asked that I didn’t?”
One more thing. The questions are the easy part — you can print the card and carry it today. The hard part is the discipline behind them: no pitching, no leading, no filling silences. Do that for eight conversations and you’ll know your customer better than most competitors ever will. Then bring it into Userforge and give your whole team the same clarity.