Feedback Synthesis

Triggers

• feedback synthesis
• user feedback
• customer feedback
• sentiment analysis
• NPS analysis
• feedback categorization
• voice of customer
• feature request analysis
• customer satisfaction
• churn prediction
• survey analysis
• pain point identification
• user research synthesis
• review mining
• feedback dashboard
• product insights

Instructions

When activated, collect, analyze, and synthesize user feedback from multiple channels into actionable product insights.

Multi-Channel Collection

• Use web_search to monitor reviews, social media, and community forums for feedback.
• Aggregate feedback from surveys, interviews, support tickets, reviews, and social media.
• Categorize sources as proactive (surveys, interviews), reactive (tickets, reviews), passive (usage analytics), or community (forums, Discord, Reddit).

Feedback Processing Pipeline

1. Data Ingestion: Collect from multiple sources with API integration.
2. Cleaning & Normalization: Remove duplicates, standardize format, score data quality.
3. Sentiment Analysis: Detect emotions, score satisfaction, assess confidence.
4. Categorization: Tag themes, assign priority, classify impact.
5. Quality Assurance: Manual review, accuracy validation, bias checking.

Synthesis Methods

• Thematic Analysis: Identify patterns across feedback sources with statistical validation.
• Priority Scoring: Use RICE framework for multi-criteria decision analysis.
• Impact Assessment: Estimate business value with effort requirements and ROI calculation.
• User Journey Mapping: Integrate feedback into experience flows with pain point identification.

Quantitative Analysis

• Volume analysis by theme, source, and time period.
• Trend analysis with seasonality detection.
• Correlation studies: feedback themes vs. business metrics.
• Segmentation by user type, geography, platform, and cohort.
• NPS, CSAT, and CES score correlation with predictive modeling.

Qualitative Synthesis

• Compile representative verbatim quotes by theme.
• Develop user journey narratives with pain points and emotional mapping.
• Identify uncommon but critical edge-case feedback.
• Map emotional frustration and delight points.

Output Generation

• Use knowledge_write to store synthesized insights and trend data.
• Use goal_create to track feedback-driven improvement initiatives.
• Generate executive dashboards, product team reports, and customer success playbooks.

Deliverables

Executive Dashboards

• Real-time feedback sentiment and volume trends with alert systems.
• Top priority themes with business impact estimates and confidence intervals.
• Customer satisfaction KPIs with benchmarking and competitive comparison.

Product Team Reports

• Detailed feature request analysis with user stories and acceptance criteria.
• User journey pain points with improvement recommendations and effort estimates.
• A/B test hypothesis generation based on feedback themes.
• Development priority recommendations with supporting data.

Customer Success Playbooks

• Common issue resolution guides with response templates.
• Proactive outreach triggers for at-risk customer segments.
• Customer education content suggestions based on confusion points.

Success Metrics

• Processing Speed: < 24 hours for critical issues, real-time dashboard updates.
• Theme Accuracy: 90%+ validated by stakeholders with confidence scoring.
• Actionable Insights: 85% of synthesized feedback leads to measurable decisions.
• Satisfaction Correlation: Feedback insights improve NPS by 10+ points.
• Feature Prediction: 80% accuracy for feedback-driven feature success.
• Stakeholder Engagement: 95% of reports read and actioned within 1 week.
• Volume Growth: 25% increase in user engagement with feedback channels.
• Trend Accuracy: Early warning system for satisfaction drops with 90% precision.

Verify

• Every non-trivial claim in the output is paired with a source link, file path, or query result, not stated as a bare assertion
• Sources span at least 2-3 independent origins; single-source conclusions are flagged as such
• Counter-evidence or limitations are explicitly listed, not omitted to make the narrative tidier
• Numbers in the deliverable carry units, time windows, and an as-of date (e.g., '$1.2M ARR as of 2026-04-30')
• Direct quotes are verbatim and cite their location; paraphrases are marked as such
• Out-of-date or unreachable sources are noted in the bibliography rather than silently dropped