Presenting Research Findings to Stakeholders

The most rigorous research in the world is worthless if it sits in a document nobody reads. Presenting findings is not an afterthought — it is the mechanism through which research drives decisions. According to a study by Yoo and Kim (2019) published in the International Journal of Design, research teams that invested in structured presentation of findings were 2.6x more likely to see their recommendations implemented compared to teams that shared raw reports without a narrative structure.

Your audience does not care about your methodology (much). They care about what you found and what they should do about it.

Know Your Audience

Before you design your presentation, understand who is receiving it and what they need:

Tailor your deliverable to your audience. A single "research report" rarely serves all of these stakeholders equally well. Consider creating a core report and audience-specific summaries.

The Three Report Formats

1. Executive Summary

Length: 1-2 pages Purpose: Communicate the headline findings and recommended actions Structure:

1. Study overview (1 paragraph): What was the research question, who did you talk to, and why?
2. Top findings (3-5 bullet points): The most important things you learned
3. Recommended actions (3-5 bullet points): What should we do about it?
4. What is at stake (1 paragraph): What happens if we do not act?

Example bullet:

"8 of 12 participants could not find the export feature without help. This means approximately two-thirds of users who need to share reports externally are either using workarounds or abandoning the task entirely."

2. Detailed Findings Report

Length: 5-15 pages depending on study scope Purpose: Provide the full picture for product teams and design Structure:

1. Study background: Research questions, methodology, participant summary
2. Participant overview: Demographics table, screening criteria, anonymized profiles
3. Theme-by-theme findings: Each theme as a section with supporting evidence
4. Cross-cutting patterns: Observations that span multiple themes
5. Prioritized recommendations: Actionable next steps ranked by impact and effort
6. Appendix: Full interview guide, participant matrix, methodology notes

3. Quick-Reference Insight Cards

Length: One card per insight (postcard-sized) Purpose: Shareable, digestible nuggets for team walls, Slack, or documentation Structure per card:

• Insight headline (1 sentence)
• Supporting data (frequency, 1-2 quotes)
• Recommended action (1 sentence)
• Evidence strength (strong / moderate / emerging)

These are particularly effective for keeping research top-of-mind between formal presentations. Pin them in your team's communication channel or print them for the office wall.

Storytelling With Data

Lead With the Story, Not the Method

A common mistake is spending the first 10 minutes of a presentation explaining your methodology. Executives will tune out before you get to the findings.

Instead, start with a participant story:

"Let me tell you about Sarah. She's a product manager at a mid-size SaaS company. She signed up for our tool on a Monday, spent 45 minutes trying to set up her first project, and by Wednesday she had downgraded to a competitor's free tier. When I asked her why, she said: 'I could see it was powerful, but I couldn't figure out how to make it do the basic thing I needed.'"

Now your audience is hooked. They want to know: How many Sarahs are there? And what can we do about it?

Use Participant Quotes Effectively

Quotes are the most powerful tool in your presentation arsenal. They bring abstract findings to life with human voice and specificity.

Rules for effective quote usage:

1. Select quotes that are vivid and specific: "I gave up after the third time the page loaded wrong" is better than "It was frustrating."
2. Keep quotes short: 1-2 sentences maximum in a presentation. Longer quotes lose the audience.
3. Always attribute to an anonymized participant: "P7, Product Manager, Enterprise" gives the quote context and credibility.
4. Use quotes to illustrate, not to prove: A single quote supports a finding; it does not establish one. Always frame quotes within the broader pattern.

The Data Sandwich

When presenting a finding, use this structure:

1. Quantitative context (top bread): "9 of 12 participants experienced this."
2. Qualitative depth (filling): A specific quote or story that makes the number human.
3. Implication (bottom bread): "This suggests that our onboarding is losing the majority of new users before they experience core value."

This format satisfies both the data-driven and narrative-driven people in your audience simultaneously.

Visualizing Qualitative Data

Qualitative data can be visualized — it just requires different approaches than charts and graphs.

Theme Maps

Show how themes relate to each other. A simple diagram with themes as nodes and connections as lines helps stakeholders see the system, not just individual findings.

Quote Walls

A curated collection of participant quotes organized by theme. This works especially well in physical spaces or as a shared digital board.

Journey Maps

