Signs Your Research Programme Is Producing Reports Nobody Uses

Research programmes can look productive while producing almost nothing that changes the business. Studies are completed. Reports are written. Debriefs are held. Decks are filed. And six months later, a product team makes a decision that directly contradicts findings the research team produced, because nobody knew the findings existed. This is not a quality problem. The research may be excellent. It is a connection problem. The work is being done but it is not reaching the decisions it should inform. Here are the signs.

1. The team measures itself by studies completed

If the primary success metric is how many studies were delivered, the programme is optimising for throughput. A programme that completes twenty studies a quarter and influences zero decisions is worth less than one that completes five and changes how the organisation thinks about its customers.

Ask: "Of the studies completed last quarter, how many directly led to a documented decision?" If nobody tracks this, volume is the only metric available. And it is the wrong one.

2. Findings are presented once and then filed

The debrief happens. The stakeholders nod. The deck goes into a shared drive. Nobody searches for it again.

Research has a shelf life, but it is longer than most programmes treat it. User behaviour findings from last year are still relevant today if the product has not fundamentally changed. But if findings are not stored in a searchable, structured way, they are functionally lost the moment the debrief ends.

Ask: "How would a product manager find every research study relevant to a feature area they are working on, without asking the research team?" If the answer is "they would need to ask us", the research is not accessible. It is guarded, and probably not intentionally.

3. The same questions keep getting researched

Different stakeholders, different quarters, same fundamental question. "Why do users drop off during onboarding?" gets studied, answered, filed, forgotten, and studied again eighteen months later by a different researcher working from a different brief.

Ask: "Has this topic been researched before?" for three current or planned studies. If the answer to any of them is "I'm not sure" or takes more than a few minutes to verify, the programme does not have a reliable way to check its own history.

4. Stakeholders commission research but do not attend the debrief

When the person who requested the research does not show up for the findings, the research was either not important enough to warrant their attention or they have already made the decision it was meant to inform. Neither is a good sign.

Ask: "Of the last ten debriefs, how many were attended by the stakeholder who commissioned the study?" If attendance is below 70%, the programme's work is being requested out of habit or obligation rather than genuine need.

5. Nobody can tell you what the programme learned last year

Individual study findings exist somewhere. But when you ask for the synthesised picture, the patterns, the accumulated understanding of how your customers behave, the answer requires assembly.

If the knowledge has to be reconstructed rather than retrieved, it is not stored in any structured way.

Ask: "What are the three most important things we have learned about our customers through research in the last twelve months?" Time how long the answer takes.

6. Research and experimentation operate in separate worlds

The research team studies user behaviour. The experimentation team tests changes. The two produce complementary evidence but rarely reference each other's work.

Ask: "When was the last time an experiment brief cited a research finding, or a research study referenced experiment results?" If the connection is rare or non-existent, two evidence-producing functions are operating in parallel without building on each other.

7. The programme cannot make a budget case with specifics

When budget conversations arrive, the team struggles to quantify impact. "We conducted fifteen studies and presented findings to six teams" is activity, not impact.

Ask: "If I had to defend this programme's budget to the board next week, what evidence would you give me?" If the answer takes days to assemble, the programme's value is real but undocumented.

What to Do About It

If several of these signs are present, the instinct is to question the team. Resist that. The researchers are almost certainly doing good work. The problem is that the programme lacks the infrastructure to make that work findable, connected, and durable.