UX Research · Step 7 · 6 min read
Research reports people read
A report is only useful if it changes what someone does next. How to write one that a busy person can read in a minute and a careful one can check in an hour: three reading depths, one finding per slide, timing, and formats that aren't a 40-page PDF.
Nobody owes your report their attention. You have to earn it in the first line. The study is done, the insights are written, and now they have to reach people who weren't in the room and have twenty other things to read. A report people read is short at the top, deep underneath, and on the table before the decision is made, not after.
What you'll be able to do after reading:
- Write a report that works at three reading depths
- Build a findings slide from a headline, the facts, why it matters and the evidence
- Time a report so it lands before the decision
- Pick a format for the audience, not out of habit
1. Three readers, one report
Headlinesfor leadership · 1 minute
People settle up in the group chat, not in the app. We should meet them there.Themesfor the product team · 10 minutes
- 7 of 8 households announce a new bill in a chat before anyone opens an app.
- The first argument is about how a split was worked out, not about the amount.
- One person becomes the household's "banker", and that person is the one who gives up.
Evidence and methodfor whoever checks · an hour
- 8 interviews, 45 minutes each, flatmates and couples, 2 to 5 people per home.
- Screener, guide, consent form and the synthesis board, linked.
- Quotes with participant codes and timestamps; clips only where consent allows.
Every report has at least three readers. The executive reads the headlines and stops. The product manager skims the themes to see what it means for the roadmap. The engineer or analyst who doubts a finding reads the method and the evidence. NN/g's advice is to design the report for all three depths at once: headlines that make sense alone, themes for skimmers, and full detail for the people who check (Rachel Krause, NN/g, 2022).
The test is simple: cover everything but the headlines. Does someone who reads only those know what you learned and what you recommend? If not, the headlines are labels ("Navigation"), not findings ("People can't find the bill they added last week").
2. A finding is a headline, not a topic
The GOV.UK Service Manual gives a structure for each findings slide that works for any format: a headline that states something you learned, a sentence or two of key facts, a sentence or two on why it matters, and a photo, screenshot or participant quote (GOV.UK Service Manual, Sharing user research findings). For a whole deck it suggests one or two slides on what you did, five to ten slides of findings, and one or two on next steps.
Three habits make the difference:
- Lead with the insight, not the data. Data is what you collected, a finding is a pattern in it, an insight explains the opportunity using context (Sara Paul, NN/g, 2023). The headline should be the insight, the facts underneath it are the finding, and the quote is the data. See Writing insights that change decisions.
- One person, then the number. A single participant's story makes the finding felt; the count says how common it is. Use anecdotes to support numbers, not to replace them (NN/g, 2022).
- Say what you'd do. Laura Klein puts it bluntly: "Research findings are not roadmap arguments." Pair each problem with its likely impact and a suggested next step (NN/g, 2026).
3. Early beats perfect
A small study delivered before planning is worth more than a big one delivered after; NN/g advises having results ready ahead of the planning cycle, and finding out when prioritisation happens so you know your deadline (NN/g, 2026). GOV.UK says the same from the team side: update the team regularly, ideally at a fixed time each week or sprint, and share findings as soon as possible (GOV.UK Service Manual).
In practice, that means two moments, not one:
- Top-line, within a day or two of the last session: three to five headlines, clearly marked as early. People who watched the sessions can check them against what they saw.
- The full report, when the analysis is done: the same headlines, now with the evidence, the method and the recommendations.
And the best report is partly unnecessary: GOV.UK recommends everyone on the team observes at least two hours of research every six weeks (GOV.UK Service Manual, Plan user research for your service). People who saw a participant struggle don't need to be convinced by a slide.
4. Formats that fit the audience
| Audience | What they need | A format that works |
|---|---|---|
| Leadership | The decision, the risk, what it costs to wait | One page, or the first two minutes of a readout |
| Product team | What changes in the backlog, and why | A readout with discussion, then the deck in the shared space |
| Designers and engineers | The detail behind each finding | Clips, the full deck, the synthesis board |
| Whole organisation | That this was learned, and where to find it | A short post, a research wall, an entry in the repository |
GOV.UK lists show-and-tells, a research wall, short video clips, posters of quotes, blog posts and empathy maps as ways to share (GOV.UK). NN/g adds short videos, "mini museums" and clip screenings, with participants' consent for any video, and warns against making people learn a new tool just to read your report (NN/g, 2022). Whatever the format, the report ends up in one findable place: that's the next lesson, Research repositories.
5. Common mistakes
- Headlines that are topics ("Onboarding") instead of findings.
- Forty findings at the same weight, with no order and no "most important".
- Method first, findings on page twelve.
- A quote with no count, or a count with no person.
- Delivering after the roadmap was decided.
- Clips or names shared beyond what participants agreed to (see Research ethics and consent).
6. Vocabulary
| Term | Meaning |
|---|---|
| Top-line | A short, early summary of the main findings, before the full analysis |
| Readout | A live presentation of the findings, with time for questions |
| Finding | A pattern across the data, stated as a sentence |
| Insight | A finding explained with context, pointing at an opportunity |
| Recommendation | A suggested next step, with an owner and the evidence behind it |
| Show-and-tell | A regular, informal session where a team shares what it learned |
7. Try it (no tools needed)
- Find an old research report, yours or your team's.
- Copy only the headlines onto a page.
- Hand that page to someone who never saw the study. Ask: what did we learn, and what should we do?
Reflection questions: Which headlines were topics instead of findings? Who needed this report, and did it reach them before their decision?
8. If you already practise
- Write the headlines first, before the slides; if you can't write them, the analysis isn't done.
- Keep a fixed slot every sprint for a five-minute research update, even when there's little to say.
- Track which findings turned into decisions; you'll need that for Showing the impact of research.
Checklist
Learn more
- Rachel Krause, Creating Engaging Reports & Asynchronous Presentations (NN/g, 2022)
- GOV.UK Service Manual, Sharing user research findings
- Sara Paul, Data vs. Findings vs. Insights: The Differences Explained (NN/g, 2023)
- Laura Klein, How to Get Research Recommendations on the Roadmap (NN/g, 2026)
Books, courses and videos to go deeper
- The Pyramid PrincipleBarbara MintoBook · Pearson, 2021
- Interviewing UsersSteve PortigalBook · Rosenfeld Media, 2nd edition, 2023 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Writing insights that change decisions · Research repositories · Present findings in ten minutes · Journey maps