Repository Retrospective: Learnings from Introducing a Central Place for UX Research
Summary
While many researchers see the value of a central research repository, how to introduce one in an organization is still a big question. Today we have the chance to learn from two researchers who have done it. Taylor Jennings, Senior UX Researcher at Chili Piper, and Joe Nelson, User Experience Researcher at MasterControl, will share their process and experience gained from implementing their research repository. We’ll cover how they realized the need for a repository, how they convinced stakeholders, evaluated solutions, and what they’d do differently in hindsight. Join us live as we leave plenty of opportunities for the audience to ask questions.
Key Insights
-
•
Building a research repository early, even as a small team, sets a scalable foundation for future growth.
-
•
A centralized repository drastically reduces time spent on analysis and synthesis compared to scattered document storage.
-
•
Including both raw data (interviews, transcripts, surveys) and polished insights enables flexible stakeholder usage.
-
•
Video and audio clips within repositories significantly increase stakeholder empathy and understanding of user pain points.
-
•
Well-designed tagging systems balance flexible project-specific tags with a controlled set of global tags for cross-project insights.
-
•
Stakeholders often hesitate to adopt new tools, so researchers must continuously promote and guide repository usage.
-
•
Implementing participant management features prevents redundantly contacting the same users and improves coordination.
-
•
Security, legal, and privacy considerations are critical when choosing repository software, especially for participant data.
-
•
Migration and implementation ease, including single sign-on and importing legacy data, are important evaluation criteria.
-
•
Repositories support long-term insight building by allowing retrospective access and iterative tagging of findings.
Notable Quotes
"If we wanted to scale and continue to grow, we were going to need something to help us."
"Setting up a repository as a team of one or two is actually the prime time to establish processes like that."
"Having a place for people to self-serve insights is really big, so they don’t ask us to repeat research."
"Slides are hitting a brick wall; video clips make findings much more interactive and engaging for stakeholders."
"Cutting down on the analysis time was huge for us, speeding up speed to insight significantly."
"We had to convince our director and executives by showing how the repository added real value for the product team."
"Drag and drop ease, and collaborative affinity diagramming in the tool, were unexpected but very welcome advantages."
"Seeing product managers and designers’ aha moments when they realize how impactful the tool is was great."
"Tags are a balance; project tags are wild and flexible, global tags must be controlled to avoid chaos."
"Short-term learnings kind of roll into long-term ones as you iterate and build on historical findings."
Or choose a question:
More Videos
"Accessibility defects are bugs. If it’s a P1 blocking bug for an accessibility issue, treat it like any other P1 bug."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"The best products come from marrying analytics with human stories."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Don't just flip the switch and say go talk to customers; you have to set guardrails and train people."
Janelle EstesUX Research Trends
January 28, 2021
"We often get designed into a corner by trying to fix words at the end instead of involving content designers earlier."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"The community is an ongoing prototype; members have a strong, frequent voice in shaping what good looks like."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Designing the service so the team can be efficient and impactful is essential — otherwise you just move the inefficiency around."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"Co-regulation means someone who is safe can help bring another out of a triggered state."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"We have over 30 contracting teams spread across roughly 10 vendors all working on parts of the veteran experience landscape."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Being comfortable with discomfort is key — if someone tells me I'm wrong, I'm okay with that."
Tricia WangSCALE: Discussion
June 15, 2018
