Five Questions That Tell You Whether Your Research Programme Is Delivering Value

Most leaders evaluate their research programme by asking how many studies the team completed last quarter. This tells you the team was busy. It tells you nothing about whether the work changed any decisions, whether the findings are accessible to anyone beyond the immediate audience, or whether the knowledge will still exist in twelve months. These five questions cut through the activity. You do not need a research background to ask them.

1. What decisions have changed because of research this quarter?

Not what was studied. Not what was found. What decisions were made differently because of what the research programme produced.

If the answer comes quickly with specifics, the programme is influencing the business. If the answer is a pause followed by "we shared the findings with the product team", you do not actually know whether the programme changed anything. Findings were produced. Whether anyone acted on them is a different question, and the fact that nobody is tracking it tells you everything.

Ask your team: "Show me the last five product or strategy decisions that were directly informed by research. Where is that connection documented?"

2. If someone asked what we know about a specific customer segment, how quickly could we answer?

Not from one study. From everything. Every piece of research the programme has conducted about that segment, synthesised into a coherent picture.

A mature programme can pull together cross-study knowledge about a topic in minutes because the findings are stored, tagged, and searchable. An immature programme has to reconstruct it from individual reports, slide decks, and whoever remembers working on that segment.

Ask your team: "Tell me everything we know about how [specific segment] behaves during [specific journey stage]. Use findings from the last two years." Time how long it takes and how many sources they have to search. That duration is the answer to this question.

3. How do we know we are not researching what has already been researched?

Research duplication is expensive and common. A new product manager joins, commissions a study on onboarding friction, and the team conducts interviews that produce findings nearly identical to a study completed fourteen months ago by a researcher who has since left.

The answer you want: "We have a searchable repository that anyone can query before commissioning new work."

The answer you probably have: "We try to remember" or "the team would know." That means duplication prevention depends on who is still around and what they recall.

Ask your team: "How many studies have we conducted in the last two years on [area you know has been researched repeatedly]? Show me all of them." If the answer requires asking multiple people or searching across several tools, the programme's history is not centralised. It is scattered.

4. If the head of research left tomorrow, what would we lose?

Every research programme has a person who holds the institutional knowledge. They know what was studied three years ago, why certain methods were chosen, which stakeholders trust the findings and which ones dismiss them. They are the programme's memory.

When that person leaves, the programme does not just lose headcount. It loses context that makes the findings interpretable. A report without context is data. The context is what makes it knowledge.

Ask your team: "Without speaking to anyone, show me a complete history of research in [product area] over the last two years, including findings, recommendations, and what happened as a result." If that requires the head of research to personally reconstruct it, the programme's knowledge is rented from an individual.

5. Are stakeholders commissioning research to learn, or to confirm?

This is the question nobody asks because the answer is uncomfortable. Some research is commissioned with genuine curiosity. Some is commissioned because a stakeholder has already decided what to build and wants evidence to support the decision. The research team usually knows the difference. They rarely say so.

Confirmation research is not useless, but it is not learning. And if a significant portion of the programme's output is confirmation work, the research function is being used as a validation service rather than a source of genuine insight.

Ask your team, privately: "In the last quarter, how many research briefs came with an implicit or explicit expected answer? How many were genuinely open questions?" If the team is uncomfortable answering, that is itself an answer.

What These Questions Reveal

If your team answered all five quickly with documented evidence, your programme is in strong shape.

If several answers required hedging, reconstruction, or long pauses, the programme is doing good work that is not structured in a way that makes it durable, searchable, or connected to decisions. The people are capable. The question is whether the infrastructure underneath them captures what they produce in a way that survives time, personnel changes, and the gap between a finding and the decision it should inform.

You do not need to understand research methodology to evaluate your programme. You just need to ask questions that can only be answered well if the right infrastructure exists underneath the work.