{"id":12307,"date":"2025-07-18T08:23:17","date_gmt":"2025-07-18T07:23:17","guid":{"rendered":"https:\/\/www.uxdesigninstitute.com\/blog\/?p=12307"},"modified":"2025-07-18T08:25:29","modified_gmt":"2025-07-18T07:25:29","slug":"how-to-write-a-ux-research-report","status":"publish","type":"post","link":"https:\/\/www.uxdesigninstitute.com\/blog\/how-to-write-a-ux-research-report\/","title":{"rendered":"How to create the ideal UX research report: an actionable guide"},"content":{"rendered":"\n

What is a UX research report and why do you need one?<\/strong><\/h2>\n

UX research report, also known as a user research report, is a visually appealing document written in plain language that summarises all the hard work the user researcher(s) has done on the project. The document should include research questions, methods, insights, and recommendations taken from your study.\u00a0 While UX research should continue throughout the project, a majority of the research should be done early in the discovery phase of the process. And this is also when a UX research report should ideally be created, so UX and UI designers have something to go on before they get too far into the design process.<\/span><\/p>\n

UX research reports can take a couple of different formats. The most obvious of those is a written report, in the form of a PDF,\u00a0 which works especially well when you have a small group of stakeholders or are dealing with a geographically distributed network of team members. However, the other kind of UX research report is a presentation, in the form of slideshows or decks. Presentations work well if you\u2019re speaking to a large audience that\u2019s meeting together at the same time. You can also put these two together and do both, so no matter what type of team member or stakeholder you\u2019re dealing with, they\u2019ll understand your findings.\u00a0<\/span><\/p>\n

UX research reports are important because they alert your team and other stakeholders on your project to the valuable results of your work. If you can\u2019t communicate your results, it can\u2019t be used, and if it can\u2019t be used, all your efforts were for nothing. So make sure you can communicate your findings so you can align your whole team on user goals and needs, prioritise specific ideas for development, and provide user insights to inform decisions.<\/span><\/p>\n

What is the structure of a UX research report?<\/strong><\/h2>\n

While UX research is different for every project, there are some things that all UX research reports should have. They include:<\/span><\/p>\n

Introduction<\/strong><\/h3>\n

Every research report should start with an introduction that explains the background of the project. This should include introducing the product or service you\u2019re designing for and an overview of your research.\u00a0<\/span><\/p>\n

Research goals<\/strong><\/h3>\n

This section should present any research questions and goals that guided your study. This can be as simple as understanding what users want from your product, but it gives an idea of what you\u2019re looking for in your research.\u00a0<\/span><\/p>\n

Methodology<\/strong><\/h3>\n

In this section, you should outline the various methodologies you used in your study, whether they\u2019re qualitative, such as user interviews, quantitative, such as online surveys, or both. Make sure you avoid professional jargon that your audience won\u2019t understand. Instead, try to present your methods in plain language so anyone can comprehend how your research was conducted.\u00a0<\/span><\/p>\n

Key findings<\/strong><\/h3>\n

This is the results section of your research report. Here, you simply lay out what you found without any additional commentary from you or any other expert.<\/span><\/p>\n

Recommendations<\/strong><\/h3>\n

This section should make recommendations and state takeaways that stakeholders can use in their designs. These recommendations and takeaways should use your findings from the previous section to come up with actionable insights, such as design changes or opportunities to bring in new users. You should also list limitations and where further research is needed here.<\/span><\/p>\n

Appendices<\/strong><\/h3>\n

Anything that wasn\u2019t represented in the body of the report should go into the appendices, including interview transcripts, surveys, and anything else that was an artifact of your study. Providing it here can allow interested parties to access it, but allows everyone else to ignore it.<\/span><\/p>\n\n\n\n
\n\t
\n\t\t
\n\t\t\t
\n \n

[GET CERTIFIED IN USER RESEARCH]<\/p>\n Take our Professional Certificate in User Research<\/span>\n <\/a>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n<\/section>\n<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

How to write an effective UX research report (step-by-step)<\/strong><\/h2>\n

Now that you know the major parts of a research report, you can get to writing with these key steps:\u00a0<\/span><\/p>\n

Define your goals and objectives<\/strong><\/h3>\n

You should define for your stakeholders what your research goals were, and for you too. After all, while stakeholders will be interested, this should also remind you what your objectives were for doing this research. You should define your goals even before you\u2019ve started your research, and in your report,you should reiterate what goals you decided on. This should lead to a more focused research report.\u00a0<\/span><\/p>\n

Understand your audience<\/strong><\/h3>\n

Different segments of your audience will have different needs when it comes to your report. Addressing designers and developers is different from addressing marketers or executives, for example. So you\u2019ll want to consider who your report will be read by and tailor your information to them.\u00a0<\/span><\/p>\n

You may need to create a report with the basic information for stakeholders with no experience with UX, and include appendices with additional information for those on your team. Alternatively, you\u2019ll want to give different presentations highlighting different information to various groups of stakeholders. Either way, you must ensure that your message is communicated effectively so those reading or listening to your report can act upon it.<\/span><\/p>\n

Summarise your research<\/strong><\/h3>\n

You may want to include every detail of what you found in your research but that would be boring for your audience. So make sure you include only what\u2019s really important to your study by highlighting only the most salient details and findings. This should correspond to the research goals you set at the beginning of the report.<\/span><\/p>\n

Pay special attention to your findings<\/strong><\/h3>\n

Your key findings is the section that everyone will read, whether they understand research methods or not. So this section must be presented in a way that is easily understood by everyone you present your report to. Make sure your provide a summary of your findings and discuss them in relation to your research questions. Then include more technical aspects further down so UX designers can make use of them.<\/span><\/p>\n

Always provide recommendations<\/strong><\/h3>\n

It can be tempting to finish your report with your key findings and leave it at that. But if you do, you\u2019re depriving your audience of actionable items for the future. Make sure you discuss your recommendations based on the findings. For example, if you\u2019ve found that users can\u2019t find the search box on your site, you need to make specific recommendations about why this is the case and what you think the designers should do to remedy the situation.\u00a0<\/span><\/p>\n

State your limitations<\/strong><\/h3>\n

No single study can address every single need of your users. At some point, you will encounter limitations, such as money or time. So as an addendum to your recommendations, you should acknowledge your research limitations and recommend future research to address these.<\/span><\/p>\n

UX research report best practices<\/strong><\/h2>\n

Here are some tips that will help you polish up your UX research report and make sure it\u2019s impactful and effective:<\/span><\/p>\n

Use clear, consistent language and avoid jargon<\/strong><\/h3>\n

In your research report, you should use plain language with a consistent voice and tone. That means even if you have multiple people working on a report, your language shouldn\u2019t change, so make sure you assign a single editor who can ensure this.<\/span><\/p>\n

Avoiding jargon is important, too. While some technical language may be included if your readers will understand it, it\u2019s important to make sure things are stated plainly or that technical jargon is defined in a glossary in the report.<\/span><\/p>\n

Tell a story<\/strong><\/h3>\n

Instead of throwing raw facts and figures at your audience, make a story of your research. Turn your research into a case study with a beginning (introduction and research questions), middle (methodology and findings), and end (recommendations). This is an easy way to have the information you present be more engaging.<\/span><\/p>\n

Put in user feedback<\/strong><\/h3>\n

Include illustrative quotes from users in the findings section if you have them. They can drive home your results and prove your point.<\/span><\/p>\n

Include effective images<\/strong><\/h3>\n

While we\u2019ve largely focused on words here, don\u2019t forget about including images, such as schematics, charts, graphs, and illustrations in your report. These are a powerful way to make your quantitative and qualitative results more exciting and interesting. Plus, illustrations can make anything in your report more accessible. So, make sure you pay adequate attention to your images.<\/span><\/p>\n

Make the report visually pleasing<\/strong><\/h3>\n

Your research report should be pleasing to the eye. Use colors, images, and textual hierarchy to make sure your report is as visually pleasing as possible. If needed, someone from the UI team should be able to help you bring the principles of document design to your report.<\/span><\/p>\n

Include a table of contents for easy navigation<\/strong><\/h3>\n

There is no standard length for a research report, but if it\u2019s going to be over 20 or so pages, you should include a table of contents with anchor links to different sections of the report. That way, your readers can easily get to the sections that matter most to them.<\/span><\/p>\n

What next? Presenting and sharing your UX research report for maximum impact<\/strong><\/h2>\n

There are several ways to present and share your results to your team and stakeholders. Here are the most popular:<\/span><\/p>\n

Share a document<\/strong><\/h3>\n

This means distributing your document via email as a PDF or Word doc. This can include all kinds of results at different levels of detail for different results; however, it also means many people in your audience won\u2019t read it. So while this is a good first step, it shouldn\u2019t be the only thing you do.<\/span><\/p>\n

Presenting your research live<\/strong><\/h3>\n

This is the best way to make your results impactful. They should provide a thorough idea of your research in plain language. Though you can present your research in person or remotely, you should do your best to schedule a time when all stakeholders can attend, or hold different meetings for different stakeholders.\u00a0<\/span><\/p>\n

You can also record and make your presentation available to anyone to watch asynchronously, but this isn\u2019t the best solution.<\/span><\/p>\n

Workshops\u00a0<\/strong><\/h3>\n

Workshops are an interactive way of presenting your research. They can be held remotely or in person, but either way, everyone should have access to the tools you\u2019ll use, whether pen and paper or digital tools. In a workshop, you and your audience will collaborate on putting a UX research report together from the data you\u2019ve gathered. This is great for ensuring you don\u2019t get too trapped in your own point of view but could lead to bandwagon jumping by your audience.<\/span><\/p>\n

Writing an effective UX research report: the takeaway<\/strong><\/h2>\n

A UX research report is a document that summarises all stakeholders and team members need to know about a research project. This document should be clear and to the point while still including everything your team members need to understand your study. You should include written data, user feedback, and visuals, including graphs, charts, and illustrations, to make the research report as interesting as possible, and share your results as either a written report or a presentation \u2014 or, ideally, both! Make sure you present your actionable insights in a compelling report so your stakeholders can understand and take advantage of the knowledge you\u2019ve gained.<\/span><\/p>\n

If you\u2019d like to learn more about user research, including how to plan, execute, analyse and communicate user research effectively, take UX Design Institute\u2019s university credit-rated <\/span>Professional Certificate in User Research<\/span><\/a>.\u00a0<\/span><\/p>\n

Or if you\u2019d like to read more about user research, take a look at these articles: <\/span>The importance of user research in UX design<\/span><\/a>, <\/span>Analysing UX research and sythesising results into valuable insights<\/span><\/a>, and <\/span>How to choose the right user research technique for your design project<\/span><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

If you\u2019re a UX researcher or UX designer who also does user research, you know all about qualitative and quantitative studies. But how do you communicate those findings to your team and other stakeholders? The answer is you create a research report, and this guide will tell you how. <\/p>\n","protected":false},"author":35,"featured_media":12311,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[273,391],"tags":[352,392,356],"class_list":["post-12307","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to-guides","category-ux-research","tag-user-research","tag-user-research-report","tag-ux-research"],"_links":{"self":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/12307","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/users\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/comments?post=12307"}],"version-history":[{"count":3,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/12307\/revisions"}],"predecessor-version":[{"id":12325,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/12307\/revisions\/12325"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/media\/12311"}],"wp:attachment":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/media?parent=12307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/categories?post=12307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/tags?post=12307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}