Remaining:60 min
← Back to Tutorials
🎯 Product•60 min•Beginner•Nov 2, 2026

1 Hour to Run a User Interview

A 60-minute script with 15 proven questions, recording setup, and a synthesis template that actually surfaces insights.

#user-research#interview#product#synthesis

By the end of this hour, you'll have a complete interview script, a working recording setup, and a filled-in synthesis template you can share with your team the same day.

🎯 What You'll Build

A repeatable user interview system: one 45-minute conversation that reliably produces actionable insights — not vague feelings.

Here's what your synthesis template looks like when filled in:

## Interview: Sarah, 34, freelance designer — 2024-06-10

### Top Quote
"I don't even look at the dashboard anymore. I just wait for the email."

### Pain Points (ranked by emotional intensity)
1. Onboarding takes too long — she gave up twice before succeeding
2. Notifications are noisy — she muted them within a week
3. Export format doesn't match her client's expectations

### Aha Moment
She discovered the bulk export feature by accident, 3 months in.
Nobody told her it existed.

### One Thing to Fix First
Mention bulk export in the onboarding checklist.

That output came from 45 minutes of conversation — not a survey, not a focus group. One real person. One focused script.

⏱️ Time Breakdown

0–10min
Set up recording and brief your interviewee
10–25min
Run the opening and context questions (Questions 1–6)
25–40min
Dig into the core pain questions (Questions 7–12)
40–55min
Explore solutions and wrap up (Questions 13–15)
55–60min
Fill in the synthesis template while memory is fresh

📋 Prerequisites

  • One willing participant (a current user, a prospect, or someone from your target audience)
  • A video call tool: Zoom, Google Meet, or even a phone call works
  • Something to record with — covered in Step 1
  • A quiet room with 45 minutes blocked off
  • This guide open in a second tab during the call

Step 1: Set Up Recording and Brief Your Interviewee (0–10 min)

You want to capture everything so you stop frantically taking notes and actually listen. Bad notes look like: "said something about dashboard — check later." Good notes are the full transcript you review afterward.

Option A — Zoom (easiest)

1. Start a Zoom meeting
2. Click Record → Record to this Computer
3. After the call, Zoom saves an .mp4 + an .m4a audio file automatically

Option B — Google Meet + Tactiq (free Chrome extension)

1. Install Tactiq from the Chrome Web Store
2. Start your Meet call
3. Click the Tactiq icon → Start Transcript
4. Real-time captions are saved to your Google Doc automatically

Option C — no tools, just your phone

1. Put your phone face-down on your desk
2. Open the Voice Memos app (iOS) or Recorder app (Android)
3. Hit record before you dial

Once recording is ready, open the call with this exact script — read it word for word:

"Thanks for making time. I want to understand your experience,
not pitch you anything. There are no right or wrong answers —
honestly, the more critical you are, the more helpful it is.
Mind if I record so I don't have to type everything? I'll keep
it internal."

Most people say yes. If they say no, that is completely fine — switch to bullet-point notes and keep going.

✅

Checkpoint

Before moving on: is your recording indicator showing red/active? Can you see your interviewee's face and hear them clearly?

Step 2: Run the Opening and Context Questions (10–25 min)

The goal of this block is to understand who this person actually is and what their world looks like — before you ask about your product at all.

Bad opening question: "What do you think of our product?" Good opening question: "Walk me through the last time you tried to solve [the problem your product addresses]."

The good version gets a story. Stories contain real details. Details become insights.

Here are Questions 1–6. Paste these into a doc and keep them visible during the call:

## Opening & Context (Questions 1–6)

Q1: "Tell me a bit about yourself and what you do day-to-day."
    → Let them talk for 2 minutes. Don't interrupt.

Q2: "When did [the problem] first become something you had to deal with?"
    → You want the origin story, not a summary.

Q3: "Walk me through the last time you dealt with [the problem].
     What happened, step by step?"
    → Magic question. Slow them down if they skip steps.

Q4: "What were you doing right before that? What triggered it?"
    → Context before the problem is gold for positioning.

Q5: "Who else was involved? Did anyone help you?"
    → Surfaces hidden stakeholders and influencers.

Q6: "What did you try before? What made you stop using that?"
    → Competitor and alternative intel. Never skip this one.

The most important rule for this block: after each answer, wait 3 full seconds before speaking. Silence feels awkward to you. To them, it signals you are actually thinking. They will fill the silence with the most honest thing they were about to leave out.

