Skip to content
Log in

Research Repository Structure

Indexes by finding rather than by study, since a study-organised archive is one nothing is ever found in again.

0

Share this prompt

Free — no card needed

Create a free account

to open Research Repository Structure — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryResearchForAnalysts, Designers, OperatorsTested onClaudeChatGPT

Running it, start to finish

  1. Design around when people actually come looking and what they search for.
  2. Make the finding, not the report, the unit of storage.
  3. Assign an owner and be honest about the weekly maintenance.

What you get back

The output this produces, every time.

  • Indexes findings rather than studies, so the repository answers what people actually ask.
  • Links contradicting findings rather than letting one silently replace another.
  • Marks findings as superseded when the product changes, since a stale finding is trusted and wrong.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Keep the taxonomy small. An elaborate tagging scheme is maintained by nobody and becomes inconsistent within a few months.
  • Capture findings during the study. Recording them afterwards is extra work with a delayed payoff, and it is what does not happen.
  • Do not migrate the archive. It consumes exactly the energy the new practice needs, and usually the project ends there.

More Research prompts

All Research

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.