Structure your raw customer feedback into clear themes and actionable insights so you can make faster, more confident product decisions.
The template
Feedback Source & Volume
Note where the feedback came from and how many responses you're working with so you can assess signal strength.
Example: Post-onboarding email survey — 84 responses collected over 2 weeks via Typeform, targeting new users in their first 7 days.
Raw Themes Identified
List the recurring topics or complaints you spotted after reading through all responses, before any prioritization.
Example: Onboarding confusion (mentioned 31 times), missing integrations (19 times), slow dashboard load times (14 times), positive comments on support team (22 times).
Supporting Quotes
Pull one or two verbatim quotes per theme that best represent what users are actually saying in their own words.
Example: Onboarding confusion — "I had no idea what to do after I connected my first data source. There was no guidance at all." / "The setup checklist disappeared and I couldn't find it again."
Recommended Actions
For each theme, write one specific next step your team should take, including who owns it and a rough timeline.
Example: Onboarding confusion → Product team to redesign the post-connect empty state with a persistent checklist — target Q3 sprint. Integrations gap → Review top 5 requested tools and add to roadmap backlog by end of month.
How to use it
Collect and paste your raw responses Export your feedback from your survey tool, CRM, or support inbox and paste all responses into a single document before you begin reviewing.
Read through everything once without tagging Do a full read-through first to get a feel for the overall tone and the most common topics before you start categorizing anything.
Group responses into recurring themes Go back through the responses and assign each one to a theme, creating new theme labels as you go and tallying how often each appears.
Fill in the template and assign ownership Complete all four template sections, then share the output with your team and make sure each recommended action has a clear owner and deadline.
What it looks like filled in
Onboarding Friction
"I signed up and genuinely didn't know what to do next — I almost gave up on day one."
→ Redesign the post-signup empty state to include a step-by-step guided checklist with progress indicators.
Missing Integrations
"We use HubSpot for everything — the fact that it's not supported yet is a dealbreaker for our team."
→ Prioritize HubSpot and Slack integrations for the next development cycle based on frequency of request.
Reporting Lacks Depth
"The summary view is fine but I need to be able to filter by segment — right now I have to export everything to Excel."
→ Add segment-level filtering to the reporting dashboard and remove the need for manual CSV exports.
Why teams skip the template
Reading hundreds of responses takes hours Manually skimming through large volumes of open-ended feedback is time-consuming and makes it easy to miss patterns buried in the middle of your dataset.
Theme identification is inconsistently subjective Two people reading the same feedback will often group responses differently, making it hard to get a reliable or repeatable view of what your users actually care about.
The template goes stale the moment new feedback arrives Every new batch of responses means starting the manual process over again, so your insights are always lagging behind your actual user sentiment.
Analyze your feedback automatically — no template needed