Step 3: Dig Into the Core Pain Questions (25–40 min)

This is where most interviewers get polite and waste the call. You will not.

You are looking for emotional intensity — the moments where their voice changes, they lean forward, or they say "honestly" or "look." Those are your signals to slow down and go deeper.

## Core Pain Questions (Questions 7–12)

Q7:  "What was the most frustrating part of that experience?"
     → If they say "it was fine," ask: "What would have made it
       10x better?" Fine is never fine.

Q8:  "How did that make you feel in the moment?"
     → Feelings, not features. This quote ends up in your deck.

Q9:  "What was the cost of not solving this? Time? Money? Stress?"
     → Quantifies the pain. $200/month or 3 hours/week is a
       headline. "It was annoying" is not.

Q10: "Have you ever told anyone else about this problem?
     What did you say?"
     → Surfaces natural language. Use their exact words in your copy.

Q11: "What have you already tried to fix it yourself?"
     → Workarounds = unmet demand. A spreadsheet hack = a
       product opportunity.

Q12: "What made those solutions not quite work?"
     → The gap between what exists and what they actually need.

When they give you a one-sentence answer, use this follow-up every time:

"Can you tell me more about that?"

Four words. Works on every question. Never wear it out — but use it at least three times per interview.

✅

Checkpoint

At the 38-minute mark: do you have at least one direct quote with emotion in it, and one specific number (time, money, or frequency)?

Step 4: Explore Solutions and Wrap Up (40–55 min)

Do not ask "what features do you want?" That is a trap. People will describe your existing product, or ask for things they will never use.

Instead, ask about behavior and outcomes:

## Solutions & Wrap-Up (Questions 13–15)

Q13: "If this problem disappeared tomorrow, what would be
     different about your day?"
     → Outcome-first thinking. They describe the result,
       not the feature.

Q14: "Have you ever seen anyone solve this well — even partially?
     What did they do?"
     → Benchmarks. They might name a competitor you've never heard of.

Q15: "Is there anything I didn't ask that you wish I had?"
     → Always the last question. Always. You will be surprised
       what comes out here.

Close the call with this script:

"This has been incredibly helpful. I may have one or two
follow-up questions by email — would that be okay? And if
you know anyone else who deals with [the problem], I'd love
an introduction. Thank you so much."

Ask for referrals at the end of every single interview. Recruiting is the hardest part of user research. Let your participants do it for you.

✅

Checkpoint

Before you hang up: have you asked Q15 and let them finish completely before saying goodbye?

Step 5: Ship It (55–60 min)

While the conversation is still alive in your head, open this template and fill it in immediately. Do not wait until tomorrow.

## Interview Synthesis Template

**Participant:** [First name, age range, role]
**Date:** [YYYY-MM-DD]
**Duration:** [X minutes]

---

### Top Quote
[One sentence, verbatim, that captures their biggest pain or aha moment]

### Pain Points (ranked by emotional intensity)
1. [Most intense — they used strong language or a specific number]
2. [Second pain]
3. [Third pain]

### Behaviors & Workarounds
- [What they currently do instead of using your product]
- [Any tools or hacks they built themselves]

### Aha Moment / Bright Spot
[A moment where they described something working well — even if it
 wasn't your product]

### One Thing to Fix First
[If you could only change one thing based on this interview, what
 would it be and why?]

### Quotes to Keep
- "[verbatim quote 1]"
- "[verbatim quote 2]"
- "[verbatim quote 3]"

After 5 interviews, copy all five synthesis docs into one file and look for patterns. The pain points that appear in 3 out of 5 interviews are your roadmap.

🎉 You've just run a complete user interview — with a recording, a script, and a synthesis you can share in Slack right now. That's more user insight than most teams collect in a quarter.

🎁 Bonus

  • Run a "Diary Study" lite: Ask your participant to send you a voice memo the next time the problem happens in real life. You get in-the-moment data, not recall.
  • Use Otter.ai for auto-transcription: Drop your recorded audio file into Otter.ai (free tier available) and get a searchable transcript in minutes. Search for the word "frustrated" or "always" to find the best quotes fast.
  • Build a Question Bank: After 10 interviews, you'll know which 5 questions get the most valuable answers for your specific product. Document those and use them every time.

📚 Next Steps

🔗 Resources