Every design researcher I know has a version of this story.
You spend weeks on a project. The research is rigorous. The synthesis is clear. The insights are genuinely good, the kind that reframe the problem in a way that should change the direction of the work. You present it. People nod. They say useful things. And then the roadmap stays exactly as it was before you started.
The research sat in a deck somewhere and was never meaningfully acted on.
This is so common that there’s a slightly gallows-humour acceptance of it in research communities. But the acceptance is doing some damage, because it lets organisations off the hook for a failure that has real costs. When research doesn’t influence decisions, you’re paying for the research and paying for the downstream cost of decisions made without it. That’s an expensive inefficiency that most organisations haven’t properly accounted for.
The easier explanation is that people are resistant to evidence. That stakeholders are too attached to their existing plans, too politically invested in their prior decisions, too short-term in their thinking to change course based on what users say. This is sometimes true. It’s not the whole picture, and treating it as such keeps researchers in a passive relationship with the problem.
The more useful question is: what made this research ignorable?
There are several answers, and most of them are addressable.
The first is timing. Research that arrives after a decision has been made isn’t research that influences the decision. It’s research that either confirms it, if you’re lucky, or sits awkwardly alongside it if you’re not. The most common reason good research doesn’t land is that it arrives too late in the process to change anything structural.
This is partly on the organisations that don’t build research into the decision-making process early enough. But it’s also on researchers who accept being brought in at the wrong moment. If you’re being asked to do research to validate a decision rather than inform one, that’s a conversation worth having explicitly. Because the alternative is doing real work that you already know won’t change anything.
The second reason research gets ignored is that it’s not translated into decision language. Research speaks in user experience terms. Strategy speaks in business impact terms. When research stays in its own register, the people who need to act on it often don’t know how. They find the insights interesting in a vague way and don’t know what to do with them specifically.
The translation burden falls on researchers. Not because it’s fair, but because it’s effective. Taking a research insight and connecting it to a business metric, a prioritisation decision, a risk, a specific design implication, makes it much harder to file away. It becomes something that requires a response rather than something that informs the general understanding.
The third reason is that research often speaks to problems rather than directions. You’ve found what’s broken. What you haven’t provided is a sense of what better looks like. Leaders and product teams are trying to decide what to build next, and research that tells them what’s wrong without giving them anything to move toward is incomplete input.
Adding a forward-facing layer to research doesn’t mean being prescriptive. It means connecting the insight to a direction. “Users are struggling with X because of Y. That suggests the design priority should be somewhere in this space.” You’re not solving the design problem. You’re orienting the conversation toward what the problem requires.
None of these are research quality problems. They’re research positioning problems. Which means they’re solvable by the research practice without waiting for the organisation to change.
The researchers and research-led designers with the most impact are the ones who’ve accepted that generating insight is half the job. The other half is getting the insight into the room, in the right form, at the right moment, with enough context that acting on it becomes the obvious next step.
That’s not watering down the research. It’s completing it.
Research that changes nothing is, practically speaking, research that didn’t happen. The work matters too much to let it disappear into a deck.
