By the end of this lesson you can
- Present test findings so stakeholders act on them.
- Use clips, quotes and data persuasively and honestly.
- Tailor reports to different audiences.
The idea
Research only matters if it changes decisions. How you communicate findings decides whether they do.
Lead with what matters
Start with the top three to five findings and recommendations, then supporting detail. Busy stakeholders may read only the first page.
Show, do not just tell
- Video clips: 30-second clips of people struggling are more persuasive than any slide.
- Quotes: short, representative, anonymised.
- Numbers: task success counts, severity totals.
- Screenshots annotated with the problem.
Tailor the format
Executives want impact and decisions. Product managers want priorities and trade-offs. Designers and engineers want detail and examples. A short summary, a highlight reel and a detailed findings log often cover everyone.
Be honest
Do not cherry-pick dramatic clips that misrepresent the overall picture. State sample size and limits. Mention what worked well, too: it protects good design decisions.
Involve people early
Stakeholders who watch sessions live are far more likely to act. Invite them and give them a role, such as note-taking.
Why it matters in real projects
Findings that are ignored are wasted research, and wasted participants' time. Clear, honest and well-targeted communication builds trust in research, wins support for fixes and helps teams make better decisions faster. Over time, a reputation for reliable, useful findings gives you and your research a stronger voice in product decisions.
A realistic example
A designer sends a 40-page report after testing a new onboarding flow. Nobody reads past page three and the critical issues stay unfixed.
For the next round, they invite the product manager and two engineers to watch sessions, share a one-page summary with the top four findings and a two-minute highlight reel, and keep a detailed log for the team. The critical issue gets fixed the same week, because everyone saw participants struggle.
Step by step
Invite observers
Ask stakeholders to watch sessions.
Choose top findings
Pick three to five that matter most.
Gather evidence
Select clips, quotes and numbers for each.
Write a one-page summary
Findings, evidence, recommendations and limits.
Create a highlight reel
Two to three minutes of key clips, anonymised.
Present and agree actions
Discuss and record decisions.
Common mistakes
Mistake Long reports nobody reads.
Instead Lead with a short summary.
Mistake Cherry-picking dramatic clips.
Instead Represent the overall picture honestly.
Mistake Only reporting problems.
Instead Include what worked well.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 1 h
Findings summary
Communicate findings from a test you analysed.
Steps
- Write a one-page summary.
- Select three quotes and one clip or screenshot per finding.
- Include limits and positives.
- Present to a peer and ask what they would do next.
Deliverable
A one-page summary and evidence pack.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Findings must change decisions.
- Lead with what matters and show evidence.
- Tailor formats and invite observers.
- Be honest about limits and successes.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Sharing user research findings (opens in a new tab)GOV.UK Service Manual
- UX research cheat sheet (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.