1. Analysis Setup
Data source
[User feedback from in-app feedback, support messages, and open-ended survey responses]
Date range
[Example: Jan 1, 2026 – Jan 31, 2026]
Analyst name
[Example: Maya Chen]
Research question this analysis answers
[Example: What recurring product issues, requests, and moments of delight are users surfacing across feedback channels this month?]
2. Step 1 — Code Your Excerpts
Excerpt [1]
"Every time I click export on the weekly report it just spins forever and then dumps me back to the dashboard. I tried Chrome and Safari, same thing. Kind of stuck because my manager needs the CSV today."
bug report
missing data/export
slow performance
Excerpt [2]
"Love the new dashboard layout, but I genuinely cannot tell if 'archive' removes a customer forever or just hides them. I was too nervous to click it on a real account."
UX confusion
positive shoutout
Excerpt [3]
"We really need a way to export interview notes with timestamps. Right now I'm copy-pasting everything into Google Docs which feels very 2012."
feature request
missing data/export
Excerpt [4]
"Signed up today and got dropped straight into the app with no clue what to do first. I found the import button after like 10 minutes, but I still don't know what counts as a 'workspace' vs a 'project'."
onboarding issue
UX confusion
Excerpt [5]
"The search takes 8–10 seconds whenever I filter by tag, and half the time the page flashes blank before results come back. It's usable, but barely."
slow performance
bug report
Excerpt [6]
"Big shoutout to your support team — the transcript cleanup is way better than it was a month ago. This is the first time I didn't have to manually fix speaker labels."
positive shoutout
Excerpt [7]
"Can you please add a way to save custom views for each team? We keep rebuilding the same filters every morning and it's getting old fast."
feature request
Excerpt [8]
"I invited two teammates during setup and neither got the email. Then when I retried, one invite showed as sent and the other disappeared completely. Not a great first run for our team."
bug report
onboarding issue
Tip: Good codes are short, specific, and reusable. They capture what the excerpt is mainly about without repeating the whole quote or jumping too quickly to a broad conclusion.
3. Step 2 — Group Codes into Themes
Bugs & Reliability
Users are running into broken flows and inconsistent system behavior that reduce trust and block key tasks.
bug report · 4 excerpts
missing data/export · 2 excerpts
Feature Requests
Users are asking for workflow-improving capabilities that reduce manual work and repeated setup.
feature request · 2 excerpts
missing data/export · 2 excerpts
UX Friction
Users are hesitating or slowing down because labels, flows, and system states are unclear.
UX confusion · 2 excerpts
onboarding issue · 2 excerpts
Performance
Response time and loading delays are making common actions feel unreliable and frustrating.
slow performance · 2 excerpts
bug report · 4 excerpts
Onboarding
Early user experience issues are creating confusion and friction before teams reach core value.
onboarding issue · 2 excerpts
UX confusion · 2 excerpts
bug report · 4 excerpts
Tip: Themes are broader patterns made from repeated codes. If codes describe what is happening in a single excerpt, themes explain what is happening across many excerpts.
4. Theme Summary Cards
Bugs & Reliability · 4 excerpts
Key insight: Users are hitting failure points in exports, invites, and filtered workflows that interrupt important jobs and reduce confidence in the product.
Representative quote: "Every time I click export on the weekly report it just spins forever and then dumps me back to the dashboard."
Recommended action: Triage top blocking bugs by task criticality, starting with export and invite flows, and confirm fixes with affected users.
Feature Requests · 2 excerpts
Key insight: Users want features that reduce repetitive manual work, especially around exporting outputs and saving team-specific views.
Representative quote: "Can you please add a way to save custom views for each team? We keep rebuilding the same filters every morning."
Recommended action: Assess demand and implementation effort for custom saved views and richer export options, then prioritize the highest-frequency workflow improvement.
UX Friction · 2 excerpts
Key insight: Ambiguous labels and unclear consequences are causing hesitation, especially in actions that feel high-risk like archive or setup configuration.
Representative quote: "I genuinely cannot tell if 'archive' removes a customer forever or just hides them."
Recommended action: Review confusing labels, add inline explanations for high-risk actions, and test revised copy with new and existing users.
Performance · 2 excerpts
Key insight: Slow loading in core tasks like search and export is making the product feel unstable even when workflows eventually complete.
Representative quote: "The search takes 8–10 seconds whenever I filter by tag, and half the time the page flashes blank before results come back."
Recommended action: Investigate response-time bottlenecks in search and export, set performance thresholds, and monitor improvements after release.
Onboarding · 2 excerpts
Key insight: New users are struggling to understand first steps and team setup, which risks early drop-off before they experience product value.
Representative quote: "Signed up today and got dropped straight into the app with no clue what to do first."
Recommended action: Improve first-run guidance with a clearer setup path, stronger definitions for core concepts, and QA on invite delivery during onboarding.
5. Analysis Wrap-Up
Top finding
[Example: Reliability issues in exports, invites, and search are appearing alongside repeated requests for workflow-saving features.]
Most urgent theme
[Example: Bugs & Reliability]
Recommended next step
[Example: Review top-coded bug excerpts with Product and Engineering, then prioritize fixes for export and onboarding invite failures.]
Share with (stakeholder)
[Example: Product Manager, Design Lead, Engineering Manager, Customer Success Lead]
Date completed
[Example: Feb 3, 2026]