Structure your user research findings into clear themes and actionable recommendations so stakeholders can make faster, more confident product decisions.
The template
Research Context
Summarize the research goal, methodology, number of participants, and the time period in which the research was conducted.
Example: 12 moderated user interviews conducted in March 2024 with mid-market SaaS customers to understand onboarding friction points and first-week activation barriers.
Key Findings & Themes
List the 3–5 dominant patterns that emerged across participants, noting how frequently each theme appeared and which user segments it affected most.
Example: Theme 1 — Integration confusion (8/12 participants): Users struggled to connect their existing tools during setup, with Slack and Salesforce integrations cited most often as unclear. Theme 2 — Value realization delay (7/12 participants): Users did not perceive meaningful value until day 4–5, well past the intended aha moment at day 1. Theme 3 — Documentation gaps (6/12 participants): Help articles were found but described as too technical for non-developer users.
Supporting Evidence
Include 2–3 direct participant quotes per theme that illustrate the finding in the user's own words, tied to a specific theme label.
Example: [Integration confusion] — "I spent an hour trying to connect Salesforce and just gave up. I assumed I was doing something wrong but couldn't find any guidance." — Participant 7, Operations Manager. [Value realization delay] — "By day three I still wasn't sure what I was supposed to be getting out of this. I almost cancelled." — Participant 3, Product Lead.
Recommendations & Next Steps
For each key theme, write one specific, prioritized recommendation tied to a team or owner, and indicate the suggested timeline or priority level.
Example: [High priority — Product team] Redesign the integration setup flow with step-by-step walkthroughs and contextual tooltips for top 5 integrations — target Q2 sprint. [Medium priority — Content team] Rewrite onboarding help articles in plain language with use-case-based examples — target within 6 weeks. [High priority — Growth team] Introduce a day-1 quick win milestone to accelerate perceived value — A/B test recommended.
How to use it
Gather your raw research data Collect all interview notes, transcripts, or session recordings in one place before you begin filling out the template so nothing gets missed.
Identify recurring themes Read through participant responses and tag repeating problems, behaviors, or sentiments, then group related tags into 3–5 named themes that represent your core findings.
Match evidence to themes Pull 2–3 direct quotes or specific observations per theme to ground each finding in real user language rather than your own interpretation.
Write one recommendation per theme Translate each finding into a single, specific action with a clear owner and priority level so your stakeholders know exactly what to do next.
What it looks like filled in
Integration Setup Confusion
"I spent an hour trying to connect Salesforce and just gave up — I had no idea what I was doing wrong."
→ Redesign the integration flow with a step-by-step guided setup and contextual tooltips for the top 5 integrations.
Delayed Value Realization
"By day three I still wasn't sure what I was getting out of this tool. I almost cancelled my trial."
→ Introduce a day-1 quick win milestone in onboarding to help users experience core value within the first session.
Documentation Too Technical
"The help articles exist but they read like they were written for engineers, not someone like me."
→ Rewrite the top 10 help articles in plain language with use-case-based examples targeting non-technical users.
Why teams skip the template
Manually reading every transcript takes hours With 10 or more interviews, reviewing raw notes and tagging themes by hand is time-consuming and easy to do inconsistently across sessions.
Theme identification is subjective and easy to bias When you code themes manually, you risk over-weighting findings that stand out to you personally rather than patterns that are statistically significant across participants.
Turning findings into a shareable report is its own project Even after analysis is done, formatting quotes, themes, and recommendations into a stakeholder-ready document can take another half day of work on top of the research itself.
Analyze your user research findings and insights automatically — no template needed
