Managing What We Know – Lessons from Atlassian’s Research Library

🎧 Talk: Managing What We Know – Lessons from Atlassian’s Research Library

👩‍🔬 Speaker: Allison Reid, Lead Research Librarian at Atlassian

📢 Hosted by: UX Insight Think Tank

📝 Read the companion article: Managing What We Know (UX Insight)

⏱️ Full Talk Length: 59 mins

⏱️ Summary Reading Time: ~8 mins

🧠 Key Concepts

"Managing what you know is even more important than doing new research."

Don’t Collect — Catalog
- A research library doesn’t physically store reports; it maps what exists and links out.
- Focus on metadata (title, author, topic, date, URL) — not migrating files!
Consistency is the Superpower
- Use simple fields: e.g., Product, Topic, Author, Date.
- Create controlled lists (e.g., always use "Purchase" not "Buy") to make finding insights reliable.
Library as a Service (LaaS)
- Adoption explodes when the library is actively supported (training, workshops, desk research help).
- Just building a tool isn’t enough — supporting use is what creates company-wide impact.
Start Simple — Expand Later
- Begin by cataloging only what researchers produce.
- If needed, later expand carefully to trusted sources (like vetted data science reports).
Success Metrics
- Atlassian’s library adoption: 10% of all employees, with 1/3 of them becoming repeat users.
- 90% of research questions now answered without needing new primary research!

Step	How to Do It
Fields to include	Title, Author, Product, Topics, Date, Link to artifact
Tools you can use	Confluence Databases, Airtable, SharePoint Lists, Google Sheets
Tagging strategy	Use broad simple terms first (e.g., “Customer Experience,” “Features”)
Maintaining quality	Start small, be consistent, and edit later if needed.
When to prune	Review content after ~5 years to remove outdated research.

✅ Pro Tip from Allison: "Even basic searchability (like a simple Confluence table) is a huge leap forward if you’re starting from nothing."