Feedback Synthesizer

---
name: feedback-synthesizer
description: "Use when an org role acts as feedback synthesizer and must turn interviews, surveys, tickets and reviews into evidenced themes and prioritized recommendations."
tags: ["product","customer-research","ux"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Feedback Synthesizer — Best Practices

## Focus
Turns raw, scattered user feedback (interviews, surveys, support tickets, reviews) into actionable themes and recommendations — the bridge between "we collected data" and "here's what to do about it."

## Best practices
- Separate analysis from synthesis explicitly: analysis breaks data into parts and finds patterns; synthesis combines those patterns into insights and recommendations. Don't skip straight to conclusions.
- Use thematic analysis for textual/qualitative data: read everything first, code short labels on similar fragments, then group codes into larger themes.
- For each theme, document what's happening, who it affects, where in the experience it shows up, and attach 1-3 concrete verbatim examples as evidence — themes without evidence aren't trustworthy.
- Triangulate across sources (interviews + support tickets + survey text + reviews) before treating a theme as real — a pattern that only shows up in one channel is weaker signal.
- Choose the analysis method and framework before sessions/collection begins, and align the team on it, so synthesis doesn't turn into ad hoc opinion.
- Quantify theme frequency and severity where possible ("18 of 40 interviews," "top support category") so prioritization discussions have a number to argue with.
- Deliver synthesis as recommendations tied to themes, not just a list of quotes — the output should answer "so what do we do."

## Common pitfalls
- Cherry-picking a few vivid quotes that confirm an existing hypothesis instead of coding the full dataset.
- Conflating loud feedback (frequent complainers) with representative feedback (what most users actually experience).
- Presenting raw notes or transcripts as "synthesis" — no grouping, no themes, no recommendation.
- Ignoring the difference between what users say they want and the underlying problem revealed by their behavior/complaint.
- Losing traceability — a theme with no linked source evidence that can't be re-verified later.

## Tools & techniques
- Thematic coding: label → group into codes → group codes into themes → attach evidence.
- Data triangulation across qualitative sources to increase confidence in a theme before acting on it.
- Frequency/severity tagging per theme to feed directly into prioritization frameworks (e.g., RICE Reach/Impact inputs).
- Structured synthesis output: theme, affected segment, evidence, recommended action.