Customer Interview Questions

Why Most PMs Ask the Wrong Questions in Customer Interviews

Customer interviews are the backbone of product discovery, yet most product managers conduct them in ways that produce misleading data. The problem is not that teams skip interviews -- it is that they ask questions designed to confirm what they already believe.

According to Teresa Torres, author of *Continuous Discovery Habits*, fewer than 15% of product teams conduct weekly customer interviews. Of the teams that do interview, the majority ask leading questions, focus on feature requests, and mistake politeness for validation.

The Problem

The most common interview failure is asking customers what they want. Customers are experts on their problems but unreliable predictors of solutions. Henry Ford's apocryphal quote about faster horses captures a real dynamic: people frame needs in terms of existing solutions.

A study by the Product Development and Management Association found that products developed with strong voice-of-customer practices have a success rate of 75%, compared to 25% for those without. But "voice of customer" does not mean transcribing feature requests. It means uncovering the underlying needs, motivations, and constraints that drive behavior.

The second failure is asking hypothetical questions. "Would you use a feature that does X?" is not research -- it is a fantasy exercise. People consistently overestimate their future behavior. Nielsen Norman Group research shows that what users say and what users do differ by as much as 50% in usability studies.

How This Prompt Works

The Customer Interview Questions prompt generates questions rooted in past behavior rather than future predictions. You provide context about your product area, target users, and the assumptions you want to test.

The prompt produces questions organized by discovery goal: understanding current workflows, identifying pain points, exploring decision criteria, and mapping the emotional landscape around the problem space. Each question includes follow-up probes designed to move past surface-level answers.

It also flags common bias traps and suggests neutral phrasing alternatives for questions that might lead the respondent.

When to Use It

• Before building anything new to validate that the problem is real and worth solving
• When existing data is ambiguous and you need qualitative depth to interpret quantitative signals
• During continuous discovery as a template for weekly interview cadences
• When onboarding new PMs who have not developed interview instincts yet

Common Pitfalls

Asking about the future instead of the past. "Tell me about the last time you..." is almost always better than "Would you ever..." Past behavior is the strongest predictor of future behavior.

Interviewing only power users. Your happiest customers confirm your assumptions. Interview churned users, non-adopters, and people who evaluated and rejected your product.

Treating interviews as surveys. Do not read questions from a script without listening. The best insights come from follow-up questions that were not planned.

Sources

• Continuous Discovery Habits - Teresa Torres
• Voice of the Customer Best Practices - PDMA
• First Rule of Usability: Don't Listen to Users - Nielsen Norman Group