What to give
- Teams that will use it: [e.g. product, design, marketing, support]
- Tool it will live in: [spreadsheet, notes app, wiki, or unknown]
- Past findings to convert: [paste findings, quotes or report sections with study name and date]
- Products, journeys or customer types to tag by: [list]
Task
Design the repository so a person can find a proven insight in two minutes and trust where it came from.
Checklist for the design
- One insight per entry, written as a plain statement of what people do or need, not a solution.
- Every entry carries its evidence: study, date, method, number of participants and one supporting quote.
- A confidence label: strong (seen across studies or many participants), medium, or early signal.
- Tags from a fixed list only: journey stage, customer type, product area, theme. No free-typed tags.
- An owner and a review date; entries older than the review date are marked "check before use".
- Links between related insights instead of duplicates.
Output format
- Entry template: | Field | What goes in it | Example |
- Tag list grouped by tag type, no more than 40 tags in total.
- Rules for adding, updating and retiring entries in eight bullets.
- The pasted findings rewritten as entries in the template.
- Three starter searches a new team member should try.
Guardrails
- Do not merge findings from different studies into one entry unless both are cited.
- Keep quotes word for word and anonymised.
- Mark any missing evidence field as [missing], never fill it in.