If your research followed a user journey, map the findings onto the stages of that journey. Annotate each stage with participant quotes, emotional states, and pain points.

Frequency Tables

While qualitative research is not about counting, showing how many participants mentioned a theme provides useful signal:

A study by Braun and Clarke (2006) in Qualitative Research in Psychology — the most cited paper on thematic analysis with over 100,000 citations — emphasizes that frequency should supplement, not replace, the researcher's judgment about theme importance.

Generating Reports With AI

When you are working with a large volume of interviews, generating the initial report structure manually is time-consuming. AI-powered platforms like Koji can generate research reports that include theme identification, supporting quotes, and preliminary recommendations based on your interview data.

These auto-generated reports give you a strong starting draft: themes are surfaced with evidence, participant quotes are linked to findings, and patterns across interviews are highlighted. Your job is to validate the AI's interpretation, add your contextual knowledge, and tailor the narrative for your specific audience.

For details on how to generate and customize these reports, see generating research reports and publishing and sharing reports.

Presenting Live: Tips for the Room

Structure Your Presentation

1. Hook (2 minutes): Start with a compelling participant story
2. Context (3 minutes): Brief study overview — who, why, how many
3. Findings (15-20 minutes): Theme by theme, using the data sandwich
4. Recommendations (5 minutes): What to do, prioritized
5. Discussion (10+ minutes): Open the floor for questions and debate

Handle Pushback Gracefully

Stakeholders may challenge your findings. This is healthy. Prepare for common objections:

• "That's just 12 people": "You are right that this is qualitative data, not a statistically representative survey. What qualitative research tells us is why people behave a certain way. The consistency across 12 diverse participants gives us confidence in the direction of the finding."

• "I talked to a customer who said the opposite": "That is valuable context. In our study, we found [X number] participants who felt this way. There may be a segment difference worth exploring. Can you share which customer that was so we can compare profiles?"

• "We already knew this": "If the organization already has this insight, that is great validation. The question is whether we have acted on it. Here are specific recommendations for what to do next."

Common Mistakes to Avoid

1. Burying the lead: Do not save your most important finding for slide 47. Lead with impact.

2. Presenting every finding equally: Not all themes are equally important. Focus 60% of your time on the top 2-3 findings and briefly acknowledge the rest.

3. Forgetting the "so what": Every finding needs a recommendation. Data without action is trivia.

4. Making it about you: The presentation is about the participants and the team's next moves. Minimize references to your process and maximize focus on what was learned and what to do about it.

5. Not following up: Schedule a follow-up meeting 2-4 weeks after the presentation to check whether findings have been incorporated into planning. Research that is never revisited is research that was never used.

Key Takeaways

• Tailor your format to your audience: executives want headlines, product teams want detail, designers want mental models
• Start with a participant story, not your methodology
• Use the data sandwich: quantitative context, qualitative depth, implication
• Short, vivid, attributed quotes are your most powerful presentation tool
• AI-generated reports provide strong first drafts that need human refinement and audience tailoring
• Always pair findings with specific, prioritized recommendations

For the analysis process that feeds into your presentation, see turning interviews into insights. For details on auto-generating report drafts, explore generating research reports.

Frequently Asked Questions

How long should a research presentation be?

For a live presentation, 30-45 minutes including discussion time is ideal. For a written report, the executive summary should be 1-2 pages, and the detailed report should be 5-15 pages. Stakeholders rarely read reports longer than 15 pages end-to-end.

Should I include my interview guide in the report?

Include it as an appendix for transparency and reproducibility, but do not expect anyone to read it. The people who want to see the methodology will appreciate having it available. Everyone else will skip to the findings.

How do I handle findings that contradict what stakeholders want to hear?

Present them directly but empathetically. Lead with the strongest evidence, use participant quotes to make the finding human, and frame your recommendation constructively: "The data suggests [finding], which creates an opportunity to [positive action]."

When should I present research findings versus share a written report?

Present live when findings are high-stakes, require discussion, or involve organizational change. Share written reports for lower-stakes updates, ongoing tracking studies, or when stakeholders are geographically distributed and scheduling is impractical.

How do I measure whether my research presentation was effective?

Track whether your recommendations appear in sprint planning, roadmap discussions, or design briefs within 4 weeks of the presentation. If they do, the presentation worked. If they do not, follow up to understand what barrier exists between insight and action.