UX and research · Beginner · 16 min
Run your first user interview
By Padding · Updated 18 Nov 2026
Any video call tool that can record, a document editor and a timer · November 2026
You will run a 45-minute one-to-one interview with a note-taker beside you and finish with a recording, a page of structured notes and a five-line debrief written within the hour.
On this page
A first interview usually goes wrong in one of two ways. The interviewer reads the guide from top to bottom like a survey and gets polite, general answers. Or the conversation is good, but nobody wrote anything usable down, and a week later the team remembers one quote and a feeling. Neither gives you anything to synthesise.
This tutorial covers the session itself and the hour after it. You run the interview with a second person taking notes, so you can listen instead of type. You agree consent on the recording, use your guide as a map rather than a script, and dig for real stories by asking about the last time something happened. Then you close properly and write a short debrief while the session is still fresh.
The running example is a small team building an app that helps people in shared houses split bills. Their research question is: "How do housemates decide who pays for what, and where does it break down?" The participant is Ada, who has lived in three shared houses. Swap in your own product, question and participant.
If you do not have a guide yet, write one first with Write an interview guide without leading questions.
Step 1 · Set up the notes template and roles
Make a copy of the template below in a shared document, one copy per session. Name it with the date and a participant code, not their full name, for example 2026-11-20 P03 notes. Codes keep names out of documents that get passed around later.
Session: P03 · 2026-11-20 · 45 min
Interviewer: Note-taker:
Consent to record: yes / no (time noted: __:__)
Context (who they are, in their words)
-
Timeline of notes
[mm:ss] Q / observation / quote
-
Stories (one block per "last time" story)
Trigger:
What they did, step by step:
Who else was involved:
Workarounds or tools:
How it ended / how they felt:
Surprises (things we did not expect)
-
Follow-ups we did not get to
-Agree roles before the call. The interviewer asks the questions and watches the person. The note-taker types, keeps the time and stays silent until the end, when they get one turn to ask a question. The note-taker writes quotes word for word in quotation marks and their own observations without quotation marks, so nobody later mistakes a paraphrase for something the participant said. Each note starts with the minute mark from the timer, which makes it quick to find the moment in the recording.
Check it worked
Your session document exists, is named with a date and participant code, contains every heading from the template, and has both names filled in at the top. Your note-taker can tell you, without looking, the two rules: quotes in quotation marks, and a minute mark on every line.
Step 2 · Open the session and agree consent
Join five minutes early, test that recording works, and keep it off until the participant agrees. Open with three things, in your own words:
- Who you both are, and that the note-taker will mostly be quiet.
- What the session is for, framed around them, not the product: "We're trying to understand how people in shared houses sort out bills. There are no right answers, and you can't say anything wrong."
- What happens to the recording and notes: who sees them, how long you keep them, and that they can stop at any time or skip any question.
Then ask directly: "Is it OK if we record this?" Wait for a clear yes before you press record. Once recording, ask again briefly so the agreement is on the recording: "Just to confirm on the recording, you're happy for us to record?" If your organisation has a written consent form, make sure it was signed before the session; the spoken check does not replace it.
If the person says no to recording, carry on without it. The note-taker's notes become the record, so they should write more quotes and fewer summaries.
Start with an easy warm-up about them, not the topic: "Tell me a bit about where you live at the moment and who with." It gets them talking and gives you context for everything after.
Check it worked
The consent line in your notes reads "yes" or "no" with a time next to it. If you recorded, the first minute of the recording contains the participant saying yes. The "Context" section has two or three lines in the participant's own words.
Step 3 · Use the guide as a map, not a script
Keep the guide open but do not read it out in order. Your guide has a few main topics. Your job is to cover each topic, in whatever order the conversation reaches them, and to spend most of the time where the participant has real experience.
Practical habits that help:
- Tick a topic off in the guide when it has been covered, even if the participant got there before you asked.
- When the participant jumps ahead to a later topic, follow them. Go back to the skipped one later with a bridge: "Earlier you mentioned the electricity bill. Can we go back to that?"
- Watch the time. With 45 minutes, plan roughly 5 for the opening, 30 for the main topics and 10 for closing. If you are at minute 25 with two main topics left, choose the one closest to your research question and drop the other.
- Ask one question at a time. "How do you split bills and what app do you use?" gets an answer to the second half only.
Check it worked
At the end of the session, your guide shows ticks next to the topics you covered and a mark next to any you skipped on purpose. The note-taker's timeline shows topics in the order they came up, which may differ from the guide. If it matches the guide exactly and every answer is short, you were probably reading it out as a script.
Step 4 · Ask for the last time it happened
General questions get general answers. "How do you usually split bills?" gets "Oh, we just use a spreadsheet, it's fine." That answer is a summary the participant has made up on the spot, and it smooths over the problems you are looking for.
Ask about one specific, recent occasion instead:
"Tell me about the last time a bill came in that the house had to share."
Then walk through it with them, in order. Useful follow-ups:
- "What happened first?" and "Then what?"
- "Who else was involved?"
- "Where were you when you did that?" or "What did you have open on your phone?"
- "You said it was annoying. What made it annoying, that time?"
- "What did you do about it?"
Take Ada's story. Asked about the last bill, she describes the broadband bill arriving in one housemate's name, that housemate posting a screenshot in the group chat, two people paying straight away, and one person still owing money three weeks later. Ada ended up paying the gap herself to avoid an argument. None of that came out of "How do you usually split bills?", where she said it was "fine".
Avoid asking people to predict the future or design for you: "Would you use a feature that reminds people to pay?" Almost everyone says yes, and it tells you nothing. If a feature idea comes up, ask about the past instead: "Have you ever tried to remind someone? What did you do?"
The note-taker fills in one "Stories" block per specific occasion: trigger, steps, people, workarounds, how it ended.
Check it worked
Your notes contain at least two filled-in story blocks, each about one particular occasion with a rough date ("about three weeks ago", "last month"), not a general habit. Read through the timeline: most lines describe things the participant did, not opinions about what they would like.
Step 5 · Leave silence and handle the awkward moments
After the participant finishes an answer, wait. Count to five in your head before you say anything. People often add the most useful detail after a pause, because they fill the gap: "...actually, the thing that really gets me is..." First-time interviewers rush to the next question and cut this off.
Other habits for the moments that feel awkward:
- Repeat their words back. If Ada says "it gets messy", say "Messy?" and wait. You get her meaning, not yours.
- Do not defend the product or correct them. If they get something wrong about how the app works, note it; it is a finding, not a mistake to fix.
- Bring a ramble back gently. "That's useful. I want to make sure we get to the bit about moving out, so can I take you back there?"
- Short answers. Switch from "what" to "show me" or "talk me through": "Could you talk me through what you'd see on your phone at that point?"
- The person gets upset. Money in shared houses can be a sore subject. Offer to skip the topic or take a break, and mean it. The research question is never worth more than the person.
The note-taker marks long pauses and moments of strong feeling in the timeline, for example [22:10] (long pause) "honestly, I just paid it".
Check it worked
Your timeline has at least one line where a useful detail came after a pause or a repeated word; mark it with an asterisk. Listen to two minutes of the recording around that point: you should hear yourself waiting, not filling the silence.
Step 6 · Close the session
Start closing about ten minutes before the end. Do not stop abruptly when the clock runs out.
- Ask a broad last question: "Is there anything about sorting out bills that we haven't talked about but you think we should know?" This often brings up something you did not know to ask.
- Give the note-taker their one turn: "Is there anything you'd like to ask?" They pick the gap they noticed while writing.
- Thank the participant, and say what happens next and when they will receive any thank-you payment or voucher you promised.
- Stop the recording, then say goodbye. Keep the recording running until after your thanks, but stop it before casual chat at the door, which the person has not agreed to share.
Check it worked
The recording file is saved in the agreed place and named with the same date and participant code as the notes. The "Follow-ups we did not get to" section has any topics you dropped. If you promised a payment or voucher, there is a line in your notes or calendar saying when it will be sent.
Step 7 · Write the debrief within the hour
Book 20 minutes straight after the session with your note-taker. Memory of tone, hesitation and body language fades within hours, and by the next interview it blends with the previous one.
First, the note-taker tidies the notes for ten minutes: fill gaps, fix typos in quotes, and make sure every story block is complete. Do not rewrite or interpret yet.
Then write the debrief together at the top of the notes document. Five lines, no more:
Debrief P03 · written 2026-11-20 15:10
1. Biggest thing we learned: Ada pays other people's shares herself to avoid conflict.
2. Best quote: "Honestly, I just paid it. Chasing Sam wasn't worth the atmosphere." [22:10]
3. What surprised us: the bill is always in one person's name, and that person carries the risk.
4. What contradicts what we believed: we assumed calculation was the hard part; it was chasing payment.
5. Change for the next session: ask about moving out earlier; we ran out of time.Line 4 matters most. If nothing contradicted your assumptions, write "Nothing contradicted our assumptions yet" rather than leaving it blank, and be suspicious of your questions.
Keep debriefs about this person. Do not write "users want reminders" from one interview. Patterns come later, when you put several sessions' notes side by side.
Check it worked
The top of your notes document has five numbered lines, a timestamp less than an hour after the session ended, and at least one quote with a minute mark you can find in the recording. Someone who missed the session can read the debrief in under a minute and tell you what Ada does when a housemate does not pay.
Next steps
You now have one interview's recording, notes and debrief. Run the remaining sessions with the same template, so every set of notes has the same shape, and change the guide only between sessions, not during them.
When you have four to six sessions, turn the notes into patterns with Build an affinity map from interview notes. To improve your questions before the next round, read Write an interview guide without leading questions. If you still need more people to talk to, see Recruit participants for user research.
Part of these paths
Related tutorials
- Write an interview guide without leading questionsYou will have a 45-minute interview guide built from your research questions, with a warm-up, story-based questions, follow-up prompts and a close, plus a list of leading questions you caught and rewrote.
- Build an affinity map from interview notesYou will turn the notes from five or six interviews into an affinity map of five to eight groups, each named as a finding and backed by notes from more than one participant.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials