A good discovery interview does not ask someone to approve your idea. It reconstructs real situations to understand goals, decisions, obstacles, and alternatives.
What an interview can—and cannot—establish
Qualitative interviews help you understand experiences and motivations, discover everyday language, reconstruct processes, and formulate better research questions. On their own, they do not provide a representative estimate of how many people will buy a product. GOV.UK recommends them, alongside observation and evidence reviews, to learn about users and problems during discovery [R02, R04].
Someone may sincerely describe what they would do and still act differently when actual money, time, or risk is involved. Questions about past experiences are therefore often more informative than hypothetical predictions about purchases. Later, the validation pillar will examine how to observe real decisions through experiments.
When the question shifts from understanding what happens to predicting behavior under an offer, consider choosing a different experiment and designing it with suitable participants and measures.
Step 1. Define the research question
Before drafting your interview guide, write something like: “We want to understand how small restaurants confirm reservations during busy periods and what happens when changes are needed.” “We want to know if people will like our app” is too broad. A useful research question can inform a decision: select a group to observe, investigate a barrier, or redefine the problem.
Break it down into topics: current routine, most recent incident, tools, people involved, consequences, workarounds, and changes made. GOV.UK's interview guidance recommends aligning topics with research questions and testing the guide beforehand [R04].
If you struggle to separate the real difficulty from the solution you imagine, start with identifying and defining the underlying problem.
Step 2. Recruit relevant and varied participants
Define verifiable inclusion criteria: someone who regularly takes reservations, someone responsible for resolving incidents, or a business with a particular type of operation. Where appropriate, include contrasting cases: one person reporting problems and another succeeding with the same method. Try not to build a sample exclusively from contacts who want to please you.
No universal interview count “validates” a market. GOV.UK mentions small ranges for qualitative rounds, but the appropriate number depends on the questions and segments; surveys and population estimates need different study designs [R03]. After a round, assess which themes recur, which new cases emerge, and which remain unexplored, without treating repetition as a statistical guarantee.
Step 3. Prepare a flexible guide, not a sales questionnaire
The interview guide might follow this sequence:
- Context. “Tell me about your role during the evening shift.”
- Current process. “How does a reservation normally come in, and what do you do next?”
- Recent incident. “Think about the last time a reservation changed at short notice. What happened?”
- Probing. “Who was involved? Which tools did you use? What did you do when the problem arose?”
- Consequences. “What was delayed or had to be repeated? Were there any lasting consequences?”
- Alternatives. “How did you try to prevent it from happening again? What worked and what did not?”
- Closing. “Is there anything important I did not ask about that I should understand?”
The “last time” phrasing helps ground the discussion in real events, but do not pressure someone into inventing a story if they cannot remember. You may request documents, walkthroughs, or examples without collecting unnecessary personal information.
Step 4. Avoid questions that suggest the answer
| Leading question | Better question for learning |
|---|---|
| “Doesn't it annoy you to waste so much time with a notebook?” | “How long does it take to record and change reservations? How do you know?” |
| “Would you pay for an app that saves you work?” | “Have you tried or paid for another way to manage this? What did you decide?” |
| “Don't you think automation would be better?” | “What do you value about your current method? What problems arise?” |
| “What features would the ideal app have?” | “What did you try to do the last time this difficulty arose?” |
An interview is not an interrogation. Listen, ask for examples, and allow silence when it feels natural. Resist defending your idea against objections: an objection may show that your interpretation was wrong. Nor should you promise a solution during the session just to obtain positive responses.
Step 5. Run the session with respect and consent
Explain who is conducting the research, why, how findings will be used, whether you will take notes or record audio, and that participation is voluntary. Obtain informed consent before collecting or recording data. GOV.UK describes these practices and recommends protecting personal information and sharing only necessary excerpts [R08, R09]. Applicable laws depend on the country and type of information; this guide does not replace legal review.
Consider accessibility: offer reasonable times, appropriate communication channels, and support where needed. Research quality should not depend on everyone having the same digital skills. If interviewing employees, avoid having a manager supervise a conversation that ought to be candid unless the study design and consent make that appropriate.
Step 6. Document statements, behavior, and context
Take verbatim notes of relevant phrases, but also record what was observed and what you are interpreting. A practical table:
| Record type | Example |
|---|---|
| Statement | “Last week two customers changed their booking time.” |
| Observation | The person checks three channels while handling a call. |
| Initial interpretation | Fragmentation may increase work during peak hours. |
| Open question | Does this also happen on other shifts? |
For each session, retain a participant code, recruitment criteria, context, date, permitted notes, and limitations. Avoid personally identifying details unless they are necessary. If you make recordings, define suitable storage and deletion practices [R09].
Step 7. Analyze several interviews, not just the most memorable one
Group incidents by tasks, obstacles, consequences, alternatives, and circumstances. Pay attention to situations that contradict the apparent pattern. Two restaurants may handle the same reservation volume, for instance, but only one faces problems: the difference may lie in responsibilities or channels, not volume.
Distinguish frequency within your interviews from frequency in the market. If six of eight interviewees mention a difficulty, you can report exactly that and explain how they were selected; you cannot claim that 75% of restaurants face the issue. GOV.UK's analysis guidance recommends synthesizing observations promptly and bringing together different perspectives to reduce bias [R07].
To avoid turning a handful of conversations into broad conclusions, explore how to evaluate evidence and bias.
Worked example: interviews for a repair service
You want to study why some homeowners delay household repairs. Instead of asking “Would you use an app to hire technicians?”, you interview people who recently needed repairs. One says they compared three quotes by phone; another hired someone through a recommendation; a third postponed the work because they could not receive a technician during working hours. The cases reveal different barriers: trust, comparing costs, and availability.
A reasonable interpretation is “There are at least three different situations that deserve further exploration.” An unsupported interpretation is “The market needs a platform with booking and price-comparison features.” The first opens up research; the second jumps to a solution without evidence.
A practice run before interviewing real participants
Conduct a trial interview with someone who does not share your professional context. Check whether questions are understandable, whether the person can describe actual incidents, and whether the length is reasonable. Reorder topics so the conversation flows naturally. During real fieldwork, note which questions steer answers, which topics recur, and when you should revise the guide.
Mistakes that undermine learning
Interviewing only supporters of the idea; treating purchase predictions as sales evidence; steering answers with positive adjectives; explaining features before hearing about experiences; overlooking context and consent; recording interpretations as quotations; mistaking unanimity in a biased sample for market consensus; and waiting weeks before analyzing findings.
What you should have when you finish
A tested interview guide, participant records and recruitment criteria, notes on specific experiences, a synthesis of patterns and contradictions, open questions, and explicit sampling limitations. The goal is to understand people and problems more accurately—not to collect favorable testimonials to show investors.
For more detail, see how to identify, organize, and prioritize customer needs.
Main sources: [R02] GOV.UK, discovery; [R03] research planning; [R04] interviews; [R06] recruitment; [R07] analysis; [R08] consent; [R09] privacy. Examples are invented for teaching purposes.
Bibliography and references
- [R02] GOV.UK — User research in discovery. https://www.gov.uk/service-manual/user-research/user-research-in-discovery — Usuarios, tareas actuales, problemas, métodos y resultados de discovery.
- [R04] GOV.UK — Using in-depth interviews. https://www.gov.uk/service-manual/user-research/using-in-depth-interviews — Guion, introducción, preguntas iniciales, seguimiento y registro.
- [R03] GOV.UK — Plan user research for your service. https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service — Preguntas de investigación, actividades, reclutamiento y planificación de rondas.
- [R08] GOV.UK — Getting informed consent for user research. https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research — Consentimiento y explicación de propósito/uso de los registros.
- [R09] GOV.UK — Managing user research data and participant privacy. https://www.gov.uk/service-manual/user-research/managing-user-research-data-participant-privacy — Gestión segura de datos y limitación de finalidad. La normativa explicada es británica; no debe atribuirse automáticamente a Perú ni a otros países.
- [R07] GOV.UK — Analyse a research session. https://www.gov.uk/service-manual/user-research/analyse-a-research-session — Separar datos de investigación, observar patrones, incorporar perspectivas.
- [R06] GOV.UK — Finding participants for user research. https://www.gov.uk/service-manual/user-research/find-user-research-participants — Criterios de reclutamiento y diversidad de participantes.