UX Research Repository: Your Team's Shared Brain

Why it exists

As a research function grows, its output—reports, videos, notes—becomes scattered and hard to find. Valuable insights get lost, and teams unknowingly duplicate studies that have already been done. A repository solves this by creating a single, organized home for this knowledge.

The mental model

A research repository is a central library for your team's collective user knowledge. Instead of asking a colleague, "What do we know about user onboarding?", you query the repository. It's a shared brain that remembers every insight, making past research discoverable and reusable.

How it works

A repository is a system, built with either general collaboration tools (like Confluence) or specialized UX tools (like Dovetail), that stores and organizes research outputs. It houses not just final reports, but also the components that generate them: research plans, raw notes, video clips, and transcripts. Each piece of data, or "insight," can be tagged and categorized, making the entire collection searchable. This allows anyone in the organization to find relevant findings without having to know which specific study they came from.

When to use it

Implement a repository when your organization starts feeling the pain of scale. Key signals include stakeholders being unable to find past research, teams accidentally re-running similar studies, or valuable insights failing to influence decisions because they're buried in a slide deck on someone's local drive. It's a foundational element for a formal ResearchOps practice and for increasing an organization's overall UX maturity.

When not to use it

A formal repository can be overkill for a very small team where knowledge is easily shared informally. The biggest risk is creating a system that no one maintains or uses. If you don't have the resources—often a dedicated ResearchOps function—to ensure adoption and upkeep, a repository will quickly become an abandoned archive, creating more noise than signal.

One canonical example

A product manager needs to understand user sentiment about a checkout flow. Instead of commissioning a new study, she searches the repository for "checkout." She finds two reports, five video clips of users expressing frustration, and a dozen tagged insights from three different studies conducted over the last two years. She has her answer in minutes, not weeks, and can build upon a foundation of existing knowledge.