{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-11-16T00:58:22.198Z"},"content":[{"type":"documentation","id":"ffb50571-9553-4671-9e86-e927e98430fa","slug":"user-interview-guide-template","title":"User Interview Guide Template: Plan From Research Goal to Questions","url":"https://www.koji.so/docs/user-interview-guide-template","summary":"A user interview guide is a structured framework for conducting research conversations. This article provides a complete template with warm-up, core questions, and closing sections, plus guidance on how to pilot-test and iterate your guide. AI-powered platforms like Koji use your guide as a research brief to conduct consistent, probing interviews automatically.","content":"A user interview guide is the plan behind your interviews. You build it top down: name the decision the research will inform, turn it into one research question, split that into 3 to 5 topic areas, and only then write the questions and probes under each topic. Every question should trace back to the research question; if it doesn't, cut it.\n\nThis page covers that planning, from goal to topics to questions, with a worked example. If you want a ready-made script to copy and fill in instead, use the [User Interview Script Template](/docs/user-interview-script-template).\n\n**Try it this week:** before your next study, write the decision and research question at the top of a blank page, list your topic areas under it, and check that each draft question sits under one of them.\n\nAn 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.\n\n## How It Works\n\nA 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.\n\nThe 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. Writing the guide forces you to commit to what you want to learn before the first conversation.\n\nWith 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.\n\n## Step-by-Step: Planning Your Interview Guide, From Goal to Questions\n\nWork top down: decision, research question, topics, then questions. Each layer should trace back to the one above it.\n\n1. **Start with the decision and your research question**\n   Name the decision this research will inform and who will make it. Then, 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.\n\n2. **Define your topic areas**\n   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.\n\n3. **Write opening questions**\n   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.\n\n4. **Write core questions**\n   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?\"\n\n5. **Add probing prompts**\n   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.\n\n6. **Write a closing section**\n   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.\n\n7. **Pilot-test your guide**\n   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.\n\n![Process for planning a user interview guide in four layers: decision, research question, three to five topic areas, then questions and probes.](/visuals/user-interview-guide-planning-goal-to-questions/user-interview-guide-planning-goal-to-questions.png \"Plan from the top down, and cut any question that doesn't trace back to the layer above it.\")\n\n## Worked example: from goal to questions\n\n**Decision:** whether to rebuild onboarding this quarter. **Research question:** \"Why do customers stop using our product after the first month?\"\n\n| Topic area | Why it is in the guide | Example core question |\n|---|---|---|\n| Onboarding experience | Tests whether setup is where people stall | \"Walk me through your first week with the product.\" |\n| Expectations vs. reality | Shows the gap between what they expected and what they got | \"What did you expect it to do for you when you signed up?\" |\n| Competing tools | Shows what they went back to or moved to | \"What were you using for this before, and what are you using now?\" |\n| The decision to stop | Finds the trigger and the moment | \"Tell me about the day you decided to stop using it.\" |\n\nIf a question doesn't serve a topic, and a topic doesn't serve the research question, it doesn't belong in this guide. Park it for another study.\n\n## The Interview Guide Template\n\nHere is the standard template structure. Copy it, adapt it, and use it for every study.\n\n**[Study Name] — Interview Guide**\n*Research Question: [One sentence]*\n*Date: [Date range]*\n*Interviewer: [Name]*\n*Session length: [X minutes]*\n\n---\n\n**Warm-Up (5–10 min)**\n- Tell me a bit about your role and what you work on day-to-day.\n- How long have you been [doing the relevant activity]?\n- Walk me through the last time you [relevant experience].\n\n**[Topic Area 1] (10–15 min)**\n- [Core question 1]\n  - Probe: Tell me more about that.\n  - Probe: What happened next?\n- [Core question 2]\n  - Probe: How did that feel?\n  - Probe: Why was that important to you?\n\n**[Topic Area 2] (10–15 min)**\n- [Core question 3]\n- [Core question 4]\n\n**[Topic Area 3] (10–15 min)**\n- [Core question 5]\n- [Core question 6]\n\n**Closing (5 min)**\n- Is there anything about [topic] that we have not covered that you think I should know?\n- Do you have any questions for me?\n\n---\n\n## Key Things to Know\n\n- **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.\n\n- **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.\n\n- **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.\n\n- **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.\n\n- **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.\n\n## Tips & Best Practices\n\n- 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.\n\n![An open laptop on a white rug, the kind of quiet setup where an interview guide gets written before the first session](https://images.unsplash.com/photo-1643747239531-0e970c6d255e?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w5NDUzMDN8MHwxfHNlYXJjaHw0fHxyZXNlYXJjaGVyJTIwaW50ZXJ2aWV3JTIwbm90ZXMlMjBsYXB0b3AlMjBkZXNrfGVufDF8MHx8fDE3OTQwMzQyMTJ8MA&ixlib=rb-4.1.0&q=80&w=1080)\n\n_Photo by [sarah b](https://unsplash.com/@sixthcitysarah?utm_source=koji&utm_medium=referral) on [Unsplash](https://unsplash.com/?utm_source=koji&utm_medium=referral)_\n\n- 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.\n\n- 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.\n\n- Use Koji to run your interviews automatically. The AI interviewer uses your research brief and asks probing follow-up questions in real time, so every participant gets the same guide and the same depth of follow-up.\n\n- 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.\n\n## How AI Changes Interview Guide Execution\n\nTraditional 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.\n\nAI-powered interview platforms like Koji address this directly. Your research brief is the interview guide: the research goal, the key questions with their types and the guardrails, laid out the same way you planned them above. The AI executes it with complete consistency across every session.\n\n![Koji draft research brief \"Why trials go quiet\" listing three interview questions with their question types](/email/shots/shot-card-brief.jpg \"A research brief in Koji: the goal at the top and the questions under it, each with its type.\")\n 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.\n\nThis 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.\n\n## Related Articles\n\n- [User Interview Script Template](/docs/user-interview-script-template)\n- [The Definitive Guide to User Interviews](/docs/user-interview-guide)\n- [How to Write Great Interview Questions](/docs/writing-interview-questions)\n- [Probing and Follow-Up Questions](/docs/probing-and-follow-up-questions)\n- [Writing a Research Question](/docs/writing-a-research-question)\n- [The Sterile Cockpit Rule for User Interviews](/docs/sterile-cockpit-rule-interviews)\n\n## Frequently Asked Questions\n\n**Q: How long should a user interview guide be?**\nA: 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.\n\n**Q: Should I share my interview guide with participants beforehand?**\nA: 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.\n\n**Q: How many times should I use the same interview guide?**\nA: 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.\n\n**Q: What is the difference between an interview guide and a survey?**\nA: 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.\n\n**Q: Can I use the same interview guide for voice and text interviews?**\nA: 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.\n\n## Further reading on the blog\n\n- [How to Analyze Customer Interview Data: A Complete Guide](/blog/how-to-analyze-customer-interview-data) — You ran the interviews. Now what? Here is a step-by-step process for turning raw transcripts into clear, actionable insights your team will \n- [How to Analyze User Interview Data: A Complete Guide (2026)](/blog/how-to-analyze-user-interview-data) — You ran the interviews. Now what? This step-by-step guide covers how to turn raw interview data into clear, actionable insights — with and w\n- [The Complete Guide to Jobs-to-Be-Done Interviews (JTBD Framework 2026)](/blog/jobs-to-be-done-interview-guide-2026) — Jobs-to-be-done interviews reveal why customers really switch to — or away from — your product. This complete guide covers the JTBD framewor\n\n<!-- further-reading:blog -->\n","category":"Interview Techniques","lastModified":"2026-11-09T06:02:28.876901+00:00","metaTitle":"How to Plan a User Interview Guide: From Goal to Questions","metaDescription":"Plan a user interview guide top down: the decision, the research question, 3 to 5 topic areas, then questions and probes. Worked example and a fill-in template.","keywords":["user interview guide template","interview guide template","how to write user interview guide","user interview questions template","research interview guide","ux interview guide"],"aiSummary":"A user interview guide is a structured framework for conducting research conversations. This article provides a complete template with warm-up, core questions, and closing sections, plus guidance on how to pilot-test and iterate your guide. AI-powered platforms like Koji use your guide as a research brief to conduct consistent, probing interviews automatically.","aiPrerequisites":["writing-a-research-question","writing-interview-questions"],"aiLearningOutcomes":["Create a structured interview guide from scratch","Write effective open-ended questions for each research topic","Build probing prompts that surface deeper insights","Pilot-test and iterate your guide across a study series"],"aiDifficulty":"intermediate","aiEstimatedTime":"9 min read"}],"pagination":{"total":1,"returned":1,"offset":0}}