Customer Feedback Review

Purpose: Transform raw customer feedback into actionable product insights by separating signal from noise

How to run this meeting

Aggregate feedback into themes before the meeting, never during it. Walking through individual tickets, NPS responses, or customer quotes in real-time is the fastest way to make bad product decisions. One loud customer with an unusual use case can derail a room full of otherwise clear-thinking people. Do the aggregation work first: group feedback by theme, count volume, and weight by segment before anyone sits down.

Distinguish signal from noise with explicit criteria. Not all feedback is equal. A complaint from a customer in your ideal customer profile (ICP) who uses the product daily carries more weight than the same complaint from a free-tier user who logged in once. Before discussing any theme, answer: who said this, how many said it, and are they customers we want more of? This discipline prevents the product roadmap from being driven by squeaky wheels.

Connect themes to the roadmap rather than reacting to them individually. The output of this meeting should never be "let's build what the loudest customer asked for." It should be "theme X is appearing in 30 feedback sources, it maps to a gap in our roadmap, and here's how we should respond." The response might be building something, communicating better about something that already exists, or deciding the feedback reflects a use case outside your target market.

Before the meeting

• Feedback aggregated from all sources: CS tickets, NPS verbatims, sales call notes, user interviews, app store reviews, community forum posts
• Themes identified and named — aim for 5-8 themes, not 50 line items
• Each theme annotated with: volume, customer segment, and whether it's been raised before
• Existing roadmap items that relate to each theme are linked
• One person owns the pre-read (typically a PM or researcher) — not a committee

Meeting Details

• Date:
• Facilitator:
• Attendees:
• Duration: 60 minutes (monthly recommended)

---

Recent Feedback

Snapshot of raw feedback volume this period. The goal is a shared baseline, not discussion — save that for themes.

Period: March 1–March 14, 2025

---

Themes

Aggregated themes from all sources above. Each theme has a name, volume, and representative quote. These are your discussion items — not the individual tickets.

Theme 1: Notification overload (High volume, broad segment) Volume: 52 mentions across CS, NPS, and app store | Segments: All, concentrated in teams of 10+ Representative quote: "I've turned off all notifications because there's no way to filter what matters. Now I miss things I actually care about." — NPS respondent, 8/10 promoter Previously raised: Yes — 34 mentions last month, growing

Theme 2: Salesforce integration gap (Medium volume, enterprise segment) Volume: 23 mentions | Segments: Enterprise and mid-market exclusively Representative quote: "Our ops team lives in Salesforce. Asking them to check Stoa for action items isn't going to happen." — Sales call note, $45K ACV prospect Previously raised: Yes — growing consistently over 3 months

Theme 3: Timeline view confusion (Low volume, new users) Volume: 8 mentions | Segments: New users (<30 days), SMB Representative quote: "I couldn't figure out what the timeline was showing me vs. the roadmap view." — CS ticket Previously raised: No — new theme this month

Theme 4: Praise for AI summaries (Positive, broad segment) Volume: 31 mentions | Segments: Broad; concentrated in teams using the feature weekly Representative quote: "The AI summary after our Monday standup saves me 20 minutes of writing. It's become part of our workflow." — NPS respondent, 10/10 Previously raised: New this month — first full month since launch

Theme 5: Onboarding friction for enterprise (Medium volume, enterprise) Volume: 14 mentions | Segments: Enterprise, >50 users Representative quote: "Getting our whole team set up took two weeks. We needed a dedicated onboarding call, and there was nothing available." — User interview participant Previously raised: Yes — 9 mentions last month

---

Impact

For each theme, assess the business impact. This is where you separate the themes worth acting on from the ones worth monitoring.

---

Potential Product Changes

Concrete responses to high-priority themes. These are proposals, not decisions — evaluate against roadmap capacity and strategic fit.

Notification overload → Notification preferences (in progress) The notification preferences feature already in Q2 scope directly addresses this theme. The volume increase this month validates the prioritization. Recommendation: Accelerate if possible; communicate timeline to CS team so they can set expectations with frustrated customers.

Salesforce integration → In Q2 scope (just approved) Approved at the executive product review on March 14. Signal here is consistent with the decision. Recommendation: Close the feedback loop with enterprise customers who raised this — proactive outreach from CSM.

Enterprise onboarding friction → No current roadmap item This is a gap. The theme is growing and concentrated in enterprise — our highest-value segment. Options: (1) Dedicated onboarding tier for enterprise (service solution), (2) In-app guided setup for large team configurations (product solution), (3) Onboarding webinars (low-cost interim). Needs a decision.

AI summary praise → Reinforce, don't neglect Positive signal should influence roadmap just as negative signal does. The AI summary feature is becoming a retention and differentiation driver. Recommendation: Prioritize AI summary improvements in Q3; include in marketing and sales messaging.

---

Experiments

Small, low-cost tests that could generate signal to inform future decisions.

Experiment: CS canned response for notification complaints Hypothesis: If CS proactively tells notification-frustrated users about the upcoming preferences feature and offers a workaround (Slack DND), we can reduce churn while the feature ships. Owner: @alex (CS lead) | Cost: 1 day of CS team time | Signal: Churn rate in this segment over next 30 days

Experiment: Enterprise onboarding check-in call Hypothesis: A 30-minute call in week 1 of enterprise onboarding will improve 30-day retention and reduce onboarding-related tickets. Owner: @nina (CSM) | Cost: ~2 hours/week of CSM time | Signal: 30-day retention for cohort that receives vs. doesn't receive the call

---

Action Items

Follow-up

The PM who owns this meeting sends a summary to CS, sales, and design within 24 hours — specifically: which themes the team is acting on, which are being monitored, and which are out of scope with a brief rationale. CS benefits from knowing what's roadmapped so they can set accurate customer expectations. If a theme moves to the roadmap, add it to the product spec with the feedback volume as context for future team members.