Why “we need more research” is often the wrong answer

Things aren’t quite landing, there’s disagreement in the room, or no one feels confident enough to commit to a direction. The energy shifts slightly, decisions slow down, and researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ gets positioned as the safe next step.

On the surface, it sounds responsible. Thoughtful, even. If there’s uncertainty, the instinct is to go and gather more information, speak to more users, validate assumptions, and reduce risk before making a call.

But in my experience, that’s not always what’s actually happening.

I was working on a project where the team had already done a solid round of researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→. They’d spoken to users, identified key frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→ points, and had a fairly clear picture of where things were breaking down. The issues weren’t hidden. They were visible in both the dataglossary×DataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term→ and the sessions.

Users were dropping off at the same points. They were hesitating in the same places. They were expressing the same concerns.

Nothing about the problem was unclear.

But the team still felt stuck.

Instead of moving forward, the conversation kept circling back to doing more researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→. Maybe we hadn’t spoken to enough users. Maybe we needed a slightly different audience. Maybe we needed to test a few more variations before committing.

It all sounded reasonable.

But when you looked closer, it wasn’t about needing more insightglossary×InsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term→. It was about not being comfortable making a decision.

That’s the difference that’s easy to miss.

There’s a point in most projects where you stop learning new things and start hearing the same patternsglossary×PatternA reusable solution to a common design problem.Open glossary term→ repeated in slightly different ways. The signalsglossary×SignalsSignals are data points or triggers that indicate changes in user behaviour, context, or external factors.Open glossary term→ don’t get stronger, they just get louder. At that stage, more researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ doesn’t add clarity, it delays action.

And I’ve seen that delay become a patternglossary×PatternA reusable solution to a common design problem.Open glossary term→.

On one project, the team ran three separate rounds of researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ over a relatively short period of time. Each round confirmed broadly the same issues. The journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ were too long, key decisions weren’t supported properly, and users were losing confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→ at specific stages.

By the end of it, we didn’t have a better understanding of the problem.

We just had more evidence of something we already knew.

Nothing changed in the product during that time.

I’ve also seen the opposite.

Projects where the initial researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ was rougher, less polished, maybe even slightly incomplete, but it was enough to move forward. Enough to identify where to focus, where to test, where to start improving things.

That momentum made all the difference.

Because once changes started going live, the learning became far more valuable. Real behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→, real dataglossary×DataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term→, real outcomes. Not just what users said in a sessionglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→, but what they actually did when it mattered.

That’s usually where the best insightglossary×InsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term→ comes from.

I saw this quite clearly on work across the NHS.

There was no shortage of researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→. In fact, there was often too much of it, spread across different teams, different departments, and different initiatives. The challenge wasn’t a lack of understanding, it was fragmentation.

Everyone had a piece of the picture, but no one was moving decisively based on it.

At that point, the value didn’t come from doing more researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→. It came from consolidating what was already known and actually applying it.

And that’s where things tend to shift.

In my experience, we need more researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ is rarely about the research itself. It’s usually about one of three things.

Either the problem hasn’t been clearly defined, so the researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ feels unfocused. Or the findings haven’t been properly interpreted, so no one is confident in what they mean. Or, more often than not, the team simply isn’t ready to make a decision and research becomes a way of buying time.

That doesn’t mean researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ isn’t valuable. It is. It’s one of the most important tools we have.

But it only creates value when it leadsglossary×LeadA lead is a potential customer who has shown interest in a product or service, typically by providing contact information or engaging with content.Open glossary term→ to something.

There’s a point where you have to stop looking for perfect clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→ and start making informed decisions. Where you accept that you’re not going to remove all uncertainty, and instead focus on reducing the biggest risks and moving forward.

That’s where progress actually happens.

I tend to think of researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ less as something you complete and more as something that runs alongside the product. You learn enough to move forward, you make changes, you observe what happens, and you refine from there.

It’s a continuous loop, not a gate.

Because if you wait until you feel completely certain, you’ll be waiting for a long time.

And in most cases, you already know more than you think you do.