A UX Research Report People Actually Read: Structure, Summary, and Recommendations
A UX research report matters only if someone acts on it. How to order findings, write a clear executive summary, and attach an owner and action to each finding.
What should a report include?
The reference guides propose similar structures. UX Design Institute suggests an introduction, research goals, business value, methodology, key findings, and recommendations (UX Design Institute, “Presenting UX research findings”). CleverX adds a cover page, a participant profile, and appendices (CleverX, “How to write a UX research report”). Koji groups everything into an executive summary, findings, visualizations, themes, recommendations, and a methodology appendix (Koji, “User research report”).
The practical version has five blocks: executive summary, goal and the decision it informs, method, findings with evidence, and recommendations with owners. Everything else goes into appendices: CleverX mentions the discussion guide, the screener criteria, and the raw coding notes. For the participant profile, it suggests a table with anonymized IDs (P1, P2…) instead of names.
Why should a designer care?
Because the report is the visible product of your research work. You can run ten excellent interviews and the team still changes nothing if the document is a long transcript. Research isn’t worth what you know; it’s worth what someone does afterwards.
A good report also protects you. If a decision goes wrong, you have a record of what was observed, with how many people, and what was recommended. If it goes right, you have an argument for the next budget round.
The report also shows that the research was done with method. When someone asks why you believe something, the answer should be in the methodology and the quotes, not in your memory of the session.
How do you write the executive summary?
It is the part that gets read most and the one most often neglected. Two rules appear in the guides:
- Write it last, but place it first. CleverX recommends drafting it once you have the findings, so it reflects the actual report.
- It has to stand on its own. Koji describes it as the section many people read without reaching the rest. It should include what was studied, three to five concrete findings, and one to three actions.
UX Design Institute approaches it from another angle: limit the report to three or four main insights. If you have twelve, you probably haven’t yet decided which ones matter.
How do you present each finding?
A finding has to be specific and backed by evidence. A practical structure:
- Headline. One sentence that says what happens, not the topic. “People looking for a time slot can’t find the location filter” is a headline; “Search” is not.
- Evidence. Two or three quotes or a metric. Koji suggests combining frequency with quotes: “11 of 14 participants…”.
- Implication. What it means for the product or the business.
- Recommendation. A concrete action, with an owner and a priority. CleverX suggests one recommendation per finding where possible.
Usability metrics give you frequency. User interviews give you quotes. Combining both is more persuasive than either alone.
Example
Illustrative example: a team runs six usability tests on appointment booking. The first draft is 27 pages, with one section per screen and a list of observations. The executive summary says “there were some navigation problems”. The version people use changes the focus. It has a half-page summary with three findings: five of six people can’t find how to change location, three confuse the confirm button with the save button, and the confirmation doesn’t say when the reminder will arrive. Each finding has two quotes, a recommendation, and an owner. The location change ships in the next sprint, and the team remembers it because the report says so on the first page.
When NOT to write a long report
- When the study is small and the decision is simple. Two well-written pages are enough.
- When the reader will see a presentation. You can write the full report and distill it into slides. CleverX proposes that order so the detailed evidence isn’t lost.
- When the audience has no decisions to make. Without a decision-maker, the document is more archive than research. Ask first what will be decided with it.
Common mistakes
- Starting with the methodology and burying the main finding.
- Summarizing transcripts instead of analyzing them.
- Including every observation without prioritizing.
- Recommending without saying who does what.
- Leaving out the study’s limitations, such as how many people took part and what their profile was.
- Delivering it after the decision has been made. A report that arrives late documents something nobody can change.
How to start tomorrow
Before you write the next report, write in one sentence the decision it informs. Then draft three findings with headline, evidence, and recommendation. Only when those three are clear, write the executive summary, and hand it to someone who didn’t take part in the study so they can read it without context. Ask them to tell you, in one sentence, what decision they would make with it. If they can’t answer, the summary isn’t finished, however well it is written. Rewrite it. If the recommendations depend on other areas, stakeholder management helps you assign owners before you present.