Interview Guide / Research Protocol

Also known as: Moderator Guide / Interview Protocol

discoverylowerBeginner

TL;DR

The structured script ensuring consistency and depth in every research session.

Strategic value

Ensures different groups or users hear the same questions, approximately in the same order and context, allowing to reveal the subtleties of participants' viewpoints.

Category: research-opsEstimated time: 2-4 hours (depending on study complexity)

What is it

The Interview Guide (or Research Protocol) is the document that structures the questions, topics, and flow of a qualitative research session. It includes opening questions, main topics, probing questions, and closing, ensuring consistency across sessions without being a rigid script.

What it is for

✓Ensure consistency across multiple interview sessions
✓Guide the researcher without limiting spontaneous exploration
✓Document research objectives and key questions
✓Allow other researchers to replicate the study

Research methods that feed it

Prior desk researchDefined research objectivesTeam hypotheses to validate

When to use it

✓Before each round of interviews or usability tests
✓When multiple researchers will conduct sessions
✓To document a study's methodology
✓When you need protocol approval before execution

When NOT to use it

✗For informal quick discovery conversations
✗If you're only doing 1-2 exploratory interviews
✗As a rigid question script (should be flexible)

Required components

✓Introduction: section to 'break the ice', set tone and explain process; include script where moderator introduces themselves
✓Impartiality statement: declare that moderator is not personally involved in product design
✓Warm-up questions: initial questions on demographics, technology use or general topic questions
✓Main discussion or tasks: central section with general topics or detailed tasks the user will attempt

Optional components

○Satisfaction and closing questions (Wrap-up): final questions to conclude, gather feedback or measure satisfaction
○Integrated questionnaires: brief questionnaires nested within the guide for specific moments

How to create it step by step

1Define objectives: What do you need to learn? Write 3-5 research questions (not interview questions).
2Structure the guide: Intro/consent (5 min) → Warm-up questions (5 min) → Main topics (30 min) → Closing (5 min).
3Write open-ended questions: 'Tell me about...' instead of 'Do you like X? yes or no'. Avoid leading questions.
4Add probing prompts: 'Can you give me an example?', 'What happened next?', 'How did that make you feel?'
5Include tasks (if applicable): For usability tests, define specific tasks with success criteria.
6Pilot the guide: Run 1-2 pilot sessions to adjust timing, wording, and flow.

Tips for small teams

A 1-2 page guide is enough — don't make a 10-page document
Memorize the main topics but carry the guide as reference
Leave room to follow interesting threads that emerge
Share the guide with your team before sessions for feedback

Common mistakes

✗Asking closed questions (yes/no) instead of open-ended ones
✗Filling the guide with too many questions (time won't be enough)
✗Not piloting the guide before using it
✗Following the guide as a rigid script without adapting to responses

Quality criteria

✓Execution consistency: allows different groups to hear the same questions in the same order and context
✓Time and depth control: ensures all topics receive necessary time without falling short
✓Question formulation balance: achieves the difficult balance of specific but open-ended questions
✓Acts as anchor for researcher: helps remember main concerns without getting lost in irrelevant details

Authority quotes

“A discussion guide is a document with the list of questions the researcher will ask throughout the session.”
— Observing the User Experience

“The discussion guide is a script that the moderator must follow. It creates a coherent framework and schedule for the focus group series.”
— Focus Groups Handbook

“Unlike a questionnaire, the topic guide lists the general topics to be discussed.”
— Qualitative Research Methods

Contextualized example

Context: Research on onboarding experience in a fintech app.

Research objective: What barriers do users encounter when activating their account for the first time?

Warm-up question: 'Tell me about the last time you opened an account on a financial app.'

Main topic: 'Talk to me about the process of activating your account on [app]. What do you remember?' (followed by: 'Was there a moment when you hesitated or stopped? What happened?')

Template available

Format: Google Docs$10 USD

Phase

discovery

Audience

product-team

Complexity

lower

Experience level

Beginner

Related deliverables

Related methodologies

Free tool by UXR — UX Research Consulting in Chile