Summary
There has been an explosion of interest in atomizing research, where researchers stop writing reports and instead tag individual insights in a database. The theory is that this will unlock your insights, making them findable and reusable. But does it work, and should you be doing the same? At Microsoft we tried it: Five years, 40,000 insights, 20+ research teams, and 17,000 unique users. So what have we learnt? We learnt that a structured insight library can be worth the effort. But we also learnt that atomizing insight can be taken too far. We learnt that context is critical. We learnt that short term efficiency is king, and that the required culture change is hard. And through this journey we’ve begun to discover how to blend atomized insight with your traditional research process.
Key Insights
-
•
Traditional research repositories often become burial grounds for insights, making it hard to find or connect reusable knowledge.
-
•
Shifting to atomic research focuses on individual insights as the fundamental unit rather than entire reports, enabling search, link, and remix.
-
•
Microsoft’s HITS system tracks dozens of thousands of insights connected across products like Windows, Xbox, and HoloLens.
-
•
Creating durable, reusable research insights requires overcoming strong human cognitive biases like hyperbolic discounting and in-group favoritism.
-
•
A culture of continuous curation and managerial priority is essential but challenging to maintain over time.
-
•
Immediate tactical value is key to motivating researchers to contribute to reusable knowledge rather than only producing one-off reports.
-
•
Allowing insights to emerge organically by observing reference patterns reduces complexity compared to rigid categorization of durable vs. raw observations.
-
•
Researchers and product teams benefit greatly from direct linking to specific insights and underlying evidence within their day-to-day workflows.
-
•
Handling conflicting insights involves encouraging researchers to collaborate and rationalize perspectives through syntheses rather than top-down arbitration.
-
•
The just-in-time curation approach folds creation and connection of reusable insights into immediate research tasks, reducing friction and cognitive load.
Notable Quotes
"Repository to me has a connotation of a place where stuff goes to sit and collect dust."
"What if the atomic unit of research wasn’t the reports, but it was the insight within those reports?"
"We wanted a living network of knowledge so yesterday’s insight connects to today’s evidence and tomorrow’s learning."
"Curation is super important, but also super hard."
"You have to push against 200,000 years of human evolution to get researchers to create reusable knowledge."
"Product teams want quick, grab-and-go research results, but reusable insights are more abstract and take longer to digest."
"Providing immediate tactical value is the big one for just-in-time curation."
"Standalone insights destroy the researcher’s ability to storytelling and engagement."
"Durable insights can emerge organically based on usage and referencing patterns in the system."
"The challenge is whether your organization has the energy to overcome cultural and technical barriers driving researchers back to disposable knowledge."
Or choose a question:
More Videos
"By understanding our systems and being intentional about tools and processes, everyone benefits."
Neema MahdaviOperationalizing DesignOps
November 7, 2018
"The ability to understand business needs and align efforts is key to delivering recognizable business value."
Sean McKayCoexisting with non-researchers: Practical strategies for a democratized research future
March 11, 2025
"All behavior your component is capable of, including responsive and interaction states, will work inside UXPin."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Every small action counts when it comes to sustainability in urban settings."
Lena ShenkarenkoCollaborative Wireframing for Creating Team Alignment and Shipping Better Products
October 21, 2020
"Traditional devops tools are more task and issue-centric, but designers think in processes and workflows."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"We need to be better at questioning the motivations of the parties we work with and what they’re getting out of the work."
Matt Bernius Sarah Fathallah Hera Hussain Jessica Zéroual-KaraTrauma-informed Research: A Panel Discussion
October 7, 2021
"Life has a way of working itself out."
Maria GiudiceEmpowering change: Reigniting purpose, passion and impact in research
March 13, 2025
"We typically design for the perfect path. Do you design and plan and test for the unexpected path?"
Marc Majers Tony TurnerInterrupted UX - Add A Dose of Reality To Usability Testing
March 11, 2022
"We as designers have the opportunity to be brave, have the courage and humility to do the work."
Jennifer Strickland Lesley-Ann NoelFireside Chat: How Design Addresses a World on Fire
March 18, 2022