How to prepare customer research interviews for a product decision
Prepare customer research interviews around one product decision, recruit people with relevant experience, and write a neutral 30-minute interview guide.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a plan to prepare customer research interviews is
You prepare customer research interviews by choosing one decision the product team needs to make and writing a guide to gather evidence for it. A team choosing where to improve account setup could ask customers to walk through their last attempt to connect a data source. Their accounts can help the team decide which obstacle to investigate.
A user interview guide gives each conversation the same core prompts and leaves room to follow what a participant brings up. It defines who to recruit, what to ask, what to write down, and how to compare notes. Customer interview questions should bring out actions, constraints, and consequences in the participant's own words.
What it does for the business
- Choose which problem to work onGive your product team a concrete problem to investigate. An administrator waiting for approval from a teammate needs a different fix than one who hits an error they can resolve alone.
- Get more from recruiting timeUse interview slots for people who have lived through the workflow you need to understand. Direct your next round of recruiting toward the experiences you still need to hear about.
- Write a narrower product briefReal examples give designers and engineers a sequence of actions to work from, including where people asked for help or switched tools. Carry those constraints into a prototype and decide what to test before committing to development.
- Make research easier to use across teamsA shared note structure helps product, design, and support trace recommendations back to specific events. Teammates can see which findings depend on an unusual setup and which recur under different conditions.
How to build a plan to prepare customer research interviews, step by step
Name the decision and read the current evidence
Give the interview one uncertainty that could change a specific decision.
What to do
- Write the decision as a choice you can make. For account setup, you might choose between clarifying setup instructions and addressing delays when a teammate has to approve a connection. Record who will make the choice and when it comes up.
- Describe the activity in scope using a clear start and end. For example, start when an administrator first tries to connect a data source and end when the connection works or the administrator stops trying.
- Read the latest relevant support requests, feedback notes, and any previous research you can use. Record each source, the period it covers, and where the relevant observation appears. Check whether older evidence describes the same setup flow.
- Write one research question about the unresolved part of the choice. If the current evidence tells you where people stopped, use the interviews to understand what they did at that point and what kept them from continuing.
Why
A decision gives you a reason to keep, cut, or rewrite a prompt. Use interview time to learn what happened between the actions you can already see in a log or support ticket.
Define who can answer the question
The best participants have a relevant event they can describe in detail.
What to do
- Write down your research assumptions separately from what the sources show. A note that an administrator needed help is an observation. A belief that the setup instructions caused the delay is an explanation you can check.
- Use participant screening to confirm firsthand experience. Ask which part of the work the person did and when. Pick a recent period that fits how often people do the work and what they can realistically remember.
- Recruit for outcomes that can test your explanation. Include people who completed the task and people who paused or handed it off. Include the teammate who took over when that perspective matters to the decision and fits the research scope.
- Write explicit exclusions. Someone who has only watched a demo cannot describe a real setup attempt. Keep criteria tied to actions and responsibilities participants can report directly.
Why
A job title can hide differences in who does the work. Screening for recent actions gives you events to compare, and including different outcomes can reveal conditions that matter, such as who had permission to finish.
Write the guide around a recent event
A useful prompt helps someone remember what they did and what happened next.
What to do
- Draft an opening that explains the purpose in plain language and tells participants how you will take and use notes. Write a separate request for permission if you plan to record. Confirm the wording with your team and prepare to proceed with notes when recording is declined.
- Start the walkthrough with an invitation such as, "Tell me about the last time you tried to connect a data source." Ask what prompted the attempt, what the participant did first, what they saw, and what eventually happened.
- Keep neutral follow-up probes near the core prompts. Ask the participant to describe what they tried next, who they involved, or how they decided to stop. A prompt like "Describe what you expected at that point" leaves room for several explanations.
- Add a prompt for a counterexample. Ask the participant to recall another attempt that went differently and describe what changed. When they report a problem, find out what they did about it and whether they had to repeat that workaround.
- Assign a time budget. You can allow three minutes for the opening, twelve for the walkthrough, eight for follow-up, four for a counterexample, and three for the wrap-up. Give the participant time at the end to correct your recap.
Why
Someone who consulted a teammate during setup might have needed approval, help finding information, or reassurance before taking a step. The sequence of actions shows which explanation fits and helps the team choose a fix.
Check for bias and rehearse
A guide is ready when it can handle an answer that challenges the team's expectation.
What to do
- Ask a teammate to mark prompts that assume a problem, supply a cause, or combine several topics. Replace "Describe the confusing setup instructions" with "Describe what you saw when you started setup." Ask about confusion only after you hear what happened.
- Check each prompt against the decision. Keep the opening broad enough for a participant to remember the event, then narrow to the actions that bear on the choice. Move optional probes below the core prompts so an interviewer can skip them when time is short.
- Rehearse the opening and walkthrough with a teammate, including an uneventful example. Check that the sequence makes sense aloud, the time budget leaves room for follow-up, and the interviewer can locate each prompt without breaking the conversation.
- Check the guide against the sources. Label assumptions and make sure the prompts let people describe smooth attempts, abandoned attempts, and obstacles the team has overlooked.
Why
Even a short qualifier can tell participants what answer you expect. Reviewing the wording catches assumptions you make about the problem or its cause. A rehearsal shows whether you can cover the core prompts and still have time for the closing recap.
Plan the notes and hand off the guide
Keep the participant's account visible when you draw conclusions from it.
What to do
- Set up a note template with space for the participant's relevant role, the event, the sequence of actions, the outcome, and any missing detail. Keep direct quotes distinct from interpretations so you can revisit a claim after the session.
- Plan interview synthesis, the work of comparing evidence across sessions. Put each event alongside the conditions that mattered, such as access to a teammate or familiarity with the setup. Preserve examples that cut against a pattern you are considering.
- Tell the interviewer which prompts everyone should hear and which ones depend on the answers. Give the note taker the same guide. Agree on how you will handle a session in which the participant cannot recall a relevant event.
- Assign who will review the notes against the original decision and record what remains uncertain. Agree on what kind of account would put each option in contention and where you would need a follow-up, a usability check, or corroborating records.
Why
A synthesis plan helps you capture details while there is time to ask. Notes that preserve the setting and sequence let you tell whether two people faced the same problem or used similar words to describe different obstacles.
Common mistakes
- Starting with a broad topicA prompt about general satisfaction gives you little basis for deciding which part of account setup to improve.
- Recruiting whoever is freePeople without experience of the task can only speculate about what would happen.
- Reading the team's explanation into the promptA question that names the supposed cause can lead participants to echo it before describing the event.
- Skipping the smooth casesYou lose a chance to learn which conditions help people complete the same work.
- Writing impressions as quotesA teammate reviewing the notes may mistake your interpretation for something a participant said.
What a good result looks like
- One decision and one research question appear at the top of the guide.
- Eligibility depends on a concrete past action within a stated period.
- The walkthrough has neutral core prompts, follow-up probes, and a prompt for a different outcome.
- The opening covers permission, and the timing leaves room for a recap.
- The note template preserves evidence and gives the team a way to record counterexamples.
And then what? Using the result
- Recruit against the criteria and track which experiences still need representation before closing the schedule.
- Run the sessions and use the same core prompts so you can compare accounts of the workflow.
- Review the evidence with the decision owner and choose which problem to pursue or what to verify first.
- Turn the best-supported problem and its constraints into a product brief or a prototype task.
- Write down the reason for the decision and the observation that would make you revisit it.
When to run it
- Before choosing a product changeUse interviews when your team has plausible explanations for an issue and needs to understand what customers were doing when it happened.
- When a support pattern needs contextA ticket often starts at the point someone asks for help. The walkthrough can recover what led up to that point and how the person handled the problem afterward.
- When a workflow has several ownersRecruit for the relevant roles to see what gets passed between people, where responsibility changes, and which part of the process each person can explain.
Questions people ask
How do you prepare customer research interviews?
Choose one product decision, review current evidence, recruit for relevant past behavior, and draft a neutral guide around a recent event. Rehearse the guide and decide how to capture notes before you start.
What customer interview questions should you ask?
Ask the participant to describe a recent attempt, starting with what triggered it and ending with the outcome. Use the details in their account to ask about tools, other people, decisions, and workarounds that affected the result.
How do you recruit participants for customer research interviews?
Screen for people who recently did or attempted the work and can describe their own role. Include different outcomes that bear on the decision so your findings cover more than one version of the experience.
How do you avoid leading questions in customer interviews?
Use plain prompts that let people describe what happened before you name a problem or pitch a solution. Invite people to recall a time the same task went differently, then ask what conditions changed.
What goes in a 30-minute user interview guide?
Include a brief opening, a walkthrough of a recent event, neutral probes, a prompt for a counterexample, and a wrap-up. Add timing, draft consent and recording wording, and a template the note taker can use throughout.
Can you use customer research interviews to measure how common a problem is?
Use a separate data source to estimate how common a problem is. Define the customer group and check a suitable source such as representative survey responses or relevant usage records.
More jobs in Product
Prepare customer research interviews, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac