User Interview Guide

The Interview Is the Most Powerful PM Skill Nobody Teaches

Ask a product manager about their most important skills and you will hear about prioritization frameworks, stakeholder management, and data analysis. Rarely will someone mention interviewing. Yet the quality of every product decision downstream depends on the quality of the customer understanding upstream, and that understanding comes primarily from conversations with real people.

The gap between what product teams think they know about customers and what they actually know is enormous. According to a 2023 study by UserTesting, 73% of product teams say they understand their customers well, but only 35% of customers agree. A CB Insights analysis of startup post-mortems found that 42% of startups fail because they build products that do not address a real market need, the single most common cause of failure. These are not data problems. They are conversation problems.

The Problem

Most product managers have never been formally trained in interview technique. They learn by doing, which means they learn by making the same mistakes:

• Asking leading questions that confirm existing hypotheses rather than challenging them
• Talking more than listening, often pitching their solution before understanding the problem
• Focusing on opinions and predictions rather than actual past behavior
• Interviewing the wrong people, typically the loudest customers rather than the most representative

The result is research that feels productive but produces unreliable insights. Teams walk out of interviews feeling validated when they should feel challenged. The interview is not a sales call. It is an investigation.

How This Prompt Works

The User Interview Guide prompt helps you design and execute effective customer interviews:

• Research objective definition to ensure every interview serves a clear purpose
• Participant screening criteria to find the right people to talk to
• Interview script with open-ended questions structured around past behavior, not hypothetical futures
• Probing techniques for going deeper when you hear something interesting
• Analysis framework for synthesizing insights across multiple interviews

You provide your product context and research questions, and the prompt produces a complete interview guide ready to use.

When to Use It

• At the start of a new product initiative when assumptions need validation
• When quantitative data shows a pattern but you do not understand the cause
• When preparing for a discovery sprint and you need to maximize learning per conversation
• When onboarding new team members who will be conducting customer research

Common Pitfalls

• Asking "Would you use this?" instead of "Tell me about the last time you dealt with this problem." Future-oriented questions produce unreliable answers. Past behavior is the best predictor of future behavior.
• Interviewing too few people. Five interviews will reveal patterns. Two will mislead you. Plan for eight to twelve per research question.
• Recording without analyzing. Raw transcripts are not insights. You need a structured process for identifying patterns across interviews.
• Treating interviews as the only research method. Interviews reveal the "why" but not the "how many." Pair qualitative research with quantitative validation.

Sources

• The Mom Test by Rob Fitzpatrick is the essential guide to asking questions that customers cannot lie to you about.
• UserTesting: The State of Customer Understanding provides data on the gap between perceived and actual customer understanding.
• CB Insights: Top Reasons Startups Fail documents the consequences of building without adequate customer research.