| name | feedback-synthesis |
| description | Synthesize community feedback into evidence-backed themes, frequency and severity context, affected segments, representative examples, product implications, and routing without turning loudness into priority. |
Community Feedback Synthesis
Use when conversations, posts, events, support-like questions, or member discussions need to become usable product or marketing evidence.
Procedure
- Define the review window, communities or channels, member segments, and decision audience.
- Capture feedback with source context, date, user goal, sentiment or impact, and whether it describes behavior, request, defect, confusion, or opinion.
- Group by underlying need or problem rather than identical phrasing or requested feature.
- Estimate recurrence carefully and distinguish broad patterns from a small number of highly active members repeating the same point.
- Preserve severity and strategic importance independently from frequency; a rare blocker can matter more than a common cosmetic preference.
- Identify affected segments, workflows, product versions, and recent changes that explain clusters.
- Include contradictory views and representative evidence instead of forcing consensus.
- Route findings to Product, Support, Marketing, or another owner with confidence, evidence, and recommended follow-up research where needed.
Decision rules
- Community volume is not a representative population sample by default.
- Synthesize the need beneath requested solutions.
- Repeated posts from one person are not repeated independent evidence.
- Preserve high-consequence outliers.
Quality gate
The synthesis is ready when themes trace to source evidence, recurrence and member concentration are visible, severity and frequency are separate, conflicting signals remain intact, and each material finding has the right receiving owner or a defined research gap.
