What is an interview guide?
An interview guide is the written plan for a research conversation.
It covers the objectives, the opening, the main question sequence, the probes to use when an answer is thin, and the close.
A guide is not a script. It exists so that ten interviews cover comparable ground and so the interviewer can follow an unexpected thread without losing the thread they came for. Good guides are short, often a single page, and front-load the questions that matter most, because time always runs out.
Why it matters
Without a guide, each interview drifts toward whatever the participant found most interesting, and the set cannot be compared. With a script read verbatim, the participant never volunteers the thing you didn't know to ask. The guide is the middle position.
Example
A one-page guide: 2 minutes of context, 15 minutes reconstructing the last time the problem occurred, 10 minutes on what they tried and what it cost, 5 minutes on who else is involved in deciding, 3 minutes for anything you should have asked.
In UpSight
You build the guide in UpSight as a question list tied to the project's research questions. During a desktop-recorded interview, the guidance panel shows the guide and lets you tick questions off as you go. After the interview, UpSight links the evidence to the research questions and decision questions on its own. The link is to the question you were trying to answer, not to the exact wording of each prompt.
Related terms
FAQ
- How long should an interview guide be?
- One page. Guides longer than that are scripts in disguise and get read rather than used.
- Should you send the guide to participants in advance?
- Usually not. Prepared answers are less useful than spontaneous ones. Sending the topic and the time commitment is enough.
- What's the most important question in any guide?
- The last one: "what should I have asked you that I didn't?" It routinely produces the best material in the session.