Skip to main content
← User Interview
Spoke · Updated May 2026 · 8 min read

User interview script

A word-for-word 60-minute walkthrough — opening lines, transitions, follow-ups, closing. Read it twice, internalize the rhythm, throw it away.

How to use the script

The script below is a rhythm and a fallback. You read it twice before the first interview, run two real conversations using it, and after that you stop reading and start improvising. By interview five it should sound like you, not like a script.

Three things matter more than the words: silence (count to four after every answer), past-tense framing ("the last time" not "would you"), and screen-share (when applicable, makes them stop summarizing and start showing).

0:00 – 0:02

Opening

Set tone, get consent, lower stakes.

"Hey [name], thanks so much for making time. Before we start — quick three things. This will take about an hour. There are no right or wrong answers here, I'm here to learn from your experience, not test your knowledge. And I'd love to record this so I don't have to take notes — it stays internal to my team. Sound good?"
0:02 – 0:05

Warm-up

Get them talking comfortably about something easy.

"To start — could you walk me through what a normal week looks like for you? What are the things you spend most of your time on?"
0:05 – 0:08

Transition into the topic

Move from general to specific without leading.

"Cool — I want to dig into [topic area]. Specifically, I'd love to hear about the last time you actually did [task]. Could you walk me through what happened, step by step?"
0:08 – 0:20

Workflow walkthrough — let them lead

Listen, follow up, do not interrupt.

"Got it. And then what happened?" / "Tell me more about that part." / "Why did you do it that way?" / "What was going through your head right then?"
0:20 – 0:30

Pain points

Find friction by asking about specific moments, not opinions.

"What was the most annoying part of that whole thing?" / "When was the last time something there actually broke for you?" / "What workaround have you ended up with?"
0:30 – 0:40

Alternatives & comparisons

Map their actual decision tree.

"What else did you consider when you were figuring this out?" / "What did you use before this?" / "If you had to switch tomorrow, what would you switch to and why?"
0:40 – 0:55

Prototype / feature reaction (if applicable)

Show, don't describe. Watch their face.

"I want to show you something quick — sharing my screen. Take a look. Don't read it carefully yet — just tell me what you think this is and what it does." / [pause] / "Where do your eyes go first? Why?" / "If you wanted to do [task], where would you click?"
0:55 – 1:00

Wrap-up

Catch the thing they were holding back.

"This has been incredibly helpful. Two last questions. First — what didn't I ask about that I should have? Second — who else on your team would be useful for me to talk to? Thanks again — I'll send the [incentive] within 24 hours."

6 follow-ups to memorize

These six phrases handle 90% of the moments where you need to dig deeper. Memorize them — they become the backbone of every section above.

"Tell me more about that specific time."

"Walk me through exactly what happened next."

"Why did you choose that over the alternatives?"

"How did that feel — frustrated, neutral, surprised?"

"What would have made that easier?"

"Has that happened before? When?"

What not to say

Avoid

  • "Would you use a feature that…"
  • "Do you think this is a good idea?"
  • "On a scale of 1–10 how excited are you?"
  • "What features do you wish existed?"
  • "If we built this, would you buy it?"

Replace with

  • "Tell me about the last time you tried to do that."
  • "What problem are you currently trying to solve here?"
  • "Walk me through your most recent attempt."
  • "What workaround have you built?"
  • "What\'s the most you\'ve ever paid to solve this?"

Run the script live first

GoNoGo lets you run the script against an AI persona before your first real interview. You hear the awkward silences, the leading questions you didn't notice, and which sections drag — without burning a real participant slot.

Rehearse my interview →

Free · No credit card · up to 25 reports

Frequently asked questions

Should I literally read this script verbatim?+
No — read it twice, internalize the rhythm, then improvise. A scripted-sounding interview triggers polite-mode in the participant; you stop getting honest answers. The script is here so you have something to fall back on if you blank, not because you should sound rehearsed.
How do I handle silence?+
Lean into it. The 3–5 seconds after someone finishes answering are the most valuable moment in the interview — that's when they decide whether to add the second sentence. Most interviewers panic and ask the next question. Don't. Count to four in your head before you speak.
What if the participant goes off on a tangent?+
Let them — for at least 60 seconds. Tangents are usually more honest than answers to your prepared questions. If after a minute the tangent isn't producing signal, gently redirect: "That's really interesting — could we come back to [topic] for a second?"

More on user interviews