Before building a protection-related product, find out what people are already trying to protect and how they handle the work today. That sounds obvious until the interview turns into a presentation. A founder explains an idea, the participant says it sounds useful, and everyone leaves with very little evidence. A better conversation stays close to a recent event and follows the decisions the person actually made.
The aim of a first interview round is to learn where a useful product might belong. You are looking for circumstances, existing habits, frustrations, and the language people use. You are also looking for reasons the idea may be unnecessary. A working solution that customers already like is important evidence. It can save a team from building a more polished version of something nobody wants to replace.
Write a question the research can answer
“Would people use our protection app?” is too broad and too easy to answer politely. Try a question about an observable task: how do small retailers find the correct support information when a customer reports a product problem? Or how do outdoor furniture owners choose a cover size? Each question points toward a different participant and a different conversation.
Choose one primary question for the round and two or three supporting questions. For a cover retailer, the supporting questions might concern measurement, product comparison, and what happened when the cover arrived. Leave pricing, packaging, and every possible future category for later rounds unless they are necessary to understand the task. A focused conversation has room for the participant to surprise you.
The GOV.UK guide to in-depth interviews recommends open, neutral questions and a focus on real examples. Its practical advice includes testing the discussion guide before using it with participants. Treat that first rehearsal as a chance to remove leading language and discover which questions require more explanation than expected.
Recruit people with a recent example
Ask for participants who have completed the relevant task recently enough to remember details. Someone who bought a cover last month can describe the page they used and the dimensions they checked. Someone who may buy one next year can mainly describe an imagined decision. Both perspectives have uses, but they should not be mixed together as if they are the same kind of evidence.
For an initial round, schedule five conversations as a manageable starting point. That number is a planning choice, not a claim of statistical completeness. Include meaningful differences in circumstances, such as a first-time buyer and a repeat buyer, or a team with a shared system and a team relying on email. Record those differences so a pattern does not get mistaken for a universal finding.
Explain what the conversation is about, how notes will be used, and whether you want to record it. Let the participant decline recording. Avoid collecting sensitive documents when a description or redacted example will answer the question. For interviews touching insurance or personal difficulties, keep the scope on the service experience and avoid asking the participant to disclose information the research does not need.
Use a simple conversation sequence
Begin with context: “Tell me a little about the equipment you were buying the cover for.” Then move to the event: “Think about the last time you bought one. What made you start looking?” Follow the sequence from trigger to search, comparison, purchase, arrival, and use. Ask what happened next before asking what the person thought about the whole experience.
Useful follow-ups include “What did you do at that point?”, “What information were you looking for?”, and “Can you show me the kind of thing you mean?” If the participant says a guide was confusing, ask which part and what they did to resolve it. A concrete example of measuring the wrong edge is more useful than a general statement that shopping should be easier.
Ask about the alternatives they considered. Did they ask a friend, call a retailer, use a product manual, or abandon the purchase? Find out what made an alternative acceptable. People often tolerate an awkward step because it is familiar, inexpensive, or backed by a person they trust. A new product must account for those benefits, not merely point out that the existing process has several steps.
Keep the idea out of the first half
It is tempting to show a prototype as soon as a participant mentions a problem. Wait until you have understood the current behavior. Once a person sees your proposed solution, their answers may start following its categories. You can lose the chance to hear how they would describe the work on their own.
If you do show a concept, separate that part of the session clearly. Ask the participant to complete a realistic task rather than rate the design. For example, give them a chair's measurements and ask which cover they would choose. Observe where they look and what they misunderstand. Avoid rescuing them immediately. A moment of uncertainty may reveal the exact instruction the product is missing.
Do not ask whether they love the name or would recommend a product they have never used. Ask what they believe the service does, who they think it is for, and what they expect to happen after the main action. Those answers can reveal a mismatch between the presentation and the offer without inviting a round of polite compliments.
Turn notes into decisions
After each session, separate what happened from what you think it means. “Participant measured the chair arms twice” is an observation. “The diagram makes the width unclear” is an interpretation. “Add arrows to the widest points” is a proposed response. Keeping those layers separate makes it easier for the team to challenge a solution without dismissing the participant's experience.
Build a small findings table with the situation, observed difficulty, current workaround, and open question. Include evidence that contradicts the initial idea. Perhaps experienced buyers never use a fit guide because they reorder a known model. That may suggest the guide should focus on first-time buyers while the repeat purchase route stays very short.
Discuss findings with the people who will make product and service decisions. A support lead may recognize a recurring issue. A supplier may explain why a seemingly simple change affects production. Use the conversation to choose the next uncertainty to investigate, rather than turning every observation into a feature request.
An example of a useful next step
Suppose three participants struggled to decide whether dimensions referred to the furniture or the finished cover. One called support, one guessed correctly, and one bought the wrong size. The next step could be a revised diagram with a plain explanation, tested with new participants. The research does not yet justify a whole new shopping platform. It points to a specific change that can be evaluated.
Keep a short record of the decision, its evidence, and what would cause you to reconsider. Schedule the next round around the unresolved question. The GOV.UK user research collection includes guidance on planning, consent, analysis, and sharing findings if the team needs to develop a more consistent practice.
A productive first round ends with better questions and a smaller, clearer experiment. Book the conversations, rehearse the guide, and leave enough time between sessions to review what you heard. The product can wait a few days while you learn which part of the customer's week deserves your attention.