Menu

Research

What stakeholders think research is vs what it actually is

Stakeholders often expect research to give them certainty. What it actually gives them is understanding.

Why research is often treated like a task with neat answers, when its real value is in changing how teams understand the problem.

02 April 20254 min read

In short

Why research is often treated like a task with neat answers, when its real value is in changing how teams understand the problem.

Why teams frame research the wrong way

For them, was something you ran. You recruit a set number of users, schedule , ask questions, and at the end you get a set of findings. A step in the : a phase, a deliverable, something you complete before moving into design.

gets scoped like a task. Five users, ten users, a week of , a report at the end. There's a start point, an end point, and an expectation that once it's done, the answers are there. It feels controlled. It feels predictable.

The framing is inherited from other kinds of work, and it is not unreasonable. Most things a team commissions do have a defined scope and a deliverable at the end. is scoped the same way because that is how the organisation buys things, and the shape does not quite fit what it is buying.

Stakeholders often expect research to reduce ambiguity. In reality, good research usually reshapes how they understand the problem first.

What actually happens when research starts working

On that same project, once we got into the , things started to shift almost immediately. Users weren't behaving the way the team expected. They weren't following the journeys in the same order, they weren't interpreting things in the same way, and they were getting stuck in places no one had flagged internally. After two or three sessions, it was already clear that the original assumptions didn't hold up. The question of how many users do we need became irrelevant. The question changed to: what are we actually learning here?

This is why the number is the wrong thing to fix in advance. If the first three all break the same assumption, the useful next move is to change what you are asking, not to complete the remaining seven for . matters for measuring how common something is. It matters much less for finding out that it exists.

Key takeaway

The real question in research is rarely how many users you need. It is what you are actually learning and how it changes the problem.

What stakeholders expect vs what research gives you

What often expect is certainty: clear answers, clear problems, clear next steps, something that reduces ambiguity and makes decisions easier. What actually gives you is understanding. And that often comes with more nuance than people expect.

I've been in situations where early findings made things feel less clear, not more. Where a simple problem turned out to have multiple layers. Where different users approached the same journey in completely different ways. That can feel uncomfortable if you're expecting a clean answer. But that's where the value is.

Naming this at the start helps more than defending it afterwards. Saying plainly that the first round is likely to complicate the picture before it simplifies it sets a very different expectation from promising answers by Friday, and it makes the uncomfortable findings easier to hear when they arrive.

It also changes who needs to be in the room. If the output is understanding rather than a document, the people who will act on it have to see some of it first-hand. A summary read two weeks later never carries the same weight as watching one person struggle.

What research actually uncovers

On Travelbag work, the initial thinking was that users were dropping off because parts of the journey weren't clear enough. What actually came out was more subtle: users weren't just struggling with , they were losing at specific points, particularly when decisions started to carry more weight. It wasn't about making things easier to understand. It was about making the experience feel more trustworthy. That's a different problem entirely.

Good isn't a checklist and it doesn't wrap up neatly with a set of answers. The most valuable research creates movement. It changes how people think about the problem, shifts the conversation, challenges assumptions that felt settled. And that's usually where I spend most of my time, not just running , but helping teams interpret what they're seeing and understand what it means for the product.

That distinction between and comes up constantly, and the two need different fixes. A clarity problem is solved by better wording or better structure. A confidence problem is solved by evidence at the moment of doubt: what happens next, what it costs, whether it can be undone. Rewriting the copy does nothing for the second.

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.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer