Simplify your job search
Get 5+ job offers from top companies with 1 application
Get job offers

Make your Findings Effective: Choosing the Right Method to Present Research

Bull's eye photo (dartboard) by Aaron Sarauer

Image by Aaron Sarauer

As user researchers we have a common goal: to provide a crystal clear picture of our research. To that end, our presentation must be both believable and digestible for our audience; stakeholders need to quickly scan whereas developers require specific details in order to take action. Likewise, the medium we use to present our findings is important.

Conventional mediums such as Powerpoint or Word might work great in some situations, whereas other situations require unconventional ones such as spreadsheets, video, storyboards and/or sticky notes. To present our findings effectively it’s imperative that we correctly match all three: the audience, the medium, and message itself.

Understand your audience

Lego people photo by CJ Isherwood

Image by CJ Isherwood

Just as designers should understand for whom they design, so should researchers understand for whom they research. Be sure to ask the following questions before choosing a presentation method:

  • Who is your audience? What is their primary role? e.g. Designers/ Executives/ Marketing/ other User Researchers/ Programmers/Community, etc.
  • What is your relationship with this audience? Is it new or ongoing?
  • What is the industry of this project? e.g. Government, Health Care, Medicine, etc.
  • What is the development cycle into which this research will be adopted? e.g. Agile/ Hybrid/Waterfall

In my experience (which consists of new and repeat stakeholders, both designers and executives) providing an executive summary in an email that also includes a link to the entire report is well received.

Executive summary

An executive summary email is pretty easy to create. Just make sure to focus on the important details and avoid any research jargon–save that kind of stuff for your actual report! More generally, structure your email:

  1. Brief description about the goal, methodology and participant demographics
  2. Notable findings
  3. High and medium-level issues (in a bulleted list) together with participant quotes (recommended) or even video snippets.
  4. Task Success Ratings and Metrics Studied (if applicable)
  5. Recommendations and next steps (if applicable)

While working with larger audiences – such as the open source community – the approach is different, however. Larger audiences include a variety of roles with varying degrees of involvement. For them we provided a comprehensive report posted on the community website with the option for them to react in the comments.

Establish credibility

Before your results are taken seriously your credibility must be established. This is easier said than done, of course. One quick way to gain the favor of your audience is to present your research in a way that makes sense to them.

While working with new stakeholders or stakeholders who are not familiar with user experience, a traditional report (PowerPoint, Text report) works well. Executives might not have the time to read an entire report but it’s reassuring to them (thereby, adding to your credibility) that the information is available to them. Over time, stakeholders may have more confidence in your data. Ask them about the effectiveness of your presentation and then pivot your method accordingly.

Credibility is directly correlated with the trust stakeholders have in your research methods, you as a person and user-centered design more generally. It is important that we act prudently in this regard, not just for ourselves but for our profession as a whole.

Manage expectations

Time is also an important factor affecting our presentation, as user research projects can range anywhere from just a few hours to a few months. Regardless, we must ensure that the information we’re after is delivered in a timely fashion to help the project succeed!

Manage the expectations of your stakeholders by informing them that the presentation of your findings affects your overall turnaround time. In agile environments, for example, writing a report is often considered wasteful as the time spent can delay the team from pivoting. As such, many researchers consider rather unconventional approaches: a compact, bulleted list, a high level summary via email (see above), or a quick conference call. Any of these can provide enough information to jump start productive solutions. In all cases, though, be sure to inform your stakeholders about your choice of medium beforehand in order to establish/retain trust.

These sort of lightweight approaches usually work well when a researcher is accessible to the team on a day-to-day basis (especially when dealing with prototypes). However, when the user researcher is an external resource, it’s recommended that they invest the time to generate a report, providing as must information as possible. That way the client can revisit their findings, in totality, at a later date.

Track progress transparently

Train tracks photo by Eirik Refsdal

Image by Eirik Refsdal

