Present Stage in UX Research: Communicate Results (4/4)

Present Stage in UX Research: Communicate Results (4/4)

By Paulina ContrerasUpdated on 1 min read
UX Research Stages
View contents

We reach the fourth stage of the research process, here I share resources that have helped me in user research, organized according to each stage of UX Research.

Let's dive into that fourth stage – Presenting the results of the research process.

Stages and resources

Heritage Library

Presenting, finally! As important as the others is delivering the results of everything done in the previous stages. But it's not just about delivering or showing what you did or what the team did and goodbye. That's what I used to believe, that delivering work with clear, deep, user data-based findings was the end of the research cycle. But something I've learned is that the results delivery process is a relevant part where we reconnect with the team, now from the business side, and from there we collaborate to make the results a reality, where we must generate key conversations to bridge users and business, and make tangible the proposals generated from the findings. In that sense, we continue leading a process that started days or weeks ago with the initial proposal.

Some questions we should ask ourselves at this stage:

How do we get the conclusions and actionables understood? How do we give value to the work done? How do we present the data in a way that is useful and actionable? What information is relevant depending on my audience? With which team or person do I need to connect and generate collaborations to bring the research findings to life?

Adapt your message to the audience

Not everyone who sees your presentation is looking for the same thing. I've learned the hard way (yes, yawns in the middle of a meeting) that tailoring the message is key. Here's my "cheat sheet" for knowing what to deliver to whom:

AudienceCares aboutIdeal formatAvoid
ExecutivesROI, metrics, business impactExecutive summary (1 page)Boring methodological details
Product ManagersPrioritization, roadmap, "what we build"Impact/effort matrixAbstract research jargon
DesignersDetails, quotes, user pain points, contextPersonas, journey maps, videosJust cold numbers with no "soul"
DevelopersSpecs, edge cases, technical feasibilityTechnical documentation, ticketsAmbiguity or "floating" ideas

Structure of an effective UX Research report

After iterating with many formats, this is the structure that has worked best for me to hold attention and clarity:

  1. Executive Summary: (1 page maximum) What they need to know if they only read this.
  2. Context and objectives: Why did we do this? What did we want to answer?
  3. Methodology (very brief): What we did, with whom (N), and when. Without being boring.
  4. Key findings: (3-5 maximum) The headlines of the story.
  5. Insights and recommendations: The "so what?" and the "now what?".
  6. Next steps: What happens now?
  7. Appendices: All the detailed data, transcripts, and links for whoever wants to dive into the depths.

The art of actionable recommendations

A finding without a recommendation is just an anecdote. But a vague recommendation is a headache. Look at the difference:

  • ❌ Bad: "Improve the checkout process". (Ok... but how?)
  • ✅ Better: "Add a progress indicator in checkout to reduce abandonment". (Better, it already has a solution).
  • 🚀 Optimal: "Implement a 3-step progress bar in checkout. Estimated impact: 15% reduction in abandonment. Effort: 2 sprints." (Boom! Business language and clear action).

After presenting: ensuring action

The presentation isn't the end, it's the beginning of change. So your research doesn't die in a digital drawer:

  • Document agreements and owners: Who will do what and by when?
  • Follow up on implementation: Don't disappear. Support the team while they build the solution.
  • Measure the impact: Once launched, did it move the needle? That's your best card for the next study.
  • Create a repository: Save everything in a centralized place (like Dovetail or a well-organized Notion) so knowledge becomes cumulative.

These are resources that have been useful to me when thinking about proposals for this stage. Do you have others you'd like to add to the list?

Thanks for reading 🙂

Series Articles

Related Articles