New

Now in Claude, ChatGPT, Cursor & more with our MCP server

Back to docs
Interview Techniques

User Interview Guide Template: How to Plan, Run, and Analyze Interviews

A practical template for creating user interview guides that produce consistent, actionable insights — whether you run 5 interviews or 500.

A user interview guide is a structured document that shapes every conversation you have with research participants. Without one, interviews wander, data becomes inconsistent, and insights are hard to compare across sessions. With a solid guide, every interview delivers comparable, actionable data.

An interview guide is not a rigid script — it is a flexible framework. Think of it like a GPS: you have a destination (your research question) and a planned route (your questions), but you are free to take detours when something interesting comes up. The guide ensures you cover the critical territory while leaving room for discovery.

How It Works

A well-structured guide typically has three phases: a warm-up phase to build rapport, a core section covering your main research areas, and a closing phase to wrap up and surface anything you missed.

The best interview guides are developed collaboratively before research begins. This process forces your team to align on what you actually want to learn — which is often more valuable than the guide itself. According to Nielsen Norman Group, the single biggest failure mode in user research is asking the wrong questions. A guide forces you to commit to the right ones.

With AI-powered platforms like Koji, your interview guide becomes a living research brief. The AI consultant helps you construct the right questions for your goals, and the AI interviewer uses that brief to conduct consistent, probing conversations with every participant — automatically following up when someone says something interesting.

Step-by-Step: Building Your Interview Guide

  1. Start with your research question Before writing a single interview question, write down the one thing you most want to learn. Everything in your guide should connect back to this. For example: "Why do customers stop using our product after the first month?" This single question should fit on a sticky note. If it takes a paragraph, you have multiple research questions — pick one or run separate studies.

  2. Define your topic areas Break your research question into 3–5 topic areas to explore. These become the sections of your guide. For a churn question, you might explore: onboarding experience, initial expectations vs. reality, awareness of competing tools, and the final decision to stop. Each topic area gets its own block of questions.

  3. Write opening questions Start broad and comfortable. "Walk me through how you first heard about [product]" or "Tell me about the last time you [relevant activity]." These warm participants up and give you context before you get specific. A good opening question puts the participant in storyteller mode — that is exactly where you want them.

  4. Write core questions For each topic area, write 2–4 open-ended questions. Use "how," "what," "why," and "tell me about" phrasing. Avoid yes/no questions or anything that leads the participant toward a particular answer. Bad: "Did you find the onboarding confusing?" Good: "What was your experience like during the first week?"

  5. Add probing prompts Include reminder prompts beside each core question: "Can you tell me more about that?" / "What happened next?" / "How did that make you feel?" / "Why was that important to you?" These help you go deeper without pre-planning every follow-up. Probing is where the real insights live.

  6. Write a closing section End with: "Is there anything about [topic] we have not talked about that you think I should understand?" This catches insights you did not anticipate. Then thank the participant and explain next steps. A good close takes 5 minutes and consistently surfaces the most surprising data of the session.

  7. Pilot-test your guide Run one internal practice interview before going live. You will immediately spot questions that are confusing, too similar to each other, or in the wrong order. One pilot interview saves hours of data that cannot be used because the questions were flawed.

The Interview Guide Template

Here is the standard template structure. Copy it, adapt it, and use it for every study.

[Study Name] — Interview Guide Research Question: [One sentence] Date: [Date range] Interviewer: [Name] Session length: [X minutes]


Warm-Up (5–10 min)

  • Tell me a bit about your role and what you work on day-to-day.
  • How long have you been [doing the relevant activity]?
  • Walk me through the last time you [relevant experience].

[Topic Area 1] (10–15 min)

  • [Core question 1]
    • Probe: Tell me more about that.
    • Probe: What happened next?
  • [Core question 2]
    • Probe: How did that feel?
    • Probe: Why was that important to you?

