Nobody Reads Your Research Report

Every UX researcher has done it.

Weeks of planning. Interviews. Analysis. Synthesis. Sticky notes covering digital whiteboards. Hours spent identifying patterns, grouping themes and extracting insights. Then comes the report. Thirty pages of findings, quotes, recommendations and carefully crafted observations.

It gets shared in Slack, presented in a meeting and quietly disappears into a folder that nobody opens again.

That might sound harsh, but I don't think it's particularly controversial. Most people working in product teams know that research reports rarely become widely read documents. Product managers skim them. Designers jump to the highlights. Stakeholders often want the conclusions without the journey that led there.

The uncomfortable truth is that the report was never the thing people actually needed.

For a long time, UX research has been closely tied to deliverables. Research reports, personas, journey maps and insight repositories became tangible evidence that research had happened. They helped teams document what they learned and gave researchers a way to communicate their findings. None of those things are inherently bad. The problem is that it's easy to start treating the deliverable as the outcome.

It isn't.

The goal of research isn't to produce documents. The goal of research is to improve decisions.

That might sound obvious, but I think it's a distinction many teams lose sight of. A beautifully written report can still have no impact. A comprehensive research study can still fail to influence a roadmap. Insights are only valuable if they change something.

The best researchers I've worked with understood this instinctively. They weren't obsessed with producing perfect reports. They were obsessed with making sure the right people understood the right things at the right time. They knew that research wasn't finished when the interviews ended or when the report was published. It was finished when the organisation acted on what had been learned.

That requires a very different skill set.

Research is often taught as a process of gathering evidence and communicating findings. In reality, a large part of the job is influence. It's understanding stakeholders, navigating priorities and helping teams make better decisions. The challenge isn't always discovering the truth. Quite often, it's helping people act on it.

This is something designers can relate to as well. We frequently mistake outputs for outcomes. Wireframes, prototypes, design systems and research reports all have value, but only if they contribute to a meaningful change. A design that never ships creates no impact. Research that never influences a decision creates no impact. The artefact itself is rarely the goal.

That's why I've become increasingly sceptical of measuring research success by what gets produced. The number of interviews conducted, the length of the report or the sophistication of the methodology can all be useful indicators, but they're not the thing that really matters.

The question worth asking is much simpler.

Did anybody make a different decision because of this work?

If the answer is yes, the research succeeded. If the answer is no, it probably doesn't matter how comprehensive the report was.

Maybe the problem isn't that nobody reads research reports. Maybe the problem is that we've been measuring the wrong thing all along.

The success of research isn't determined by how many pages are in the document or how detailed the findings are. It's determined by whether the work changes the direction of a product, challenges an assumption or helps a team make a better decision.

Everything else is documentation.