Story-First Discovery Interview
Ask for the last real story, then adapt follow-ups to the evidence it reveals
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
The Story-First Discovery Interview opens with a concrete narrative prompt instead of an abstract request. With founders, Rajaram begins by asking for the company's founding story and listens for how the founders met, why they chose the problem, and whether their motivation reflects deep observation or a fashionable market. With customers, ask about the last time they performed the relevant activity rather than asking for their top three problems. The interviewer can keep a standard opening and a few recurring themes, but follow-ups should change with the story. Because people naturally remember actions and sequences, the method surfaces behavior, context, and authenticity while reducing rehearsed answers and freeing the interviewer to listen.
Origin
Rajaram described using 'tell me your founding story' as his standard opening with startup founders. He connected it to customer research, where asking about the last delivery or payment experience works better than asking customers to rank their problems.
Core principles
- 01People recall concrete events more reliably than abstract rankings
- 02Stories reveal motivation, sequence, relationships, and behavior together
- 03A stable opening question frees the interviewer to listen
- 04Follow-up questions should respond to evidence rather than a rigid script
How to run it
- 1
Frame a concrete prompt
Ask for a specific recent or origin event, such as the founding story or the last time the customer used a service. Avoid asking for generalized opinions first.
Pro tip Use 'tell me about the last time' to anchor recall in behavior.
Watch out Questions such as 'what are your top three problems?' invite invented rankings.
- 2
Listen for the sequence
Track who acted, what happened, what triggered each decision, and what changed. Note the difference between observed events and retrospective explanation.
Pro tip Keep the opening stable so your attention can stay on the answer.
- 3
Probe authentic motivation
Ask how the person encountered the problem and what they did before formalizing a solution. Look for immersion, direct observation, and costly action.
Watch out A polished market narrative may conceal shallow contact with the problem.
- 4
Adapt the follow-ups
Let the story determine the next question. Probe contradictions, missing transitions, and specific choices rather than forcing every conversation through a fixed list.
Pro tip Retain standard themes while varying the wording and order.
- 5
Record evidence, then reset
Capture concise notes about behavior and motivation, then clear attention for the next interview. Use the notes for comparison instead of carrying impressions between conversations.
Pro tip Write the evidence before writing the verdict.
In the wild
Rajaram asks founders how they met and how they came to the problem. He listens for whether they observed and immersed themselves in the space or adopted an idea after reading about a fashionable Web3, crypto, or NFT trend.
→ The story provides evidence about motivation and founder-problem fit beyond the pitch deck.
Instead of asking a customer to name their top three problems, ask about the last time they took a credit-card payment. The customer can recount the actual process, friction, and workarounds in sequence.
→ The interviewer gathers concrete behavioral evidence rather than an abstract wish list.
Common mistakes
Starting with abstract rankings
People often cannot reliably state their top problems, but they can describe what they recently did and experienced.
Following a rigid script
A fixed list can prevent the interviewer from probing the evidence and contradictions unique to the story.
Is it for you?
Best for
Investors evaluating founder authenticity and product teams conducting customer discovery.
Not ideal for
Structured compliance interviews that require every participant to answer identical closed questions.
From the episode
Gokul Rajaram on designing your product development process, when and how to hire your first PM, a playbook for hiring leaders, getting ahead in you career, how to get started angel investing, more