Story-Based Customer Interviews Uncover Much-Needed Context

Teresa Torres argues that product teams often misuse customer interviews by spending time evaluating solution ideas, which yields unreliable feedback because people overestimate their future behavior. Interviews are better used to uncover customers' goals, context, and unmet needs, ideally on a weekly cadence. Generic interview advice (open questions, avoid leading questions, don't ask about the future) is insufficient, and closed questions and self-reported frequency are unreliable. The article recommends story-based interviewing: grounding conversation in a specific recent instance of past behavior, which surfaces richer context and more accurate answers. The skill takes practice in guiding participants, recalling details, and active listening.

01Key takeaways

• Use interviews to understand customer goals, context, and unmet needs, not to validate solution ideas.
• Evaluate solutions through observed behavior and assumption tests rather than what people say they would do.
• Avoid closed questions and questions about future behavior; they produce shallow or aspirational answers.
• Ask about a specific recent instance (e.g., the last time they did X) to get grounded, reliable stories.
• Let participants do most of the talking and gently steer them back to specifics when they generalize.
• Use behavioral analytics to answer questions about frequency and quantity instead of asking participants to estimate them.

02Key sections

Don't use interviews to test solutions

Showing prototypes and asking whether people would use something produces polite, aspirational answers. Behavior, observed through assumption tests, is a more reliable signal.

Interviews reveal goals, context and needs

Weekly interviews provide the missing context behind feature requests and analytics, helping teams match needs to solutions.

Why generic interview advice falls short

Common tips are good but incomplete; a Netflix example shows how closed questions and self-reported frequency produce unreliable, shallow data.

Story-based interviewing

Asking about the last specific time someone did something elicits concrete stories with far more context and more trustworthy detail than general speculation.

Practicing the skill

Story collection requires letting participants talk, guiding them back from generalities to specifics, aiding memory, and strong active listening, which is best learned through practice.

03From the post

“Customer interviews are one of the most impactful activities a product team can do. But only if we use the right methods. An early customer interviewing mistake is to spend your interview time exploring your solution ideas. You might present a prototype and ask, “What do you think?” Or even,”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.