Conduct Product Discovery Interviews Without Leading People
Plan focused discovery interviews around recent behavior, concrete examples, and competing explanations instead of asking customers to endorse an idea.
Choose a question worth investigating
Define the uncertainty before recruiting participants. You might need to understand why new users abandon a setup process, how a team handles an exception, or whether a problem occurs often enough to matter. An interview is not a request for approval of your roadmap. Identify people with relevant experience and document recruitment limits so a convenient sample is not mistaken for the entire market.
Ask about a recent event
Invite the participant to walk through the last time the situation occurred. Ask what triggered it, what they tried, where they got stuck, and what happened next. “Would you use our automatic planner?” invites speculation and politeness. “Show me how you planned your last project” can reveal real constraints. Obtain appropriate consent before recording and follow the organization's research and data-handling practices.
Follow evidence, not your script
Use the guide to cover important topics, but ask neutral follow-ups when something unexpected appears. Separate what the participant said from your interpretation. If they describe a workaround, explore its cost and why it persists. Avoid pitching a solution in the middle of the interview; that can change later answers. Save concept feedback for a clearly separated activity with its own questions.
Synthesize patterns and exceptions
Group observations by problem or behavior, retaining examples that do not fit the dominant story. Do not turn a small interview sample into a market percentage. Compare findings with support records or product behavior where those sources are available and appropriate. Use stakeholder feedback triage to distinguish individual requests from recurring needs without dismissing important minority experiences.
Translate learning into the next test
State what you learned, how confident you are, and what remains uncertain. A useful result may be a narrower problem statement rather than a new feature. Choose the smallest next activity that can resolve the most consequential uncertainty. The experiment planning guide helps turn a discovery insight into a testable proposition with a decision attached.
Published by AgilePro.info under our Editorial Policy. Guidance is based on established delivery practice and is general information, not professional advice for a specific project.