Purpose
Interviews generate enormous amounts of raw information, but most of it fades within hours. The interview snapshot forces you to distill a conversation into a single, shareable artifact while memory is fresh. It creates a consistent format the whole team can scan, reference during synthesis, and map onto an opportunity solution tree.
When to Use
- Immediately after every discovery interview (within 30 minutes).
- When multiple team members conduct interviews and need a common format for comparison.
- As input to affinity diagramming or experience mapping sessions.
- When you need to share interview findings with stakeholders who were not present.
Steps
-
Block 15 minutes right after the interview. Do not schedule back-to-back interviews. The snapshot must be written while the conversation is vivid.
-
Fill in participant context. Record the participant's role, company size or segment, and how they were recruited. Include any screener criteria they matched. Keep this to two or three lines.
-
Write the top three insights. State each insight as a declarative sentence that captures a behavior, belief, or constraint you observed. Prioritize surprises and things that challenge your assumptions over confirmations.
-
Capture two to four direct quotes. Select verbatim quotes that are vivid, specific, and illustrative. Quotes carry emotional weight that summaries cannot replicate and are invaluable during stakeholder presentations.
-
List pain points and workarounds. Note specific moments of friction the participant described and any improvised solutions they use today. These map directly to opportunities.
-
Identify potential opportunities. Frame each as an unmet need, not a feature idea. Use the format: "[Participant type] needs a way to [outcome] because [reason]." These feed into your opportunity solution tree.
-
Note open questions. Record anything you want to follow up on in future interviews or anything that contradicts previous snapshots. These guide your next round of conversations.
-
Share with the product trio. Post the snapshot where your team can see it the same day. The value of snapshots multiplies when the whole trio reads them and spots cross-interview patterns.
Tips
- Use a template. Create a reusable one-page template with fixed sections so every snapshot has the same structure. This makes cross-interview comparison dramatically easier and removes the friction of deciding what to write.
- Insights are not data points. An insight is an interpretation: "Enterprise buyers evaluate three tools simultaneously before any internal pitch" is an insight. "Participant mentioned looking at competitors" is just a data point. Push yourself to the interpretation layer.
- One page maximum. If the snapshot exceeds one page, you are summarizing too much of the conversation instead of distilling it. Cut ruthlessly; the recording or transcript is your backup if you need details later.
Source
Torres, T. Continuous Discovery Habits (interview snapshot format and integration with opportunity solution trees).
