Story-Based Customer Interview
Reconstruct one recent experience to reveal behavior, context, and unmet needs.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 99%
The Story-Based Customer Interview replaces a long question protocol with a reconstruction of one recent event. Begin with a prompt such as asking about the last time the customer used a streaming service, then situate them in that moment by asking where they were, who was present, and what triggered the behavior. Follow the timeline with simple prompts like what happened next, summarize what you heard, and probe any point of friction or choice. Because the customer is recalling what actually happened, the account is more reliable and nuanced than answers about preferences, intentions, or imagined future behavior. The interviewer can listen instead of planning the next scripted question, uncover needs the customer did not explicitly name, and leave with a vivid experience rather than a collection of disconnected facts.
Origin
Torres teaches this conversational method because she repeatedly sees product teams collect abstract facts and hypothetical opinions instead of the rich stories needed to identify opportunities.
Core principles
- 01Past behavior is more reliable than hypothetical intent.
- 02A specific story preserves the context and nuance behind an action.
- 03Curiosity and listening matter more than a long interview script.
- 04Following the timeline reveals needs the customer may not recognize.
- 05Depth in one story creates more value than shallow coverage of many stories.
How to run it
- 1
Choose a recent event
Ask the customer to describe the last time they had the experience you want to understand. Anchor the interview in a real event rather than a general preference.
Pro tip Use one broad opening question and let the customer's account determine the follow-ups.
Watch out Questions about what someone usually does can produce a fast answer that does not match behavior.
- 2
Set the scene
Help the customer return to the moment by asking where they were, who they were with, and what was happening. Capture the trigger that started the experience.
Pro tip Repeat concrete details back to the customer to reinforce the shared scene.
Watch out Do not rush past context in order to reach the product interaction.
- 3
Follow the timeline
Ask what happened next and continue through the sequence. Let each answer create the next question instead of returning to a fixed list.
Pro tip Use short prompts so the customer, not the interviewer, does most of the talking.
Watch out Thinking ahead to the next prepared question causes the interviewer to miss useful details.
- 4
Probe meaningful moments
Slow down around friction, choices, workarounds, and surprises. Ask what the customer considered and what happened when the experience did not go smoothly.
Pro tip Treat an abandoned path or failed attempt as a place to investigate, not a detail to skip.
Watch out Moving quickly to a second story can discard the richest part of the first one.
- 5
Summarize and clarify
Summarize the sequence you heard to show that you are listening and to return the customer to a point that needs more detail. Ask for corrections before interpreting the story.
Pro tip Use the summary to reopen a precise moment rather than to close the topic.
Watch out Do not replace the customer's account with your own explanation of why they acted.
- 6
Extract behavioral opportunities
Review the story for unmet needs, pain points, and desires. Frame each opportunity around what occurred, not what the customer says they might do later.
Pro tip Look for needs revealed by tolerated mediocrity or a workaround the customer considers normal.
Watch out Intentions, opinions, and explanations of why behavior occurs are less reliable than the behavior itself.
In the wild
Torres asks Lenny about the last time he watched something. He recalls sitting on his couch at about eight o'clock, opening Netflix, finding nothing, opening Prime, finding nothing, and then remembering Obi-Wan Kenobi on Disney Plus. Instead of moving to another topic, Torres shows how each step can be explored: what he saw, what failed to resonate, what he considered, and why he changed services.
→ A simple timeline exposes multiple search and selection frictions that a general question about preferred shows would miss.
Common mistakes
Reading a 50-question protocol
A rigid question list makes the conversation unnatural and diverts attention from what the customer is saying.
Asking about future behavior
What a customer says they would do is unreliable. Ground the interview in a specific past action instead.
Collecting shallow stories
Starting another story as soon as the basic sequence is clear skips the friction and choices where opportunities emerge.
Is it for you?
Best for
Product teams investigating how customers currently navigate an experience and where meaningful friction occurs.
Not ideal for
Research that requires statistically representative measurement rather than deep qualitative understanding.
From the episode
Teresa Torres on how to interview customers, automating continuous discovery, the opportunity solution tree framework, making the case for user research, common interviewing mistakes, and much more