Why Your UX Research Isn’t Landing (and How to Fix It)

The Report Nobody Acted On

“To me, the biggest insult as a researcher is when people read a report and they say, mm, interesting” 1. That is Tomer Sharon, in a talk at Google on the failure of traditional research reports, describing the most common outcome of the job: a deck circulated, a few people skimming it, one word of acknowledgment in a planning meeting, and a roadmap that comes out the other side unchanged.

Teams in that position often blame the sample size, the method, or the writing. The findings were accurate. They were never attached to anything anyone had to decide, so there was nothing for a stakeholder to do with them except agree.

Erika Hall, whose writing on design research has shaped how a generation of practitioners think about the discipline, frames the purpose of asking questions as establishing a shared framework for making decisions so a team can make better decisions faster 2. Research that informs changes how a team thinks about a problem. Research that is merely interesting ends its life as a document.

The Trouble With Long Lists

A list of twenty usability issues, every one of them real and documented, gives a stakeholder with an hour of decision time no entry point. Nothing in it signals which two items would move a quarterly number and which eighteen are minor annoyances, so the reader is left to do the ranking the researcher was better placed to do.

The same pattern shows up outside product teams. Peer-reviewed work on knowledge translation, the field that studies why evidence does or does not reach the people who act on it, records that decision makers are under increasing pressure to ensure their decisions are evidence-based while facing significant identified barriers to doing so, and that targeted messages show potential for increasing research utilization 3. Targeting is the variable the researcher controls.

Hindsight bias is a second condition worth designing around. Once a finding is revealed without being anchored to a pending decision, an audience reconstructs it as something already obvious. One analysis of the effect in UX contexts describes how, after research surfaces a problem, “stakeholders might unconsciously revise their knowledge to make the result seem obvious and themselves seem prescient” 4. The same analysis points to collecting predictions in advance: if a team member forecasts that five of ten users will complete a task easily and all ten struggle, the gap is on record before the findings land 4.

Ranking by Impact

The structural fix is scoring. Jakob Jakob Nielsen’s severity rating method, published by Nielsen Norman Group (a UX consultancy that sells training and research services), scores each usability problem on a 0 to 4 scale built from frequency, impact, and persistence. The stated purpose is that severity ratings “can be used to allocate the most resources to fix the most serious problems” 5. The same consultancy, which has a commercial interest in UX methodology becoming standard practice, also publishes guidance on prioritization matrices: two-dimensional plots that rank items against two weighted criteria such as user impact and available budget 6.

Ranking gives a researcher something to say in a single meeting: these three findings out of thirty deserve engineering time this quarter, and here is the basis for that ordering. It also makes the ordering contestable in a productive way, since a stakeholder who disagrees has to argue about frequency or impact rather than about taste.

A Recommendation for Every Finding

An ordered list still leaves work on the reader. A sentence reporting that users struggled with the required field on step two is an observation. A line instructing the onboarding team to remove that field is a decision someone can approve, defer, or reject.

Public-sector practice treats that pairing as mandatory rather than stylistic. The GOV.UK Service Manual directs teams to identify not only what users do but what changes are needed in response, pairing each finding with a specific recommendation and an identified owner for implementation 7. US federal usability guidance published through Digital.gov covers reporting usability test results in similar terms, treating recommendations and prioritization as part of the report rather than a follow-up conversation 8. Sharon’s argument from the same talk is that if nobody is acting on the reports, the format itself is the thing to change 1.

One finding, one recommendation, one owner. Three fields close the gap between a document and a decision.

Built for the Audience Reading It

A format choice determines whether evidence is read at all, which makes it part of the research work itself, not a step that happens afterward. The International Development Research Centre, which funds research in low- and middle-income countries, builds tailored knowledge products such as policy briefs, videos, and digital storytelling into program design because different audiences take in evidence differently. Its stated aim is “to ensure that research findings are shared, interpreted and implemented by relevant stakeholders to improve decision-making, policies and outcomes” 9. GOV.UK guidance expects presentation to be matched to how stakeholders will actually use the information 7.

The comprehensive report serves the researcher’s own record and is worth keeping for that. The artifact that reaches a decision is usually shorter: a one-page brief, a ten-minute live readout, a two-minute clip of a user failing a task, or a single slide someone else can carry into their own meeting.

Four Steps to Make It Land

Name the live decision the research is meant to serve before a single session is scheduled, and write it at the top of the research plan so every finding arrives with a slot to fill. Where stakeholders have strong priors, ask them to record a prediction, which gives the readout a documented baseline.

Rank what comes back by combined user and business impact, using severity scoring or a prioritization matrix, and bring the scoring sheet so the ordering is defensible. Pair every surviving finding with one specific recommendation and a named owner, in a table a product manager can paste into a backlog without rewriting it.

Then build the deliverable around how that particular audience consumes information: a one-page brief for an executive who reads before meetings, a live readout for a team that argues things out loud, a short clip for anyone who needs to see the failure to believe it. The full report can still exist behind all of it.

Research that changes a product is designed for its readers with the same care the product is designed for its users. The next readout is a design problem. Treat it like one.

Spruce DX is the digital experience division of Spruce Technology, helping organizations design and build accessible, human-centered digital products.