{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-05-18T13:51:58.125Z"},"content":[{"type":"documentation","id":"fddab163-eab2-4415-acfc-03794c86d59e","slug":"user-research-report","title":"How to Write a User Research Report: Structure, Templates, and Best Practices","url":"https://www.koji.so/docs/user-research-report","summary":"A user research report translates interview data into decisions using a 7-section structure: executive summary (what was researched, what was found, what to do), research overview, key findings (each with specific headline, evidence, frequency, and implication), supporting data visualizations, cross-interview themes, recommendations, and methodology appendix. Koji generates reports automatically as interviews complete — transcribing, extracting structured answers, identifying patterns, and assembling findings in real time. The Interviews plan includes unlimited free report refreshes; published reports are shareable via link without requiring a Koji account.","content":"A user research report translates raw interview data into decisions. The best reports don't just document what participants said — they tell stakeholders what it means and what to do about it. This guide covers report structure, audience-first writing strategies, visualization choices, and how Koji generates research reports automatically as interviews complete.\n\n## What Is a User Research Report?\n\nA user research report is the deliverable that communicates your research findings to the people who need to act on them — product managers, designers, engineers, executives, or clients. It converts interview transcripts, themes, and patterns into a structured narrative supported by evidence.\n\nThe goal is not to faithfully document every opinion you heard. The goal is to give your audience what they need to make a specific decision — confident in the evidence behind it.\n\n## Who Reads User Research Reports?\n\nBefore writing a word, know your primary audience. Different roles need different formats:\n\n**Product Managers**: Need specific, decision-relevant insights. Focus on \"what do users actually need?\" rather than \"what did they say?\" Recommend concrete next steps. Keep it under 10 slides or 1,500 words.\n\n**Designers**: Need behavioral context and representative quotes. Show specific friction points, user mental models, and the emotional dimensions of pain. Verbatim quotes are essential.\n\n**Engineers**: Need clarity on which problems are worth solving and which edge cases actually occur. Frame findings in terms of failure modes and frequency.\n\n**Executives**: Need the bottom line first. Start with the strategic implication. Provide evidence in an appendix for those who want depth.\n\n**Clients** (for agencies): Need narrative structure, professional polish, and clear ROI framing. Include methodology, sample description, and confidence levels.\n\nWrite for your primary audience and make secondary sections skimmable for everyone else.\n\n## Standard User Research Report Structure\n\n### 1. Executive Summary\n\nThe three things your audience needs to know:\n- What we researched and why (1–2 sentences)\n- What we found (3–5 bullet points with specific insights)\n- What we recommend (1–3 concrete, actionable steps)\n\nThe executive summary must stand alone. Assume 60% of stakeholders will read only this section. Make it dense with specific insights, not vague summaries. Avoid \"users have mixed feelings\" — instead write \"11 of 14 participants abandoned setup at the API key step because they expected it to auto-populate from OAuth.\"\n\n### 2. Research Overview\n\n- **Research question**: What were we trying to learn?\n- **Methodology**: How we ran the research (interviews, voice/text, AI-moderated)\n- **Sample**: How many participants, how recruited, behavioral profile, when research was conducted\n- **Dates**: When fieldwork occurred\n\nThis section establishes credibility. Stakeholders who understand your methodology trust your findings more than those who see conclusions without context.\n\n### 3. Key Findings\n\nThe core of the report. Structure each finding as:\n\n**Finding headline** — a specific, actionable insight, not a topic\n\n**Evidence** — 2–3 supporting quotes from participants\n\n**Frequency** — \"11 of 14 participants mentioned...\" or \"Raised by 3 participants but consistently the highest-severity issue\"\n\n**Implication** — what this finding means for the decision you're informing\n\n**Good finding headline**: \"Users abandon setup at the API key step because they expect it to auto-populate from their OAuth connection\"\n\n**Bad finding headline**: \"Users have issues with the setup process\"\n\nThe good headline tells you exactly what the problem is and implies a testable solution. The bad one tells you nothing actionable.\n\n### 4. Supporting Data Visualizations\n\nFor structured questions — scale ratings, single-choice, multiple-choice, ranking, yes/no — include charts. Koji generates these automatically from structured question responses:\n\n- **Scale questions**: Distribution chart showing how many participants gave each rating\n- **Single / multiple choice**: Frequency bar chart showing how many chose each option\n- **Ranking questions**: Average rank table from most to least preferred\n- **Yes / No**: Pie or donut chart with participant counts\n\nThese visualizations let stakeholders see quantitative distribution at a glance, while the qualitative findings provide the \"why\" behind the numbers. This is the core advantage of using Koji's six question types — you get both the story and the statistics from a single interview.\n\n### 5. Themes\n\nA themes section sits between individual findings and the executive summary. Where findings are specific observations, themes are broader interpretive patterns that cut across multiple findings.\n\nExample themes:\n- \"Confidence gap: Users understand what to do but don't trust that it worked\"\n- \"Time pressure overrides thoroughness: Users skip optional steps regardless of their stated importance\"\n- \"Social proof drives decision-making: Every major purchase decision was validated by a peer before proceeding\"\n\nThemes are interpretive — they require the researcher's judgment, not just tallying responses. This is where your expertise shows and where AI-assisted tools still benefit from human review.\n\n### 6. Recommendations\n\nWhat should happen next? Effective recommendations are:\n\n- **Specific**: \"Redesign the API key step to auto-populate from OAuth, with a manual fallback\" — not \"Improve the setup experience\"\n- **Prioritized**: Distinguish between must-do (addresses a critical blocker for most participants) and nice-to-have\n- **Evidence-backed**: Each recommendation references the finding it responds to\n- **Scope-appropriate**: A copy change shouldn't be recommended as a \"complete redesign\" if that's all that's needed\n\n### 7. Methodology Appendix\n\nFor audiences who want detail: screener questions used, full interview guide, participant profile breakdown by segment, analytical approach. Keep this out of the main report body — link to it for those who need it.\n\n## How Koji Generates User Research Reports Automatically\n\nTraditional report writing is a multi-day process: transcribe → code → theme → write → format. Koji compresses this dramatically.\n\nAs each interview completes, Koji:\n\n1. **Transcribes** the conversation automatically (voice and text)\n2. **Extracts structured answers** for each question type — scale ratings, choice selections, rankings — and aggregates them into charts\n3. **Generates individual insights** — key quotes, patterns, and notable responses from each interview\n4. **Runs cross-interview analysis** — identifies patterns and themes across your full participant set\n5. **Assembles a report** — structured by question, with aggregated data and representative quotes\n\nThe Interviews plan (€79/month) includes unlimited report refreshes. As more interviews complete, refresh your report to incorporate new data and watch themes solidify as sample size grows. The Insights plan includes 5 free report refreshes; additional refreshes cost 5 credits each.\n\n## Publishing and Sharing Research Reports\n\nKoji supports report publishing — shareable links that let stakeholders view findings in a clean, formatted interface without needing a Koji account. Published reports include all findings, supporting quotes, data visualizations, and the executive summary.\n\nThis is the fastest path from \"research complete\" to \"stakeholders aligned\": generate the report, publish the link, share it in Slack. No exporting to slides, no reformatting, no waiting for a read-out meeting.\n\n## Writing Tips for More Impactful Reports\n\n**Lead with recommendations, not methodology**: Stakeholders care about what to do, not how you gathered the data. Put recommendations first, methodology last.\n\n**Use participant quotes strategically**: Choose the one quote that most precisely illustrates each finding. Specificity beats volume — one sharp quote is more convincing than five vague ones.\n\n**Don't hide uncertainty**: If 6 of 15 participants raised an issue, say \"6 of 15.\" Don't round up to \"many participants.\" Stakeholders should be able to calibrate their confidence from your report directly.\n\n**One source of truth**: Don't email a slide deck and also post a shared doc. Choose one format, share the link, update it in place. Research findings that exist in multiple versions destroy trust in the findings.\n\n**Make findings findable over time**: Use consistent heading structure. Number your findings. Store reports in a central research repository so future teams can learn from past research without starting from scratch.\n\n## Common User Research Report Mistakes\n\n**Writing a transcript summary instead of a report**: A list of \"Participant 1 said X, Participant 2 said Y\" is documentation, not analysis. Your job is to interpret patterns, not transcribe conversations.\n\n**Burying the headline**: The most important finding belongs in the first paragraph, not page 7. Write the report in the order your audience cares about, not the order you discovered things.\n\n**Over-caveating**: Qualitative research can't be statistically significant — acknowledge this once, then commit to your findings. Constant hedging undermines the credibility of your analysis.\n\n**Reporting without recommending**: Your stakeholders need to know what to do. Tell them. \"More research needed\" is only acceptable when it's true and you specify exactly what research.\n\n**Charts without context**: A bar chart showing that 60% of users chose Option A is meaningless without knowing why. Always pair quantitative data with the qualitative context from open-ended responses.\n\n## Key Takeaways\n\n- Know your primary audience before writing — format and depth should match what they need to decide\n- Structure every key finding with a specific headline, evidence, frequency, and implication\n- Use Koji's six question types to generate both qualitative quotes and quantitative charts from the same interviews\n- Lead with executive summary and recommendations; put methodology in the appendix\n- Publish a shareable link rather than emailing a static file — it stays current as you add interviews\n\n## Related Resources\n\n- [Structured Questions Guide: Mixing Qualitative and Quantitative in One Interview](/docs/structured-questions-guide)\n- [Thematic Analysis: Finding Themes in Interview Data](/docs/thematic-analysis-guide)\n- [How to Conduct User Interviews: The Complete Guide](/docs/how-to-conduct-user-interviews)\n- [How to Write a Research Brief](/docs/how-to-write-research-brief)\n- [Jobs to Be Done Framework: Understanding What Users Actually Want](/docs/jobs-to-be-done-framework)\n- [AI Voice Interviews: Automated Voice User Research](/docs/ai-voice-interviews)","category":"Analysis & Synthesis","lastModified":"2026-05-17T20:31:05.449022+00:00","metaTitle":"How to Write a User Research Report: Structure and Templates (2026)","metaDescription":"Learn how to structure a user research report for PMs, designers, and executives. Covers findings, themes, data visualizations, and recommendations — plus how Koji auto-generates reports.","keywords":["user research report","research report template","how to write a research report","ux research report","research findings report","research report structure","qualitative research report","interview findings report","user research deliverables"],"aiSummary":"A user research report translates interview data into decisions using a 7-section structure: executive summary (what was researched, what was found, what to do), research overview, key findings (each with specific headline, evidence, frequency, and implication), supporting data visualizations, cross-interview themes, recommendations, and methodology appendix. Koji generates reports automatically as interviews complete — transcribing, extracting structured answers, identifying patterns, and assembling findings in real time. The Interviews plan includes unlimited free report refreshes; published reports are shareable via link without requiring a Koji account.","aiPrerequisites":["Experience collecting qualitative interview data","Familiarity with basic research methods"],"aiLearningOutcomes":["Structure a user research report for different stakeholder audiences","Write specific, evidence-backed finding headlines that drive action","Combine qualitative quotes with quantitative chart data in one report","Develop cross-interview themes from individual findings","Use Koji's automatic report generation and publishing features"],"aiDifficulty":"intermediate","aiEstimatedTime":"16 minutes"}],"pagination":{"total":1,"returned":1,"offset":0}}