PRODUCT MANAGEMENT TEMPLATE
User Research Synthesis Template
Synthesize findings from user research into themes, insights, and actionable recommendations.
Use this templateWhat's inside
Field | Value |
|---|---|
Study Name | Descriptive name for this research effort |
Method | Interviews / Surveys / Usability Testing / Diary Study / Analytics Review |
Dates | to |
Researcher | Lead researcher name |
Participants | Number and brief description (e.g., "8 enterprise admins, 5 individual contributors") |
Research Questions
Define the specific questions this research was designed to answer.
What problem or behavior were you investigating?
What assumptions were you testing?
What decisions will this research inform?
Methodology
Describe how the research was conducted. Include enough detail for someone to evaluate the rigor of the findings.
Recruitment: How were participants selected? What criteria were used?
Protocol: Describe the session structure, tasks, or survey design.
Duration: How long was each session? How many sessions were conducted?
Analysis approach: How were the data coded, tagged, or synthesized?
Key Findings
Finding 1: Descriptive title
Summarize what you observed or learned. Support with evidence.
"Direct participant quote that illustrates this finding."
Supporting data point or observation
Pattern observed across multiple participants
Finding 2: Descriptive title
Summarize what you observed or learned. Support with evidence.
"Direct participant quote that illustrates this finding."
Supporting data point or observation
Frequency or prevalence across the participant pool
Finding 3: Descriptive title
Summarize what you observed or learned. Support with evidence.
"Direct participant quote that illustrates this finding."
Supporting data point or observation
Contrast with prior assumptions or expectations
Themes
Theme | Evidence Strength | Related Findings |
|---|---|---|
Theme name | Strong / Moderate / Emerging | Finding numbers or descriptions |
Theme name | Strong / Moderate / Emerging | Finding numbers or descriptions |
Theme name | Strong / Moderate / Emerging | Finding numbers or descriptions |
Theme name | Strong / Moderate / Emerging | Finding numbers or descriptions |
Insights & Implications
For each insight, explain both what you learned and so what — why it matters for the product.
Insight 1: Concise insight statement
What we learned: Describe the insight in plain language.
So what: Explain the implication for product decisions, design, or strategy. What should change as a result?
Insight 2: Concise insight statement
What we learned: Describe the insight in plain language.
So what: Explain the implication for product decisions, design, or strategy.
Recommendations
Recommendation | Priority | Confidence | Related Theme |
|---|---|---|---|
Specific action to take based on findings | High / Medium / Low | High / Medium / Low | Theme name |
Specific action to take based on findings | High / Medium / Low | High / Medium / Low | Theme name |
Specific action to take based on findings | High / Medium / Low | High / Medium / Low | Theme name |
Specific action to take based on findings | High / Medium / Low | High / Medium / Low | Theme name |
Limitations & Caveats
Describe the boundaries of this research. Be transparent about what the findings can and cannot tell you.
Sample size or composition limitations
Self-reported data vs. observed behavior
Selection bias in recruitment
Conditions that may not generalize to the full user base
Next Steps / Further Research Needed
Follow-up study to validate a specific finding at larger scale
Quantitative survey to measure prevalence of observed behaviors
Usability test on proposed design solutions
Longitudinal study to track behavior changes over time
Appendix
Link to supporting materials. Keep raw data in its original location and reference it here.
Interview scripts: Link
Raw notes / transcripts: Link
Session recordings: Link
Survey instrument: Link
Affinity diagram / analysis artifacts: Link
Other Product templates
-
A/B Test PlanDesign an experiment with hypothesis, variants, success metrics, and sample size requirements. -
Competitive AnalysisAnalyze competitors across features, pricing, positioning, and market strategy. -
Feature SpecificationDetail a specific feature with user stories, acceptance criteria, edge cases, and dependencies.