Synthesize feedback for customer interviews
 August 1, 2025 | Career, Product Discovery

Synthesize feedback for customer interviews

Keep learning clear, actionable, and in front of the trio.

Rushing past synthesis is like ignoring the map before setting out — you’ll wander and get lost, and not deliver.

— Kristy Sullivan

What does it mean to synthesize?

It’s not a one-time step. It’s not something you save for “later.” In Continuous Discovery Habits, Teresa Torres makes it clear: synthesis is something you do continuously, right alongside your customer conversations. Instead of batching insights after you finish research, you synthesize as you go.

One of her most useful tools is the interview snapshot. It’s a one-page template you fill out right after an interview. Not a transcript. Not a write-up. A quick summary while your memory’s fresh. These snapshots become your running archive of customer knowledge. She recommends keeping them visual, quotes, pictures, and even little maps of the customer’s experience, to make their story stick with the team.

Here’s how to get better at it.

Make it a habit

Synthesis works best when it’s lightweight and continuous. You’re not producing a giant report. You’re capturing what matters, while it’s fresh. Here’s what helps:

  • Write down unusual or unexpected behaviors, even if they seem rare.
  • Sketch a quick story of what happened, beginning, middle, and end.
  • Capture opportunities as pain points, needs, or desires. Not features.
  • If someone asks for a feature, ask why, then write down what they’re trying to solve.
  • Use the customer’s actual words to frame each opportunity. Avoid rewriting it in your language.

The point isn’t to document everything. It’s to capture what’s important — clear, actionable, and in the customer’s voice.

What about affinity mapping?

You don’t have to stop affinity mapping. Just don’t start there.

In fact, Torres names three (3) big risks when teams rely only on traditional affinity maps:

  • You batch your learning, so insights get delayed.
  • You lose structure, which makes it hard to trace quotes back to people.
  • You have a bias toward recency, giving more weight to the last interview you did.

Affinity maps aren’t bad. But they’re not enough on their own. The best approach? Pair snapshots with affinity mapping so you build a steady stream of insight.

When you do use an affinity map, use it well.

Why it helps

Customer feedback is messy. You’ve got sticky notes, scribbles, Slack threads, and gut feelings. Affinity mapping helps you cut through the noise.

It helps you:

  • Spot patterns across interviews.
  • Align as a trio so everyone hears the same thing.
  • Tell the difference between real signals and one-off noise.
  • Build empathy by reading actual quotes together.
  • Prepare for opportunity mapping and prioritization.

When you skip it, you risk chasing whatever sounds loudest or newest. And that’s how teams miss the mark. Affinity maps help you ground your thinking in real patterns.

How to do it

  • Pull the highlights from your interview snapshots.
  • Drop them into Miro, FigJam, or whatever tool your team uses.
  • Turn each observation into a short sticky note.
  • Place notes along the customer journey.
  • Group similar ideas together under each phase.
  • Label each group with a theme, in plain language.
  • Mark any themes that show up more than once with a tally.
  • Talk through each theme as a team. Don’t skip this step.

Use comments to ask questions like: Does this feel true? Are we missing something?

Don’t rush the mapping. Don’t overdo it either. The goal is a shared view of which problems matter, and how often they show up.

From quote to opportunity

One common struggle: turning a customer quote into an actual opportunity.

That’s because many teams skip the middle step. They hear a quote and drop it straight onto an opportunity solution tree. But quotes are observations — not opportunities.

The difference

Observation = what you saw or heard

  • Users take 10 clicks to finish checkout.
  • Customers say they feel overwhelmed when signing up.

Insight = what you think it means

  • Checkout flow causes drop-off due to too many steps.
  • Sign-up form erodes trust by asking too much, too soon.

Observations tell you what happened. Insights explain why. You need both. But only insights lead to good opportunity framing.

Opportunities should always reflect a pain point, need, or desire. Not a feature. And not a vague quote. When in doubt, ask: What is this person struggling with? or What outcome are they hoping for?

Conclusion

Strong synthesis makes every part of the discovery better. You ask sharper questions. You spot patterns earlier. You spend less time chasing shiny ideas. And your team builds stronger conviction because they’re closer to the customer.

If your insights feel fuzzy or disconnected, look at your synthesis habits. That’s often where the breakdown starts. And the fix isn’t more process. It’s better habits: capture what matters, right away, in the customer’s voice.

This work isn’t about documenting everything. It’s about seeing clearly and acting confidently.

Take Action

  • Synthesize as you go, don’t wait until after a “research phase.”
  • Use interview snapshots to build customer memory over time.
  • Use an affinity map to find patterns, but pair it with your ongoing notes.
  • Distinguish observations from insights so you know what you’re acting on.
  • Frame opportunities as needs, pain points, or desires, never just features.