User Research Report Template: How to Present Findings That Drive Action

The problem with most research reports: They're too long, too dense, and structured around what the researcher found rather than what the stakeholder needs to decide.

A great user research report doesn't document the research process. It presents findings in a way that makes the path forward obvious — and makes it impossible to ignore the evidence.

This guide gives you a complete template for research reports that drive action, plus an explanation of how Koji's AI-generated reports automatically produce this structure for every study.

---

The Core Principle: Research Reports Are Decision Documents

Before you write a single word, ask yourself: What decision does this report need to inform?

• Should we build Feature X or Feature Y?
• Is our onboarding working for the target segment?
• Why are customers churning after 60 days?
• Does our new positioning resonate with enterprise buyers?

Every section of your report should make that decision easier. Evidence that doesn't connect to the decision is a distraction.

If you don't know what decision the report is informing, find out before you write. Research without a decision consumer isn't research — it's documentation.

---

The User Research Report Template

Section 1: Executive Summary (1 page maximum)

The executive summary is the most important section of your report. Many stakeholders — especially executives and product leads — will read nothing else.

Structure:

1. Research question (1-2 sentences): What were you trying to learn?
2. Method (1 sentence): How many interviews, over what period, with whom?
3. Top 3 findings (3 bullet points): The most important things you learned, framed as clear statements
4. Recommended actions (2-3 bullet points): What should happen next based on these findings?

Example:

Research question: Why do users who complete onboarding fail to run their first study within 30 days?

Method: 12 in-depth interviews with users who signed up in the past 60 days and have 0 completed studies.

Top findings:

• 9 of 12 participants said they weren't sure what research question to start with — they needed a template or guided starting point.
• 7 of 12 described feeling anxious about "getting it right" before inviting participants.
• 4 of 12 mentioned they recruited their first participant immediately after setup but the participant never responded, and they didn't know how to follow up.

Recommended actions:

• Add a "quick start" template library to the onboarding flow
• Add a checklist or quality review step before the study goes live to address perfectionism anxiety
• Add automated participant re-invitation after 48 hours of no response

This summary takes 60 seconds to read and gives a stakeholder everything they need to act.

---

Section 2: Research Background (Half page)

What to include:

• Research objective: The full question the research was designed to answer
• Research method: Type of interviews (moderated, AI-moderated, voice, text), duration, recruitment approach
• Participants: Number of participants, key demographic/firmographic characteristics, how they were recruited
• Timeline: When the research was conducted
• Researcher/team: Who conducted the research and who to contact with questions

Keep it factual and brief. Stakeholders don't need to evaluate your methodology — they need to trust it. A concise, confident description is more credible than a defensive one.

---

Section 3: Key Findings

This is the heart of the report. Each finding should follow the same structure:

Finding structure:

1. Headline (one clear statement): "Most users don't understand the difference between a study and a template"
2. Evidence (2-4 supporting quotes or observations with attribution)
3. Frequency (how many participants this applied to)
4. Implication (what this means for the decision at hand)

Example:

Finding: Users consistently overestimate how long setup takes — and abandon before they experience the value

"I thought I had to design all the questions myself from scratch. I spent an hour on the first study and wasn't happy with it so I gave up." — P7, Product Manager, SaaS company

"I wasn't sure what format the questions should be in, so I kept second-guessing myself." — P3, Founder, B2B startup

8 of 12 participants described a version of this experience. None of the 4 who reported smooth setup had been given the same level of unguided onboarding — 3 of them were referred by a colleague who showed them the template library.

Implication: The template library is not discoverable in the current onboarding flow. This is likely the primary driver of 30-day activation failure.

How many findings to include:

• 3-5 for most reports
• Never more than 7 (after that, stakeholders stop retaining them)
• Rank by strategic importance, not by how interesting they are to you

---

Section 4: Themes and Patterns

For studies with 10+ participants, a themes section helps stakeholders see the macro patterns rather than individual stories.

What to include:

• Top 5-7 themes: Named, defined, and quantified by frequency
• Theme frequency chart: A simple bar chart showing how often each theme appeared
• Sentiment breakdown: How did participants feel overall? What topics generated positive vs. negative sentiment?

Example theme table:

---

Section 5: Participant Quotes (Highlights)

A dedicated quotes section serves two purposes: it gives stakeholders the emotional truth behind the numbers, and it gives writers and product teams the language they need.

Selection criteria:

• Prioritize quotes that illustrate findings the data can't fully capture
• Include quotes from multiple participants, not just one eloquent respondent
• Include at least one challenging/uncomfortable quote — reports that only surface positive quotes aren't credible

