How to present research findings from a written report

You’ve finished the research. Interviews are done, the notes are tidied and the write-up runs to several pages, with themes, quotes, method and caveats. Now there’s a readout meeting on the calendar, and most of the people coming will never read the full report.

That’s normal, and it’s fine. The readout deck isn’t a shorter copy of the report. It’s the version for people who need to act on what you found, and it works best when it’s built around decisions rather than around your method.

Start from what the team will do differently

Ask yourself one question before you make any slides: what should change because of this research?

Maybe the team should drop a feature idea, rethink the onboarding flow or prioritise a customer segment they’d been ignoring. Write that down as two or three short statements. They become the spine of the deck. If you’re still gathering material, a guide to researching for a presentation covers that earlier step.

If you can’t answer the question yet, that’s useful to know. It usually means the findings are still a list of observations, and they need one more pass to turn into conclusions.

Reorder the report for a readout

Research reports tend to follow the order the work happened: goals, method, participants, findings, recommendations. That’s right for a document, because readers want to judge the method before trusting the results.

A readout audience usually wants the reverse. A structure that works:

1. What we set out to learn (one slide)
2. The headline: the most important thing you found, in one sentence (one slide)
3. Key findings, one per slide (three to five slides)
4. What this means for us: recommendations or decisions (one or two slides)
5. How we did it: method and participants, briefly (one slide)
6. Open questions and what you’d research next (one slide)

Method moves near the end. It still matters, and you should be ready to discuss it, but it isn’t what the room came for. If you’d rather start from a ready layout, a research project template gives you slides for each of these parts.

One finding, one slide

For each finding, the slide needs three things:

• A headline that states the finding as a sentence. Not “Onboarding” but “New users stall when asked to invite teammates before they’ve seen the product.”
• The evidence: a short quote, a simple count or a clear example from the research.
• Why it matters: one line connecting the finding to the product or decision.

The example above is illustrative. Keep the supporting detail, such as more quotes, participant breakdowns and edge cases, in the report or your speaker notes.

Show evidence without overloading it

Research slides go wrong in two opposite ways. Some show nothing but conclusions, which makes them hard to trust. Others paste in pages of quotes, which makes them hard to read. Aim for the middle.

Use one strong quote, not five. Pick the quote that captures the finding most clearly, show it large and attribute it to a role rather than a name, such as “operations lead, mid-size retailer”. Use real quotes only, with participants’ consent.

Count carefully. With small qualitative samples, say “four of the six people we interviewed”, not a percentage. Percentages suggest a precision the sample can’t support.

Show patterns visually where you can. A simple grid of participants against themes, with a mark where each theme came up, shows how widespread a finding is at a glance.

Separate what people said from what you concluded. Directly observed behaviour and your interpretation of it should be clearly labelled, so the room can weigh them differently.

Write the recommendations as choices

The recommendations slide is where the readout turns into action. Write each recommendation so the team can agree, disagree or assign it:

Finding	Recommendation	Owner to decide
Users stall at the invite step	Move invites after the first project is created	Product lead
Pricing page answers few real questions	Rewrite around the three most asked questions	Marketing
Admins want a usage summary	Explore a monthly summary email	Design

These rows are illustrative. A table like this gives the discussion something concrete to work through, rather than a general agreement that the research was interesting.

Prepare the written report to help you

If the report is structured well, the readout almost builds itself. A few habits on the page make a difference:

• Write each finding under its own heading, phrased as a statement.
• Put the headline finding in a summary at the top of the report.
• Keep quotes in a consistent format under each finding, so you can pick one quickly.
• Move raw notes and transcripts under an appendix heading.

For the general approach to turning any long document into slides, see how to turn a written document into a presentation. If the research is a group assignment, from class notes to a student project presentation covers structure and dividing the work.

Running the readout

Give the headline in the first two minutes. Then walk through findings briskly and save most of the time for the recommendations, because that’s where the room’s input matters.

Expect questions about the method, especially from people whose assumptions the research challenges. Have a backup slide with participant details and how you recruited them.

End by confirming who will decide each recommendation and when. Then share the full report, so anyone who wants the detail can read it. If your findings sit in scattered notes rather than one page, an AI tool for building presentations can help you draft the readout from a short description instead.

Before the meeting

• Is the headline finding on slide two?
• Does each finding slide have a statement headline, one piece of evidence and a reason it matters?
• Are counts given as numbers of people, not percentages?
• Are observations clearly separated from interpretation?
• Does each recommendation have someone to decide it?

If your report already lives in a page with clear headings, Notion2Deck can turn it into a first draft of the readout, leaving you to choose the evidence and sharpen the recommendations.