Most researchers assume their findings were ignored because the organisation wasn't ready.
That's a comfortable story.
It's also wrong.
Your research didn't get shelved because of timing, politics, or budget cycles.
It got shelved because it didn't give stakeholders what they came for.
They didn't come to learn. They came to decide.
Stakeholders sit in research readouts for one reason: they have a decision to make, and they're hoping your work makes it easier.
The moment you walk them through methodology, sample sizes, and thematic coding - you've lost them.
Not because they're lazy. Because none of that answers the question they walked in with.
They don't need to understand how you got there. They need to know what to do next.
This is the gap nobody talks about. And it's why research that's brilliant still ends up ignored.
The best readouts start at the end. Not "here's what we did." But "here's what this means for the decision you're facing."
That one shift changes everything.
You're no longer presenting findings. You're delivering a recommendation with evidence behind it.
That's not the same thing.
Findings are passive. They sit there. They require interpretation.
Recommendations are active. They prompt a response. They force a position.
Your job isn't to hand over the data and step back. It's to walk into the room with a point of view - and be prepared to defend it.
The three reasons research gets shelved
In my experience, it comes down to one of three things.
- The insight is framed around the research, not the decision. You've presented what you found. But not what it means for the thing they're weighing up. Without that bridge, they have to do the interpretive work themselves. Most won't.
- The recommendation is missing. You've given them information. You haven't given them a position. Stakeholders don't want to interpret findings - they want to know what you think they should do, and why. The absence of a recommendation reads as uncertainty. And uncertainty makes people wait.
- The timing is off. Research delivered after the decision has already been made informally is useful for confirmation, not direction. By then, changing course feels like backing down. The window has closed before you've even opened the deck.
Fix any one of these, and your research starts to land differently.
Fix all three, and you become someone they want in the room before the brief is even written.
Three questions before you present
Before your next readout, answer these on paper:
- What decision does this research make easier?
- What would I recommend, and why?
- What's the one thing I want them to do differently as a result of this work?
If you can't answer all three, your research isn't ready to present. It's ready to be refined.
The analysis is one step. Translating it into decision language is another.
Most researchers stop before the second step. The ones who get invited back don't.
What changes when research lands
When stakeholders act on your work, something shifts.
You stop being the person who delivers reports.
You start being the person who changes what gets decided.
That's the difference between a researcher who's respected and a researcher who's valued.
Respect is about outputs - rigorous methodology, clean analysis, well-structured findings.
Value is about outcomes - decisions made differently because of what you uncovered.
Research that doesn't change a decision has a value of zero. Not because it was bad research. Because it never connected to the thing it was supposed to move.
That's the uncomfortable truth worth sitting with before your next project even starts.
The question isn't "did they read it?"
The question is "did anything change?"
Research that drives decisions, not discussions.
~ JP
Related from ResearchGeek
Share this issue