[Topic Area 2] (10–15 min)

  • [Core question 3]
  • [Core question 4]

[Topic Area 3] (10–15 min)

  • [Core question 5]
  • [Core question 6]

Closing (5 min)

  • Is there anything about [topic] that we have not covered that you think I should know?
  • Do you have any questions for me?

Key Things to Know

  • Length: A 60-minute interview guide should have roughly 8–12 main questions. Less is more — depth beats breadth every time. A 60-minute session with 5 deep questions produces better data than the same session with 20 shallow ones.

  • Question order matters: Move from general to specific, from past to present, from easy to sensitive. Never start with the hardest question — trust needs to build first.

  • Guide vs. script: A guide is a flexible tool. If a participant says something unexpected and interesting, follow it. Then return to your guide. The skill of interviewing is knowing when to follow a thread and when to redirect.

  • One question at a time: Never combine questions ("What happened and how did you feel?"). Split them and let the conversation breathe. Combined questions let participants answer only the part they are comfortable with.

  • Avoid hypothetical questions: "What would you do if..." produces unreliable data. "Tell me about a time when..." produces real behavior. Always anchor questions in past experience.

Tips & Best Practices

  • Keep your research question visible while you interview — tape it to your monitor. It is easy to get pulled off-course by interesting tangents that do not serve your goals.

  • Color-code your guide: blue for core questions, green for probes, red for "must ask" items. At a glance, you can see what is essential and what is flexible.

  • After each interview, note which questions worked and which produced shallow answers. Iterate your guide across a series — by interview 5, your questions will be sharper than they were at interview 1.

  • Use Koji to run your interviews automatically. The AI interviewer uses your research brief and generates probing follow-up questions in real time, capturing deeper insights without any moderator effort. Teams using Koji report completing research cycles 10x faster than manual interview methods.

  • For remote interviews, send a one-sentence agenda to participants beforehand: "We will talk for 45 minutes about your experience with [topic]. No preparation needed." This reduces no-shows and puts participants at ease.

How AI Changes Interview Guide Execution

Traditional interview guides require a skilled moderator to execute them well. Reading the guide, following up on interesting threads, managing time, and taking notes simultaneously is cognitively demanding. Many moderators under-probe because they are overwhelmed — a documented failure mode in qualitative research.

AI-powered interview platforms like Koji address this directly. Your research brief is the interview guide, and the AI executes it with complete consistency across every session. It probes automatically when a participant says something that warrants deeper exploration. It does not get tired, distracted, or pulled off track. And it runs sessions 24/7, so participants can interview at their convenience.

This does not replace the need for a well-crafted guide — the quality of your research brief directly determines the quality of your data. What it eliminates is the gap between guide quality and execution quality.

Related Articles

Frequently Asked Questions

Q: How long should a user interview guide be? A: For a 60-minute interview, aim for 8–12 main questions with probing prompts. Each question typically takes 5–8 minutes including follow-ups. If you have more questions than time, prioritize ruthlessly — you can always add a follow-up study.

Q: Should I share my interview guide with participants beforehand? A: No. Sharing questions in advance causes participants to prepare rehearsed answers rather than authentic responses. Share the general topic ("we will talk about your onboarding experience") but not specific questions.

Q: How many times should I use the same interview guide? A: Update your guide after every 3–5 interviews. You will discover questions that consistently confuse participants or yield shallow answers. Continuous refinement produces sharper data across a study.

Q: What is the difference between an interview guide and a survey? A: An interview guide shapes a live conversation — answers lead to follow-up questions that go deeper. A survey collects fixed responses with no follow-up. For understanding the "why" behind behavior, interviews consistently yield deeper insights. For measuring how widespread a behavior is, surveys scale better.

Q: Can I use the same interview guide for voice and text interviews? A: Yes — a well-written guide works across both formats. On platforms like Koji, the same research brief automatically adapts delivery for voice or text mode while maintaining the same research framework and probing strategy.