What stakeholders think research is vs what it actually is

It wasn’t a bad question.

It just told me where their head was.

For them, researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ was something you ran.

You recruit a set number of users, schedule sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→, ask questions, and at the end you get a set of findings. Something you can present, share, and move on from.

A step in the processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→.

And to be fair, that’s how it often gets positioned.

A phase.

A deliverable.

Something you complete before moving into design.

I’ve seen this play out a lot.

Researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ gets scoped like a task. Five users, ten users, a week of sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→, 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.

But that’s not how it works.

On that same project, once we got into the sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→, things started to shift almost immediately.

Users weren’t behaving the way the team expected. They weren’t following the journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ 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 sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→, it was already clear that the original assumptions didn’t hold up.

At that point, the idea of how many users do we need became irrelevant.

The question changed to:

What are we actually learning here?

That’s the gap.

What stakeholdersglossary×StakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term→ often expect is certainty.

Clear answers.

Clear problems.

Clear next steps.

Something that reduces ambiguity and makes decisions easier.

What researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ 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 journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ in completely different ways.

Where something that looked like a usabilityglossary×UsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term→ issue was actually a mismatch between expectation and reality.

That can feel uncomfortable if you’re expecting a clean answer.

But that’s where the value is.

I saw this clearly on work like Travelbag.

The initial thinking was that users were dropping off because parts of the journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ weren’t clear enough. The expectation was that researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ would highlight those areas so they could be fixed.

What actually came out was more subtle.

Users weren’t just struggling with clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→. They were losing confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→ 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.

And I’ve seen it in more complex environmentsglossary×EnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term→ as well.

Across the NHS, the expectation was often that researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ would highlight usabilityglossary×UsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term→ issues within individual servicesglossary×ServiceA service is a component or function that performs a specific task within a system.Open glossary term→. What it exposed instead was inconsistency at a structural level. Different patterns, different approaches, different expectations depending on where users landed.

Again, not a simple fix.

That’s where researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ starts to diverge from what people expect it to be.

It’s not a checklist.

It’s not a box to tick.

And it’s not something that neatly wraps up with a set of answers.

In my experience, the most valuable researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ creates movement.

It changes how people think about the problem. It shifts the conversation. It challenges assumptions that felt settled.

Sometimes it simplifies things.

Sometimes it makes them more complex before they get better.

And that’s usually where I spend most of my time.

Not just running sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→, but helping teams interpret what they’re seeing and understand what it means for the product.

Because without that, researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ becomes something that’s done, rather than something that’s used.

The expectation is that researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ gives you answers.

The reality is that it helps you ask better questions.

And the teams that understand that are usually the ones that get the most out of it.