Research isn't cheap. A properly run qualitative study — recruiting, incentives, researcher time, note-taking, synthesis, readout — runs anywhere from $10,000 to $50,000 when you account for fully-loaded costs. Enterprise teams running moderated studies with specialized audiences can spend considerably more.

Now consider what happens when a team re-runs a study they already ran.

That's not $10,000 to $50,000 in research spend. That's $20,000 to $100,000 — for findings that, in many cases, are nearly identical to what the first study produced. Except this time, there's a fresh deck, fresh synthesis, and a fresh sense of confidence that came at a very stale price.

Even worse, what is the price you pay if the research team re-runs the study because they forgot they had already run it, but the customer DOES remember giving these answers before?

We've seen this happen. More than once. At more than one company. And the teams involved weren't being careless — they were being thorough. They wanted current data. They wanted to be rigorous.

The problem wasn't their intentions. The problem was that no one could find the original work.

When a research study ends, the artifacts scatter.

The Zoom recordings sit in a folder that requires a login that most people don't have. The notes live in a shared doc that hasn't been opened since the project closed. The synthesis is in a Miro board that made complete sense during the workshop and now reads like an ancient map with no legend. The findings are in a slide deck that was emailed to a distribution list on a Friday afternoon.

Six months later, someone has a new research question. They check the obvious places. They don't find anything definitive. So they start over.

This is the hidden cost — not just the money spent re-running studies, but everything that comes with it:

Time. A new study takes weeks from kick-off to readout. That's weeks of researchers', stakeholders', and participants' time. All of it spent to arrive somewhere the team has already been.

Momentum. The question that needed answering didn't get answered — it got deferred. Whatever decision was waiting on that research waited longer than it had to.

Credibility. Nothing erodes confidence in a research function faster than a stakeholder who discovers, mid-debrief, that this exact question was answered two quarters ago. The implicit message is devastating: we're not learning, we're just running studies.

Institutional knowledge. Every time research is re-run instead of retrieved, a team misses the chance to build on what it already knows. Insights that should compound are starting from zero instead.

The teams running repeated research aren't failing at research. They're often running excellent studies — rigorous, well-recruited, carefully synthesized.

They're failing at infrastructure. And in most organizations, no one is explicitly hired to fix it.

Research discoverability is a systems problem that gets misdiagnosed as a rigor problem. Teams respond by asking for better documentation, more consistent tagging, and more thorough readouts. All reasonable requests. None of them address the core issue: research artifacts are stored in disconnected tools with no shared taxonomy, no cross-project search, and no clear path from a research question to the work already done to answer it.

The question "didn't we already research this?" shouldn't require institutional memory to answer. It shouldn't require tracking down the researcher who ran the original study. It shouldn't require digging through three different project management tools and a shared drive.

It should have an answer that anyone on the team can find in under two minutes.

The individual cost of a repeated study is significant. The systemic cost is worse.

When research can't be found, it can't be built on. Teams don't just repeat studies — they repeat the same learning cycles, rediscover the same user frustrations, and redraw the same conclusions. The knowledge that should accumulate over years of research investment stays fragmented, inaccessible, and effectively invisible.

Meanwhile, teams wonder why their research program doesn't feel like it's moving the product forward: why insights don't seem to stick, why stakeholders keep asking for more research instead of acting on what already exists.

Research you can't find might as well not exist. And research that might as well not exist can't do what research is supposed to do: reduce uncertainty, sharpen decisions, and build a shared understanding of who you're building for.