A searchable library of past research, so insights compound instead of evaporating. Without one, the same study gets run three times and decisions ignore evidence that already exists.
▸ Try the interactive toolA research repository is a centralised, searchable library of past research — interviews, surveys, usability tests, analytics insights, and experiment results. Without one, research is redone repeatedly, insights are lost, and decisions get made without the evidence that already exists somewhere in the organisation.
The repository's value is that it makes research compound instead of evaporate. Each study adds to a searchable base that future questions can draw on, so the team builds cumulative understanding rather than starting from scratch each time. The discipline is that insights must be findable — tagged, structured, and searchable — not just stored. A folder of unsorted research documents is technically a repository and practically useless.
Centralised (one place, not scattered) + searchable (tagged and structured, not a document dump) + consistent (insights in a standard shape) + maintained (kept current). Findable, not just stored.
Research that isn't findable might as well not exist — and the cost is paid over and over as teams re-run studies and ignore evidence they already have.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Research evaporates | Insights live in one person's memory or a lost doc, then vanish. | A repository preserves and compounds them over time. |
| Redone studies | The same question gets researched repeatedly at full cost. | A searchable base lets teams check existing evidence first. |
| Decisions ignore evidence | Choices made without research that already exists somewhere. | Findable insights inform decisions that would otherwise guess. |
| Stored but not findable | A folder dump is technically saved, practically lost. | Tagging and structure make insights actually retrievable. |
Pick one home for all research and commit to it. Scattered insights across tools and drives are the default failure — one searchable location is the foundation.
Use the insight-statement format (Tool 21) so entries are comparable and skimmable. Consistency is what lets someone find and trust an insight months later.
Tag by topic, segment, product area, method, and date so future questions can find relevant past work. Untagged research is unfindable research.
A repository only compounds if entries keep coming. Build it into the discovery rhythm so logging research is routine, not an afterthought that never happens.
The payoff step: before commissioning a study, check whether the answer (or part of it) already exists. This is what turns the repository from an archive into a time-saver.
A team spent weeks researching a user question, confident it was new ground. Late in the process someone recalled that a similar study had been done a year earlier — the findings existed, but in a slide deck nobody could locate, effectively lost.
Most of the new study had re-discovered what the organisation already knew. With a searchable repository and a habit of checking it first, the team could have started from the prior findings and spent their weeks extending them rather than repeating them. The cost of the missing repository wasn't abstract — it was weeks of duplicated work and a decision delayed.
The deliverable is a centralised, tagged, consistently-formatted library that the team searches before starting new research.
| A pile of docs | A real repository |
|---|---|
| Scattered across tools | Centralised in one place |
| Inconsistent formats | Standard insight statements |
| Untagged | Tagged for retrieval |
| Write-only | Searched before new research |
A repository turns research from a recurring cost into a compounding asset. The whole value is that the second time a question comes up, the answer is already there — if it's findable.
The word that does the work is searchable. Storage is trivial and nearly worthless on its own; teams have always had folders full of research nobody can find. The discipline that separates a useful repository from a document graveyard is the unglamorous operational work — consistent insight format, thorough tagging, a habit of adding entries, and crucially a habit of checking before researching anew. Get that right and research compounds: every study makes the next question cheaper to answer. Skip it and you pay full price for the same insight again and again, while making decisions that ignore evidence sitting unfindable somewhere in the organisation.
A folder dump isn't a repository. Tag and format for retrieval.
If entries don't share a shape, they can't be found or trusted. Standardise.
A repository that stops being updated decays into an archive. Make logging routine.
If no one checks before researching anew, the repository saves nothing. Build the check-first habit.
The repository is the home for the structured insights produced by Tool 21.
Logging and checking the repository is part of the continuous rhythm (Tool 23).
Before adding a question to the backlog (Tool 24), the repository is checked for an existing answer.
Over time the repository is what lets a team's user knowledge compound across Modules 3 and 5.
Think about a team you know (or your own work). Where does past research actually live — and could you find a study from a year ago in under five minutes?
If the answer is “scattered” or “probably not,” list what it would take to make it findable: one location, consistent format, tags.
If you couldn't quickly retrieve old research, you've found the hidden cost — every unfindable study is one your team is liable to pay for again.