Attribution format: Use participant role + company type, not names: "— Senior PM, B2B SaaS company" or "— P7, 30-day trial user." Real names require consent and add noise.

---

Section 6: Recommendations

The recommendations section is where research creates business value. It should be direct, specific, and owned.

Each recommendation should include:

1. Action statement: "Add X template library to onboarding flow, surfaced at step 2 of setup"
2. Evidence link: "Addresses the onboarding confusion theme present in 9 of 12 interviews"
3. Expected impact: "Should reduce 30-day activation time and decrease time-to-first-study"
4. Priority: High / Medium / Low
5. Owner suggestion: Which team should take this on?

Avoid vague recommendations like "improve onboarding" or "make it easier for users." These feel like research findings, not decisions. Stakeholders need specific actions.

---

Section 7: Appendix (Optional)

For reports that will be referenced over time, a brief appendix adds credibility and archival value:

• Full participant list (role, segment, interview date)
• Complete interview guide
• Links to individual interview transcripts (if available)
• Methodology notes

Keep the appendix lean. Its job is to answer "where did this come from?" — not to document everything you did.

---

How Koji Generates Research Reports Automatically

Building this structure manually for every research project takes 4-8 hours. Koji's report generation does it automatically — and does it for every study, not just the ones you have time to analyze.

Here's what Koji generates automatically after every completed study:

Executive summary: AI-generated overview with key themes, participant count, and top findings — ready to share.

Key findings: Each question in your study gets its own findings section with theme analysis, representative quotes, and frequency data. Every quote is linked back to the original interview transcript.

Theme analysis: Automatically extracted across all interviews with frequency charts and sentiment breakdown.

Recommendations: AI-generated action suggestions based on the pattern of findings, categorized by product, marketing, research, and general.

Individual interview analysis: Quality scores, sentiment, and structured answer extraction for every interview — so you can filter by participant segment or quality threshold.

Shareable report: Publish your report as a clean public link to share with any stakeholder — no login required.

The full report is available in minutes after your study is complete. For researchers who would otherwise spend a week on synthesis, Koji's automatic reports represent a 10x reduction in analysis time.

---

Research Report Writing Tips

Write findings, not observations. "Users struggled with the export function" is an observation. "The export function's incompatibility with Excel is the primary friction point blocking enterprise adoption" is a finding. Findings interpret what you observed.

Use present tense for findings. "Users expect templates to be available at setup" — not "users expected." Present tense creates urgency.

Show, don't tell. "Users were frustrated" is weak. "Seven users described feeling frustrated — using words like 'confused,' 'stuck,' and 'gave up' — specifically during the first study setup." is evidence.

Include the uncomfortable data. The most valuable research reports contain findings that challenge current assumptions. If you sanitize the uncomfortable findings, you've removed the most valuable parts.

Design for skim-readers. Use headers, bold text, bullet points, and visual hierarchy. Most stakeholders will skim before deciding whether to read. Make it easy to extract the key messages at a glance.

---

Common Research Report Mistakes

The "findings dump": 20+ bullet points with no prioritization. Stakeholders can't retain it, can't act on it, and stop trusting research that produces it.

Burying the lede: Starting with background and methodology before getting to findings. The most important things should be first.

Recommendations that sound like findings: "We should learn more about X" is not a recommendation — it's a research proposal. Recommendations are actions, not investigations.

Passive voice throughout: "It was found that users were observed to have difficulty..." is researcher-speak. Write like a human who wants to be understood.

Missing the "so what": Every finding needs an implication. If you can't say what the finding means for the decision at hand, rethink whether it belongs in the report.

---

The Bottom Line

A user research report that drives action has three characteristics: it's scannable in 2 minutes, it makes the evidence undeniable, and it makes the recommended actions obvious.

The template above is designed to hit all three. Executive summary first, key findings with quotes, themes with frequency data, specific recommendations with evidence links.

If the research process is taking time away from report writing, Koji's automatic synthesis is worth exploring. You design the study, collect responses via Koji's AI interviews, and Koji generates the full report structure — findings, themes, quotes, and recommendations — so you can spend your time acting on insights instead of producing them.

---

Related Resources

• Presenting Research Findings — Report presentation guide
• How to Analyze Qualitative Data — Analysis methodology
• Generating Research Reports — Koji report generation
• Writing Insight Statements — Craft actionable insights
• Research Repository Guide — Organize research outputs

Explore structured questions for building data-rich research reports.