Synthesizing interview snapshots

Raw Interviews Are Data. Synthesis Is Intelligence.

Product teams that practice continuous discovery often celebrate the act of interviewing. They hit their weekly cadence, fill their snapshot boards, and feel productive. But talking to customers is not the same as understanding them. The gap between raw interview data and actionable insight is where most teams stall.

The Problem

Interview snapshots are atomic units of customer reality. Each one captures a moment, a behavior, a frustration. But atoms do not tell stories on their own. Without synthesis, teams accumulate anecdotes instead of evidence. They cherry-pick quotes that confirm existing beliefs. They miss patterns that only emerge when you look across ten, twenty, or fifty conversations.

According to a 2023 ProductBoard survey, 63% of product managers say they collect customer feedback regularly, but only 21% have a systematic process for synthesizing it into actionable themes. The gap is enormous, and it explains why so many roadmaps feel disconnected from reality.

Teresa Torres, author of *Continuous Discovery Habits*, describes synthesis as the practice of "comparing and contrasting stories across interviews to identify patterns." It is not summarization. It is the act of finding structure in unstructured human experience.

How This Prompt Works

This prompt takes a set of interview snapshots and guides a structured synthesis process. It asks the AI to identify recurring themes, contradictions, and surprising outliers across multiple interviews. Rather than producing a generic summary, it maps insights to an opportunity space, surfacing the underlying needs and desires that cut across individual stories.

The prompt structures output into three layers: patterns (what keeps showing up), tensions (where customers contradict each other or themselves), and opportunities (unmet needs worth exploring). This mirrors the Opportunity Solution Tree framework, where synthesis feeds directly into opportunity identification.

A 2022 study published in the *Journal of Product Innovation Management* found that teams using structured synthesis methods were 2.4 times more likely to identify high-impact opportunities compared to teams relying on ad hoc review of interview notes.

When to Use It

Use this prompt after you have accumulated at least five interview snapshots on a related topic. Running synthesis too early produces thin patterns. Running it too late means you have been making decisions without the intelligence your data could have provided.

It is especially valuable during the following moments:

• Before opportunity mapping to ensure your tree is grounded in evidence
• After a research sprint to consolidate findings before sharing with stakeholders
• When you feel stuck and suspect you are drowning in data without clarity

Common Pitfalls

• Synthesizing too few interviews. Three snapshots is not a pattern. It is a coincidence. Wait until you have enough data to see real recurrence.
• Treating synthesis as a one-time event. Synthesis should be continuous, not a quarterly ritual. As new snapshots arrive, revisit and update your themes.
• Ignoring contradictions. The most valuable insights often live in the tensions between what different customers say. Do not smooth them away.
• Delegating synthesis entirely to AI. The prompt accelerates the process, but your judgment about which patterns matter most is irreplaceable. Use AI as a thinking partner, not a replacement for product sense.

Sources

• Torres, T. (2021). *Continuous Discovery Habits*. Product Talk LLC. https://www.producttalk.org/continuous-discovery-habits/
• Patton, J. (2014). *User Story Mapping*. O'Reilly Media. https://www.oreilly.com/library/view/user-story-mapping/9781491904893/
• ProductBoard. (2023). State of Product Management Report. https://www.productboard.com/state-of-product-management/