Finally, issue tracking is an invaluable asset as it not only provides visibility into the state of a product’s usability but also aides in decision making. A spreadsheet log of issues can be effective enough for smaller projects. For bigger projects, there are other available such as Sifterapp, JIRA, Lighthouseapp or even a home-grown application. Choose your issue tracking solution based on a project’s complexity and shelf life.

Over time, analyze the impact of issue tracking data to seek patterns. Tracking number of urgent/ high issues per feature will make it easier to prioritize and to focus. It is also a great way to validate design changes. For live features, higher tracking is recommended whereas for iterative prototypes less tracking could work.

In all cases, it’s important that issue tracking be done transparently. Sharing your ongoing findings with the wider organization is useful in evangelizing usability and raising awareness about the concerns within a product. Consider creating a central platform to share your findings (especially with the option to comment). Sharable documents (like google docs) or an intranet are good places to start.

Take it the next level

With the significant overlap of pointers and variables, it’s difficult to have a one-size-fits all solution to the problem. However, by considering our audience, our medium and our message together we can make better choices with regards to how we present our research.

Certainly, I’ve only scratched the surface here. How do you present your findings?

The author wishes to thank Lisa Rex and Jeff Noyes for their feedback on this article.

About the Author

Dharmesh Mistry

Dharmesh is passionate about open source, user experience and design. He works as a usability specialist for Acquia, a start up in the Greater Boston area and Drupal, the open source content management system. He is also the co-organizer of Boston Design Jam and active within the UX and Drupal communities. He has degrees in Computer Science engineering (University of Mumbai) and Human Factors in Information Design (Bentley University).


  • Nick from NZ Reply

    Good points Dharmesh, … I agree, sometimes a report is the most appropriate deliverable, but increasingly I’m finding visuals to be much more accessible and engaging for my clients. .. not to mention the amount of discussion they generate when they are not too detailed.

    I explain in some more detail with examples here:

    Take it easy with those bullet points!

    • Dharmesh Mistry Reply

      Thank you, Nick.

      That is a great way to present the findings. It looks pretty cool. Is there a particular audience that prefers the visual report more than the others?

  • Kok Chiann Reply

    Nice points, I was hoping for more detail in the exact methods of presenting your research outcomes other than a text-based report.

    Personally I have found text-based reports highly ineffective when it comes to stakeholders who are non-technical, that’s when the use of visuals provide better clarity and confidence, whether its in the form of diagrams, prototypes, accompanied by detailed documentation if necessary.

    For presenting solutions to research on complex systems, I believe journey maps could prove useful:

    • Dharmesh Mistry Reply

      If you find the text based reports are ineffective in your organization, try making your reports more visual and engaging. PowerPoint slides and Visual reports (like the ones posted by Nick) are good places to start. In the Powerpoint slides, I try to use bullet points and be concise. Also, going through your findings in a meeting can increase the engagement.

      You mentioned that you were looking for more details. What kind of details were you expecting? May be, I can offer some suggestions.

  • Navigator Multimedia Reply

    Thanks, Dharmesh!
    I find it’s best when clients can come into the office for a meeting and have their user research results delivered through a charismatic presentation. Clarifications can be made, and details can be explained in “live” terms, where it’s a person-to-person report. When possible, this is a great way to go!

    Sarah Bauer
    Navigator Multimedia

  • Dharmesh Mistry Reply

    I absolutely agree with you. Supplementing findings with a meeting goes long way.

  • AAGT Business Web Hosting Reply

    When presenting research it is important to know how to connect to your audience. If you have great research, but the findings are not interesting to your audience then who will read it.

  • Edrian Reply

    I agree that reports with lots of information can be difficult for people to digest without the use of visual charts. It is even better if you can connect with your audience in person to create an engaging presentation. You can get immediate verbal feedback and you can also read people’s body language.

  • Wilco Vogt Reply

    This article gave me some good tips for my current research project, i enjoyed reading it. However i have one comment. In the last paragrahp under the header “Manage Expectations” you write “..providing as must information as possible.” I believe must should be replaced with much.

    If this is not the correct place to address these issues i apologize.

Leave a Comment on This Article