Why "we need more research" is often the wrong answer

On the surface, it sounds responsible. If there's uncertainty, 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. But the team still felt stuck. Instead of moving forward, the conversation kept circling back to doing more research. Maybe they hadn't spoken to enough users. Maybe they needed a slightly different audience. It all sounded reasonable. But 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.

It is an unusually defensible thing to ask for, which is part of the problem. Nobody has ever been criticised for wanting to understand users better, so the requestglossary×RequestA request is an action sent from a client to a server asking for data or a service.Open glossary term→ passes without scrutiny in a way that proposing an actual direction would not.

There's a point in most projects where you stop learning new things and start hearing the same patternsglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.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.

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. By the end, 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.

Saturation is a useful thing to watch for and easy to miss when sessionsglossary×SessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term→ are booked in advance. If the last three have produced nothing you had not already heard, the remaining ones will most likely confirm the same patternglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term→, and the budget is better spent on doing something about it.

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, maybe even slightly incomplete, but it was enough to move forward. 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, uninterpreted information collected and stored so it can be analysed, processed, or used to inform decisions. On its own it carries no meaning; context and interpretation are what make it useful.Open glossary term→, real outcomes: not just what users said in a session, but what they actually did when it mattered. That's usually where the best insight comes from.

Shipping something also changes the quality of the question. A live change produces behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→ rather than opinion, at a scale no round 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→ can reach, and it tends to settle disagreements that months of discussion could not.

The condition is that it has to be small enough to reverse. Learning from what goes live works when the change can be pulled back cheaply. When the only available step is a full rebuild, the caution behind wanting more researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ is entirely reasonable.

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: the problem hasn't been clearly defined, so the research feels unfocused; the findings haven't been properly interpreted, so no one is confident in what they mean; or the team simply isn't ready to make a decision and research becomes a way of buying time.

Researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ is 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. Accept that you're not going to remove all uncertainty, and instead focus on reducing the biggest risks and moving forward. 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.

Naming which of the three is happening usually unblocks it faster than another round would. An unclear problem needs a workshop. Uninterpreted findings need an afternoon with the team and the transcripts. Reluctance to decide needs somebody with the authority to decide, and no amount of additional evidence will substitute for that.