User Research Repository & Synthesis Templates

Purpose

This repository template helps teams capture, organize, synthesize, and surface user research so insights remain discoverable, credible, and reusable. Use it to reduce duplicated interviews, speed scoping of new studies, and ensure evidence guides decisions.

Why this matters

Research often vanishes in personal notes, drives, or chat threads. A simple, consistent repository with good metadata and a lightweight synthesis habit turns single interviews into organizational memory — accelerating discovery and reducing risk from anecdote-driven decisions.

Recommended folder structure

Keep structure shallow and predictable. Store raw artifacts and syntheses separately so findings can be updated without losing source material.

1. 00_Metadata — templates, taxonomy, README, consent forms, recruitment artifacts.
2. 01_Raw
   • Audio/Video
   • Transcripts
   • Field notes
   • Survey exports
3. 02_Artifacts
   • Photos, screenshots, artifacts captured in sessions
   • Observation logs
4. 03_Syntheses
   • Interview-level notes (per session)
   • Study-level synthesis (themes, opportunities, evidence)
   • Decision memos / recommended experiments
5. 04_Decisions — Rationale and trace to research evidence (feature decisions, process changes, pilot results)

Essential metadata (per artifact or interview)

Store metadata as a small human- and machine-readable record next to each artifact. Suggested fields:

• Title — concise, searchable (e.g., "Jan 2026 | Customer Support | Refund Flow | Interview 07")
• Date
• Type — interview, diary, usability test, survey, observation
• Method — remote moderated, unmoderated, in-person, contextual inquiry
• Persona / segment
• Product / service area
• Researcher(s)
• Consent status — consent form ID, PII allowed? (yes/no)
• Recording link(s)
• Transcript link
• Keywords / tags — pain points, tasks, emotions, channels (comma-separated)
• Confidence / evidence level — anecdote, suggestive, corroborated, validated
• Related decision IDs — link to Decision artifact

Synthesis template (study-level)

Paste this as the header of every study-level synthesis so stakeholders can quickly assess trustworthiness and next steps.

1. Study title & dates
2. Scope & question — what we wanted to learn and why
3. Sample — n, recruiting criteria, segments represented
4. Methods — how we collected evidence
5. Top themes (3–6)
   • Theme name
   • Short description
   • Representative quote(s)
   • Evidence level (how many participants, cross-method corroboration)
6. Opportunity statements — concrete problem framed for action (format: “Users need to because ; opportunity: ”).
7. Risks & unresolved questions
8. Recommended next steps — experiments, prioritized research, metrics to measure impact
9. Attachments & sources — links to raw recordings, transcripts, interview-level notes

Interview-level note template (per session)

• Participant ID
• Timestamped highlights (00:03:45 — key quote or observed behavior)
• Behavioral observations (what they did, not speculation)
• Immediate interpretations (flag as hypothesis)
• Quotes (verbatim short quotes with context)
• Tags (pain points, tasks, emotions)
• Consent & PII handling notes

Quick lookup guide

When scoping a new study, find relevant past interviews using a few fast searches:

• Search by tag + product area (e.g., "onboarding AND payments")
• Filter by method (usability test, diary) to reuse protocol artifacts
• Filter by date range to surface recent behavior
• Search for quotes or exact phrases to build evidence quickly ("I never knew how to...")
• Use evidence level to prioritize studies that are corroborated

Research reuse metric (simple)

Track whether stored research is actually used. A lightweight metric:

Research Reuse Rate (monthly) = (# of times repository artifacts were cited in decisions or referenced in scoping docs during month) / (total decisions or scoping docs that month) × 100

Start with a manual count (link mentions, decision memos pointing to study IDs). Over time you can automate detection of repository links in docs or PRs.

Governance & ethics checklist

• Consent forms are stored with each recording and indicate reuse scope.
• PII is redacted or access-controlled where consent does not allow sharing.
• Retention policy: keep raw data per legal and organizational rules; keep syntheses as long as they are referenced by decisions.
• Access levels: researchers, product teams, executives — limit raw recordings if required.

Getting started checklist

1. Copy folder structure into your team drive or knowledge system.
2. Drop the metadata template into 00_Metadata and require researchers to fill it after each session.
3. Use the interview-level template for rapid notes; add timestamped highlights to be searchable.
4. Produce a short study synthesis within one week of collection and link it to any decisions or experiments that follow.
5. Measure reuse monthly and review barriers in your research retro.

Tailoring guidance

Keep metadata minimal and consistent. Avoid overly complex taxonomies at the start — iterate the tag set from actual use. Use the Evidence Level field to help non-research stakeholders judge how much weight to give a finding.

Example quick templates (copyable)

Study synthesis header
Title: [ ] | Dates: [ ] | Question: [ ] | Sample: n=[ ] | Methods: [ ]

Opportunity statement (one-line)
"Users like struggle to because . Opportunity: ."

Next steps & capability ideas

• Use a small metadata entry form (one line per artifact) to standardize tags and store consistent fields.
• Consider integrating automated transcript linking or a lightweight dashboard that surfaces frequently-cited themes and reuse metrics.
• Make the repository part of your Discovery & Innovation domain so teams can copy and tailor the templates to their sites.

Resources

Keep consent, screener and recruitment templates in 00_Metadata. Link any facilitation kits or synthesis canvases used for rapid workshops.