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
"Sometimes, avoiding the conversation feels easier but can have bigger costs than facing it."
Joshua GravesWe Need To Talk: Navigating Conversations with Your Boss (Part 1 of 3)
April 14, 2025
"Feedback is more like an investment and a contribution into not just the person's work, but also to their growth."
Vanessa VarinFeedback: The Other F-Word
September 10, 2025
"We had a backlog that made turnaround times at least 14 days; now teams can get answers within three days through democratization."
Jen Cardello Jennifer OttoLearning Velocity—The Insights Speedometer
September 16, 2021
"Our goal is to be AI fluent, not necessarily AI experts."
Alnie FigueroaThe Future of Design Operations: Transforming Our Craft
September 10, 2025
"You can invite your coworker, your brother, your sister, your aunt to sponsor sessions even if they’re not signed up for the conference."
Bria AlexanderOpening Remarks
September 29, 2021
"Most AI fails because projects require near perfect accuracy, which AI can't reliably deliver."
Dan SafferWhy AI projects fail (and what we can do about it)
May 14, 2025
"These bots will say yes to all your ideas, whether they're good or bad—that's the rocket to Mars anti-pattern."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"You don’t build in Figma or Photoshop and handoff anymore, you build in code alongside AI agents that generate working components."
Erika FlowersThe Handoff is Dead: Design-Led Engineering with AI Agents
March 4, 2026
"Giving the whole team access to feedback made them feel responsible and inspired to solve user needs."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
