How to Write a User Research Report: Structure, Templates, and Best Practices

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.

What Is a User Research Report?

A 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.

The 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.

Who Reads User Research Reports?

Before writing a word, know your primary audience. Different roles need different formats:

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.

Designers: Need behavioral context and representative quotes. Show specific friction points, user mental models, and the emotional dimensions of pain. Verbatim quotes are essential.

Engineers: Need clarity on which problems are worth solving and which edge cases actually occur. Frame findings in terms of failure modes and frequency.

Executives: Need the bottom line first. Start with the strategic implication. Provide evidence in an appendix for those who want depth.

Clients (for agencies): Need narrative structure, professional polish, and clear ROI framing. Include methodology, sample description, and confidence levels.

Write for your primary audience and make secondary sections skimmable for everyone else.

Standard User Research Report Structure

1. Executive Summary

The three things your audience needs to know:

• What we researched and why (1–2 sentences)
• What we found (3–5 bullet points with specific insights)
• What we recommend (1–3 concrete, actionable steps)

The 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."

2. Research Overview

• Research question: What were we trying to learn?
• Methodology: How we ran the research (interviews, voice/text, AI-moderated)
• Sample: How many participants, how recruited, behavioral profile, when research was conducted
• Dates: When fieldwork occurred

This section establishes credibility. Stakeholders who understand your methodology trust your findings more than those who see conclusions without context.

3. Key Findings

The core of the report. Structure each finding as:

Finding headline — a specific, actionable insight, not a topic

Evidence — 2–3 supporting quotes from participants

Frequency — "11 of 14 participants mentioned..." or "Raised by 3 participants but consistently the highest-severity issue"

Implication — what this finding means for the decision you're informing

Good finding headline: "Users abandon setup at the API key step because they expect it to auto-populate from their OAuth connection"

Bad finding headline: "Users have issues with the setup process"

The good headline tells you exactly what the problem is and implies a testable solution. The bad one tells you nothing actionable.

4. Supporting Data Visualizations

For structured questions — scale ratings, single-choice, multiple-choice, ranking, yes/no — include charts. Koji generates these automatically from structured question responses:

• Scale questions: Distribution chart showing how many participants gave each rating
• Single / multiple choice: Frequency bar chart showing how many chose each option
• Ranking questions: Average rank table from most to least preferred
• Yes / No: Pie or donut chart with participant counts

These 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.

5. Themes

A 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.

Example themes:

• "Confidence gap: Users understand what to do but don't trust that it worked"
• "Time pressure overrides thoroughness: Users skip optional steps regardless of their stated importance"
• "Social proof drives decision-making: Every major purchase decision was validated by a peer before proceeding"

Themes 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.

6. Recommendations

What should happen next? Effective recommendations are:

• Specific: "Redesign the API key step to auto-populate from OAuth, with a manual fallback" — not "Improve the setup experience"
• Prioritized: Distinguish between must-do (addresses a critical blocker for most participants) and nice-to-have
• Evidence-backed: Each recommendation references the finding it responds to
• Scope-appropriate: A copy change shouldn't be recommended as a "complete redesign" if that's all that's needed

7. Methodology Appendix

For 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.

How Koji Generates User Research Reports Automatically

Traditional report writing is a multi-day process: transcribe → code → theme → write → format. Koji compresses this dramatically.

As each interview completes, Koji:

1. Transcribes the conversation automatically (voice and text)
2. Extracts structured answers for each question type — scale ratings, choice selections, rankings — and aggregates them into charts
3. Generates individual insights — key quotes, patterns, and notable responses from each interview
4. Runs cross-interview analysis — identifies patterns and themes across your full participant set
5. Assembles a report — structured by question, with aggregated data and representative quotes

The 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.

Publishing and Sharing Research Reports

Koji 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.

This 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.

Writing Tips for More Impactful Reports

Lead with recommendations, not methodology: Stakeholders care about what to do, not how you gathered the data. Put recommendations first, methodology last.

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.

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.

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.

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.

Common User Research Report Mistakes

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.

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.

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.

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.

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.

Key Takeaways

• Know your primary audience before writing — format and depth should match what they need to decide
• Structure every key finding with a specific headline, evidence, frequency, and implication
• Use Koji's six question types to generate both qualitative quotes and quantitative charts from the same interviews
• Lead with executive summary and recommendations; put methodology in the appendix
• Publish a shareable link rather than emailing a static file — it stays current as you add interviews

Related Resources

• Structured Questions Guide: Mixing Qualitative and Quantitative in One Interview
• Thematic Analysis: Finding Themes in Interview Data
• How to Conduct User Interviews: The Complete Guide
• How to Write a Research Brief
• Jobs to Be Done Framework: Understanding What Users Actually Want
• AI Voice Interviews: Automated Voice User Research