Effective ways to share research insights

Share research so it changes decisions: lead with the answer, tailor the format to each audience, back findings with short video clips and quotes, link each insight to a recommendation and owner, and store everything in a searchable repository. Involving stakeholders during research makes them far more likely to act on it.

Why research often fails to change decisions

Teams invest considerable time and money in user research, yet many studies have little effect on what gets built. The research itself is usually sound. The problem is in how findings are shared. Long reports arrive weeks after the decisions they were meant to inform, findings are written in research language rather than business terms, and recommendations have no owner, so nobody acts on them.

Sharing research effectively means treating communication as part of the research, not an afterthought. It involves knowing who needs the findings, what decisions they face and what format will help them act. Done well, it turns research into a trusted input for product decisions across the organisation.

Match the format to the audience

Writing a one-page summary

A one-page summary is the single most useful format for most audiences. It should start with the main answer to the research question in one or two sentences, followed by the three to five most important findings, each with a short piece of evidence and a recommendation. Close with what the team should do next and who owns each action. Link to the full findings and recordings for anyone who wants detail.

• The question: What we wanted to learn and why.
• The answer: The main conclusion in plain language.
• Key findings: Three to five findings with evidence.
• Recommendations: What to do about each finding.
• Next steps: Owners, dates and links to detail.

Making evidence memorable

Numbers and written findings are easy to forget. Seeing a real person struggle with a product is not. Short video clips, ideally under a minute, are one of the most persuasive ways to share research. Pair clips with direct quotes, before-and-after comparisons and simple charts showing how often a problem occurred. Always get consent before sharing recordings, and blur or remove personal information.

Choosing the right channels

Different findings suit different channels. Urgent issues, such as a bug that blocks checkout, should be raised immediately in the team’s usual chat or ticketing tool. Strategic findings deserve a live session with decision-makers. A short monthly digest of recent insights, shared across the company, keeps research visible to people who are not directly involved in projects. Making findings easy to find later, in a searchable repository, matters as much as the first presentation.

Tactics that work

• Lead with the answer: Start with what you learned and what to do.
• Show, do not tell: Thirty-second clips of users struggling are persuasive.
• Invite observers: Stakeholders who watch sessions act on findings.
• Assign owners: Every recommendation gets a name and a date.

Using workshops instead of presentations

Presentations put stakeholders in a passive role. Workshops invite them to work with the findings directly. In a synthesis or prioritisation workshop, the research team shares key findings and the group sorts, discusses and prioritises them together, then agrees actions. People who help shape the conclusions are much more likely to act on them, and the discussion often surfaces constraints and ideas the researchers did not know about.

• Affinity mapping: Group observations into themes together.
• Dot voting: Prioritise problems by impact.
• How might we: Turn problems into design opportunities.
• Action planning: Agree owners and next steps.

From study to decision

• Debrief: Share top findings within a day of the last session.
• Summarise: One page of key insights and recommendations.
• Present: A short session tailored to each audience.
• Store and follow up: Add to the repository and check progress.

Storing findings as linked atoms makes them easy to reuse; see atomic research. Clear UX metrics help show whether changes worked.

Following up on recommendations

Sharing does not end with the presentation. Track each recommendation in the team’s backlog, check progress at regular reviews and report back on what changed. When a recommendation leads to a measurable improvement, share that result too: it builds trust in research and makes stakeholders more eager for the next study. Storing findings in a searchable atomic research repository means they remain available long after the project ends.

Common mistakes when sharing research

• Leading with methodology instead of findings
• Sharing too late to affect the decision
• Using research jargon with business audiences
• Listing every finding with equal weight
• Giving recommendations without owners
• Sharing recordings without participant consent

Frequently asked questions

How long should a research summary be?

One page for most audiences, with links to the full findings and recordings for those who want detail.

How do we get stakeholders to act on research?

Involve them early, invite them to observe sessions, and link every finding to a clear recommendation and owner.

Should we share raw recordings?

Share short, consented clips. Full recordings should be stored securely with access limited to the team.

Who should present research findings?

Usually the researcher, ideally with a product or design partner who will act on the findings, so the audience sees a shared commitment.

How soon after research should we share findings?

Share a quick debrief of top findings within a day, and a fuller summary within a week, while the decisions are still open.

Related articles

• Atomic research: building a research repository that lasts
• How to measure user experience in your product
• Using AI tools in user research: what helps and what to avoid