This video discusses best practices for presenting and incorporating the results of your user experience research into the design and development process, including research report best practices and suggestions for incorporating results into team discussions and using emotion to make connections.
- [Voiceover] Once you've analyzed your research and come up with the key takeaways and suggestions, your biggest task is to share your insights and ensure that your recommendations are actually implemented. After all, research doesn't matter if you don't use the information. To share learnings, find a format that will work for your particular team. If you're embedded on a development team, you may be able to include the team in the process of performing and analyzing research, and therefore, you can share knowledge in ongoing discussions. You'll also want to record key findings in a shared team wiki document, or even on a whiteboard, and keep some sort of documentation of the main study details, such as what interface was tested, or who was interviewed.
While it may not be necessary for sharing the current findings, there are often times that you may want to revisit previous research, and it's much easier to record a small amount of data as you go, rather than trying to remember or recreate after the fact. If you're acting as a consultant or not fully embedded in a team, you're likely going to need to write a formal report recording all the details of your methodology and findings. I strongly recommend creating an executive summary of key information and findings, because most people will not have time to read lengthy reports.
In the body of the report, include a mixture of visuals and text to appeal to the different ways that people best learn and interpret data. For instance, if you created a matrix to distill your insights, you can take a picture or create a digital version to include in the report. If you usability tested a prototype, take screenshots of the prototype, and highlight key areas of interest, or video clips of the participants actually interacting with it. You can also create a simple spreadsheet of findings and recommendations to give readers a quick way to visualize highlighted takeaways.
I've included a test report sample in the exercise files that you can use as a starting point. You'll also want to include any particular relevant or emotional quotes or screenshots of participants' faces if you can. Incorporating the emotional responses of the people behind the findings helps team members connect the research to a broader context. The more you can get each member of your team, from engineers to business stakeholders, to understand and empathize with end users, the easier it will be to get them to incorporate your findings. In your report, you can also link to the research plans, related sites, or summaries of previous research.
While a report is useful as a summary deliverable and to document findings, I also implore you not to let a report be your only method of sharing findings. Regardless of your relationship with the project team, one of the most effective ways to share your research findings is to schedule a whole team discussion of takeaways and their implications. Whether you're an embedded member of the team, who will only be writing notes, or a consultant who will be providing a polished report, take at least 30 minutes to go through each of the key insights you uncovered.
Discuss what you observed, why it matters to the team, and what the team should do. As an example, if you found a key usability study in a checkout flow of an e-commerce page, you wouldn't just say, "It's difficult "for users to enter their credit card information." Instead, you'd say something like this: "It's difficult for customers to enter their "credit card, because we ask for the date "in a format that doesn't match "the way they see it on their card. "Many participants get frustrated at this point "and drop out, which results in abandoned "sales and a large potential loss for the company.
"We should tweak the form so that "the date selector matches what "customers see on their cards." However you decide to document results, keep in mind that the most important thing you need to do with your data is connect it to the broader context of the business. You also really need to help people understand why it matters, and what they should do about it.
This course introduces the fundamentals of user experience research so that anyone can understand the benefits and start integrating research into their everyday design and development process. Start watching to learn how to use UX research to find the answers to the most basic questions about your customers—who, what, when, why, and how—and drive better user experiences and business outcomes.
- An overview of research methods, including usability testing, interviewing, eye tracking, surveys, and many more
- A review of the main types of research, including quantitative and qualitative, behavioral and attitudinal, and moderated vs. unmoderated
- Determining the right methodologies based on organizational environment, client type, and project stage
- Targeting the right research participants
- Crafting the right questions in the right way
- Analyzing and presenting your data