User interview script template: a complete guide for UX researchers

Q: How do you write good user interview questions?

Start open-ended ('Tell me about a time when...'), avoid leading language ('Don't you find it frustrating that...'), and separate compound questions into individual ones. Frame questions around behavior and past experience rather than hypotheticals. Probes such as 'Can you tell me more?' or 'What happened next?' are essential complements to every core question.

Q: What is the difference between a user interview script and a discussion guide?

They refer to the same document in most research teams. 'Discussion guide' emphasizes the semi-structured, conversational nature: you have prepared questions but you follow the participant's lead. 'Script' can imply a stricter word-for-word format, which is less appropriate for qualitative interviews. In practice, treat yours as a flexible discussion guide regardless of what you call it.

A user interview script is a structured discussion guide that outlines every question, prompt, and transition in a qualitative research session. Having a clear template before you start recruiting saves significant preparation time and produces more consistent, comparable data across participants.

This guide gives you a ready-to-use template you can copy and adapt, along with the reasoning behind each section.

Why a script matters more than you think

Most researchers know they need questions prepared. Fewer invest in structuring the entire session, including the opening, transitions, and close. That gap leads to:

Participants who never warm up and give surface-level answers
Sessions that run over time because there is no clear wrap-up signal
Consent and recording issues because the intro was ad-libbed
Inconsistent data when multiple researchers run the same study

A proper script solves all of these by turning the session into a repeatable, professional process rather than an improvised conversation.

The five sections of a user interview script

Section	Purpose	Typical time
Introduction	Consent, recording, ground rules	3-5 min
Warm-up	Build rapport, gather context	5-8 min
Core questions	Answer your research goals	25-35 min
Task prompts (if any)	Observe behavior on a specific flow	10-15 min
Closing	Capture final thoughts, debrief	3-5 min

Full user interview script template

Copy the template below and replace the bracketed placeholders with your study-specific details.

Section 1: Introduction

Read or paraphrase this section before any questions begin.

“Hi [Participant name], thank you for making time today. My name is [Your name] and I work on the research team at [Company]. With me today is [note-taker name if applicable].

This session should take about [X] minutes. We are here to learn about your experiences with [topic or product area], not to test you. There are no right or wrong answers.

A few things before we start:

We will be recording this session with your permission. The recording is only used internally to help us review notes. It will not be shared publicly.
You can skip any question you are not comfortable with.
You can stop the session at any time.

Do you have any questions before we begin? And are you comfortable with us recording? [Wait for verbal confirmation.]”

Section 2: Warm-up questions

Use these to ease the participant in and gather background context.

Can you start by telling me a bit about your role and what you do day-to-day?
How long have you been in that role?
How does [relevant tool, task, or domain] fit into your typical week?

Note: Warm-up answers often reveal context that reframes your core questions. Listen for signals about workflows, pain points, or vocabulary the participant uses naturally.

Section 3: Core research questions

Adapt these to your specific research goals. Aim for 8-12 questions in a 60-minute session.

Goal: Understand current behavior

Walk me through the last time you [relevant task]. What did you do first?
What tools or resources did you use during that process?
Was there anything that felt slow or frustrating? What happened?

Goal: Understand motivations and context

What were you trying to accomplish when you [relevant action]?
How did you decide to approach it that way rather than another method?

Goal: Explore unmet needs

Is there anything about [topic area] that you wish worked differently?
Have you ever had to work around a limitation? Tell me about that.

Goal: Capture mental models

If you had to explain [concept or product] to a new colleague, how would you describe it?
What does a successful outcome look like for you in this area?

Probing follow-ups to use throughout:

“Can you say more about that?”
“What made you decide to do it that way?”
“What happened next?”
“How did that make you feel?”
“Can you give me a specific example?”

Section 4: Task prompts (for usability or prototype sessions)

Include this section only if participants will interact with a product, prototype, or scenario.

“Now I would like to ask you to [complete a specific task or review a specific flow]. As you go through it, please think aloud and narrate what you are noticing and what you would do next. There is no pressure to complete the task quickly.

[Task prompt]: Please imagine that you want to [scenario]. How would you go about doing that from this screen?”

After the task:

What were you expecting to happen when you [action]?
Was there anything that surprised you?
If you could change one thing about what you just experienced, what would it be?

Section 5: Closing

“We are coming up on the end of our time. Before we finish, I want to make sure I have not missed anything.

Is there anything about [topic] that you wanted to share that we did not cover?
If you were to give one piece of advice to our team about [topic area], what would it be?

Thank you so much for your time today. Your input is genuinely valuable and directly shapes how we think about [product or topic]. [Explain incentive delivery if applicable.] If you think of anything else later, feel free to reach out to [contact email].

Does the note-taker have any follow-up questions? [Pause for 30 seconds.]

Great. I will stop the recording now.”

How to adapt the template for different research goals

Discovery research

When you are early in the research cycle and exploring a problem space, weight the script toward behavior and context questions (Section 3 goals 1 and 2). Minimize task prompts. Keep the conversation broad so participants can surface topics you have not anticipated.

Usability testing

For sessions where participants interact with a product, Section 4 becomes central. Keep the core questions brief and focus on post-task reflection rather than pre-task framing. You want to observe behavior before you ask participants to explain it.

Jobs-to-be-done research

Structure your core questions around the job the participant is trying to accomplish rather than the product itself. Ask about the situation before the task, the outcome they are seeking, and the obstacles in the middle. This approach works well for competitive research and positioning interviews alike.

Concept testing

Show the concept only after establishing the participant’s current context and mental model. Otherwise your framing contaminates their natural perspective. Always ask about existing behavior before introducing new material.

Common mistakes to avoid

Writing closed questions by accident. “Do you find X difficult?” invites a yes or no. Rephrase as “Tell me about a time when X felt difficult.”

Asking hypotheticals. “Would you use a feature that did X?” is unreliable. People are poor predictors of their own behavior. Ask instead about past experience: “Have you ever needed to do X? What did you do?”

Stacking multiple questions. “What did you think of the layout, and was the navigation clear, and did you find what you were looking for?” gives the participant permission to answer only the last question. Separate each question.

Skipping the warm-up. Jumping straight into your research questions puts participants on the spot and reduces depth of response. Even three gentle warm-up questions make a measurable difference in how openly people talk.

Underestimating the close. The final question (“Is there anything you wanted to share that we did not cover?”) surfaces some of the most useful insights in any session. Budget time for it.

Script format: how to lay it out

A practical script format for your research team includes:

Interviewer text in regular type, to be read or paraphrased
Moderator notes in italics or brackets, with guidance on timing, follow-up probes, or things to watch for
Section timings in the margin to pace the session
Space for live notes after each question if you are printing it

Keep the script to one or two pages maximum. Long scripts become unwieldy during a live session. If your study has a lot of ground to cover, run two separate sessions rather than one long one.

Running the script with multiple moderators

When more than one researcher will conduct the same study, script consistency is critical. Brief all moderators together before the study begins, agree on which probes are standard and which are flexible, and debrief after the first two sessions to align on interpretation. Consistent phrasing across sessions makes analysis significantly easier.

Platforms like CleverX support multi-session studies at scale, with either human-moderated or AI-moderated formats, so your discussion guide can be applied uniformly across a large participant pool. For teams running B2B research across many job roles or geographies, this removes a major coordination bottleneck.

Before you write your script: checklist

Research goals documented and agreed with stakeholders
Participant profile defined (screener complete)
Session length confirmed
Recording consent process agreed internally
Note-taking approach agreed (live notes, AI transcription, observer notes)
Pilot session scheduled with a colleague or internal tester

Frequently asked questions

What should a user interview script include? A well-structured user interview script has five core sections: an introduction (consent, session overview, recording notice), a warm-up to relax the participant, core open-ended questions tied to your research goals, any task prompts or scenario walk-throughs, and a closing that invites final thoughts. Each section serves a distinct purpose and keeps the session moving without feeling mechanical.

How long should a user interview script be? For a 45-60 minute session, plan around 8-12 core questions plus warm-up and wrap-up. A tight script for a 30-minute session typically has 5-7 questions. The script is a guide, not a transcript: your questions should leave room for follow-up and natural conversation rather than forcing a word-for-word reading.

Should you read the script verbatim during the interview? No. A user interview script is a discussion guide, not a script to be read aloud. Use it to stay on track, prompt probing follow-ups, and cover all your research goals. Reading verbatim makes sessions feel robotic and discourages participants from speaking naturally. Internalize the questions beforehand so you can focus on listening.

How do you write good user interview questions? Start open-ended (“Tell me about a time when…”), avoid leading language (“Don’t you find it frustrating that…”), and separate compound questions into individual ones. Frame questions around behavior and past experience rather than hypotheticals. Probes such as “Can you tell me more?” or “What happened next?” are essential complements to every core question.

What is the difference between a user interview script and a discussion guide? They refer to the same document in most research teams. “Discussion guide” emphasizes the semi-structured, conversational nature: you have prepared questions but you follow the participant’s lead. “Script” can imply a stricter word-for-word format, which is less appropriate for qualitative interviews. In practice, treat yours as a flexible discussion guide regardless of what you call it.

Can you use the same script for moderated and AI-moderated interviews? With adaptation, yes. For human-moderated sessions the script is a personal guide; probes, tone adjustments, and follow-ups happen live. For AI-moderated interviews the discussion guide is programmed into the interview flow, so questions need to be self-contained and less reliant on spontaneous follow-up. Keep questions shorter and more direct when adapting for an AI-moderated format.

For further reading on qualitative interview best practices, Nielsen Norman Group’s guide to user interviews is a well-regarded starting point.