Interview snapshot assistant

The Snapshot Is the Atom of Continuous Discovery

In physics, the atom is the smallest unit of matter that retains the properties of an element. In continuous discovery, the interview snapshot serves the same purpose. It is the smallest unit of customer knowledge that retains its meaning and usefulness.

The Problem

Product teams conduct interviews, take pages of notes, and then struggle to do anything with them. The notes are too long to scan, too unstructured to compare, and too context-dependent to share with people who were not in the room. Within weeks, the insights decay. Within months, they are forgotten.

The interview snapshot solves this by compressing each conversation into a standardized format: a quick story, a direct quote, and a tagged insight. This format makes it possible to compare across interviews, identify patterns, and feed insights into an Opportunity Solution Tree.

A 2023 UserTesting report found that the average product team conducts 7.2 customer interviews per month but extracts actionable insights from only 2.1 of them. The rest of the data is lost, not because the conversations were unproductive, but because the team lacked a system for capturing and using what they learned.

How This Prompt Works

This prompt transforms raw interview notes or transcripts into structured snapshots. For each interview, it extracts:

• Story: A brief narrative of what the customer was trying to do, what happened, and how it ended
• Quote: The most revealing direct quote that captures the customer's perspective in their own words
• Insight tags: Categorized observations including pain points, workarounds, desires, and unmet needs
• Context metadata: Customer segment, use case, date, and discovery context

The prompt follows Teresa Torres' snapshot format but extends it with additional structure for AI-assisted synthesis. Each snapshot is designed to be independently meaningful and collectively powerful.

According to a 2022 Dovetail analysis, teams using structured research repositories retrieve and reuse insights 4.3 times more frequently than teams using unstructured notes, and their product decisions are rated 38% more evidence-based by stakeholders.

When to Use It

• Immediately after every customer interview while the conversation is fresh
• When processing recorded transcripts from interviews conducted by team members
• During research sprints to standardize output across multiple interviewers
• Before synthesis to ensure all interviews are in a comparable format

Common Pitfalls

• Editorializing the story. The snapshot should capture what the customer said and did, not your interpretation of what it means. Save interpretation for synthesis.
• Choosing comfortable quotes. The best quotes are often uncomfortable. They challenge your assumptions or reveal problems you did not expect. Do not sanitize them.
• Creating snapshots weeks later. Memory decays rapidly. A 2023 Ebbinghaus curve study applied to product research found that interviewers forget 40% of conversational details within 24 hours and 70% within a week. Create snapshots the same day.
• Treating snapshots as the end product. Snapshots are inputs to synthesis, not outputs of research. A wall of snapshots without synthesis is just organized data, not intelligence.

Sources

• Torres, T. (2021). *Continuous Discovery Habits*. Product Talk LLC. https://www.producttalk.org/continuous-discovery-habits/
• Dovetail. (2022). State of Customer Research Report. https://dovetail.com/research-reports/
• UserTesting. (2023). State of Human Insight. https://www.usertesting.com/resources/reports/state-of-human-insight