How to Write a User Interview Guide That Produces Better Insights
Learn how to write a user interview guide with clear goals, better question flow, and unbiased prompts that lead to stronger insights.
A good interview guide is not a script
The quality of your guide shapes the quality of your insights. If it is vague, biased, or overloaded, interviews turn into scattered conversations and analysis gets messy fast. A strong guide keeps the study focused, gives interviewers a consistent structure, and still leaves room to follow unexpected threads.
The most common mistake is treating the guide like a questionnaire to get through. It is closer to a discussion map — what to learn, in what order, and where to probe — not a script to read word-for-word. (See also When to Use Surveys vs Interviews.)
Start with the objective, not the questions
Before writing questions, define the research objective in a sentence or two — the job the interview needs to do, e.g. "Learn why trial users drop off in the first week." This prevents the most common failure: mixing multiple studies into one conversation. A guide covering onboarding, pricing, and support at once produces shallow answers across all three.
Then separate three layers teams blur: the research objective (the decision behind the study), the research question (what you need to learn, e.g. "what blocks users from completing setup?"), and the interview question (what you ask, e.g. "walk me through the last time you set up your account"). Participants can't answer abstract prompts like "What are your onboarding barriers?" — but they can describe what happened. If an interview question sounds like it belongs in a slide deck, rewrite it into plain language.
Build around topics, then anchor in behavior
Organize the guide into 4 to 6 topic areas, not 25 standalone questions. Under each, write a short goal, 1 to 3 core prompts, and likely probes. A simple reusable arc: an intro that sets expectations, background on role and context, recent experience ("Walk me through the last time you did this"), friction ("Where did it get difficult?"), impact ("Why did that matter?"), and a close.
Anchor the interview in specific past behavior; people recall what they did far better than they predict what they might do. Weak guides lean on opinions ("Do you like this?", "Would you use this feature?"), which produce attitudes, not evidence. Prioritize behavioral questions — "Tell me about the last time this came up." If a participant can answer without referring to a real situation, the question is too abstract.
Remove leading language aggressively
Small wording choices push participants toward the answer you expect — especially risky when researching your own product. Leading questions hide assumptions: "How helpful was the new dashboard?" assumes it was helpful. Rewrite to let the participant supply the judgment — "What was your experience using the dashboard?" Also watch for double-barreled questions ("Was it easy and useful?"), assumptive ones ("When do you use our dashboard?"), and accusatory wording ("Why didn't you complete setup?" vs. "What happened after you started setup?"). This matters most when founders interview their own customers.
Plan your probes and timing
The best insights come from follow-ups, not first answers. Add planned probes under each topic so they're consistent across interviewers — "Can you give an example?", "What happened after that?" — covering sequence, context, decision-making, constraints, and impact. For the conversation skills on top of the guide, see How to conduct better customer interviews.
Keep it short enough to finish well: 5 to 7 core questions for a 30-minute interview, 8 to 12 for 45 to 60 minutes, not counting follow-ups. Label each Must ask, Nice to ask, or Only if time allows.
Make it reusable, then check it
A reusable guide is structured, not generic. Keep the objective, intro and consent language, core sections, standard probes, and an interviewer debrief consistent, then customize the prompts per study. The debrief pays off during synthesis — see How to Analyze Customer Interview Data.
Before recruiting, check: Is the objective narrow? Are research questions separate from interview questions? Does it favor past behavior over speculation? Is the wording neutral? Does it fit the session length? Have you piloted it? If any answer is no, fix the guide first — it's far easier to fix the instrument upfront than to salvage weak data later.