Research

Research that doesn't change anything isn't research, it's reassurance

Research is only valuable when it leads to something. When it becomes a way to justify what's already been decided, it's just a more expensive form of confirmation.

Why the purpose of research matters as much as the method, and how to tell the difference between insight that changes decisions and output that just justifies them.

28 April 20255 min read

In short

Why the purpose of research matters as much as the method, and how to tell the difference between insight that changes decisions and output that just justifies them.

When research exists to justify rather than inform

I've been part of projects where the findings had no meaningful impact on the direction of the work. Not because the research was poorly done, but because the decision had already been made. The research existed to document that users had been considered, not to genuinely learn from them.

That of is very common. It looks responsible. It feels like due diligence. But it's fundamentally backwards — starting with a conclusion and finding the evidence to support it rather than starting with a question and being willing to follow where the answer .

Research that only confirms existing decisions doesn't move products forward. It just makes it harder to challenge them.

What useful research actually changes

The most valuable I've been involved in hasn't produced the answers the team expected. It's produced better questions. It's revealed that the problem being solved was the wrong one, that the journey didn't reflect how users actually thought, or that an assumption baked into the product for years wasn't holding up in practice.

Those moments are uncomfortable. They require rethinking things that already have momentum behind them. But they're where creates real value, because they change the product in ways that would never have happened otherwise.

Key takeaway

Research should challenge what the team thinks it knows, not confirm it.

How to tell the difference

There's a simple test. After a round of , ask: did anything change that wouldn't have changed without it? Did a decision get made differently? Did a get reconsidered? Did a journey get restructured based on what was learned? If the answer is no — if the work continued exactly as planned regardless of the findings — then the research wasn't research. It was reassurance.

That's not always the team's fault. Sometimes is brought in too late to influence anything. Sometimes the findings are interpreted too conservatively. Sometimes there isn't enough organisational appetite to change direction based on what users are showing. But in each of those cases, the research has been positioned wrong.

Why the purpose matters as much as the method

methods matter. How you recruit, how you moderate, how you analyse — all of it affects the quality of what you learn. But method without purpose produces better-quality reassurance. What makes research genuinely useful is the behind it: a real willingness to be wrong, to be surprised, and to change course when the evidence points in a different direction.

That's a harder thing to commit to than running a set of . But it's what separates that moves things forward from research that just fills a gap in the .

Written by Andy Scott

Strategic design, UX and digital transformation thinking from real projects.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20