Summary
One of the hardest parts of building a knowledge management system is getting leadership buy-in and getting your team to use it properly. Join Kevin and Sarah to learn about their journey from passion-fueled side project to research-only management to fully funded knowledge/project/insights management initiatives (including an on-staff research librarian!). In this talk you will hear real-world examples of how they struggled to show how this was one of the most important things to be doing. They will share examples of how one team is leveraging the work to scale their research capabilities and provide rapid evaluation for the entire company. You will also hear about the accelerated growth and value that has come from connecting their system with the greater design org and even product management. Through all of this they will share actionable takeaways on how to show value early, what not to do, and how to use a system to amplify your teams’ work across the organization and help your Ops team scale.
Key Insights
-
•
Inefficient project tracking using Google Sheets was replaced by a custom Airtable base with automated unique project numbers, improving scalability and reducing duplicate entries.
-
•
Leadership resisted using standard service management tools like Jira for research project tracking, fearing it implied UX research was a service team taking orders.
-
•
Participant recruitment leverages LinkedIn’s data warehouse for opted-in users, enabling quarterly bulk recruits that account for 80% of recruiting needs.
-
•
Participant incentives were decentralized and error-prone until onboarding Ethnio enabled global culture-specific rewards, automated delivery, and compliance tracking.
-
•
Implementing a status reporting workflow integrated into tools researchers already used (Teams, Figma) drastically improved status accuracy and reduced manual effort.
-
•
Rapid Lab, a biweekly evaluative research program across three lines of business, tests six designs every two weeks, made possible by foundational operational improvements.
-
•
Connecting research assumptions, participant feedback, insights, and business impact in Airtable enables leadership to track research impact and identify process issues.
-
•
A research librarian role was critical to maintain a consistent taxonomy in the insights repository, preventing chaos from multiple inconsistent tagging styles.
-
•
Consolidating planning workflows across multiple design functions into a single Airtable interface addressed visibility, prioritization, and capacity planning challenges.
-
•
Scaling research ops requires strategic partnerships, custom tooling, centralization with flexibility, automation to reduce human error, and ongoing iteration as the organization grows.
Notable Quotes
"Broken processes aren't scalable."
"The biggest pain point in my life was tracking research projects through a disjointed flow of Airtable, Google Docs, and hand-curated emails."
"The only way to get a project number was through Airtable, which allowed us to further evolve the process."
"Researchers used to issue incentives manually, running on an honor system that was error-prone and inconsistent."
"Ethnio allowed us to track participants' total compensation and set annual caps, reducing fraud risk and improving compliance."
"We simply told leadership we don’t even know what we don’t know or what we do know, leading to a research insights repository."
"The research librarian equals consistent taxonomy; without that, you can’t build accessible and searchable knowledge."
"In a large organization, processes must become more centralized and rigid to scale, though flexibility and team needs still matter."
"Start somewhere simple, start early, include the right voices, and build foundational components you’ll reuse over and over."
"Go find a partner in Ops who has a passion for operations and pain points of inefficiency, then build something great together."
Or choose a question:
More Videos
"Graph databases use nodes and relationships instead of tables to store information, providing a network of knowledge."
Ren PopeBuilding Experiences for Knowledge Systems
June 6, 2023
"Everyone wanted to know what the official pattern was, so they could have confidence that they were using the right one."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Different teams were thinking about users quite differently for the same product on the Windows phone."
Ellen ChisaThe Values of Design
November 29, 2023
"About 200,000 digital health products exist, but only 1% of 1% have FDA clearance for accuracy."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"We still think of accessibility as a binary when it should be recognized as a continuum."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
June 10, 2022
"If you can’t tell me your workflow, don’t talk about your tools."
Jacqui FreyScale is Social Work
March 19, 2020
"In two years, some design ops team members shouldn’t have a job because the muscle memory and structure is baked in."
Dominique WardThe Most Exciting Time for DesignOps is Now
September 8, 2022
"We add value not by providing more data but by introducing critical thought, friction, and reflection into organizational insight-making."
Jemma Ahmed Megan Blocker Eduardo OrtizRedefining the research toolkit: Expanding methodologies for a changing world
March 12, 2025
"Federal funding does not provide food for participants, so we had to plan accordingly to make participation irresistible."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
Latest Books All books
Dig deeper with the Rosenbot
How can research repositories score or show the impact of research recommendations to enhance organizational learning?
How does User Interviews use AI to improve participant matching and reduce fraud?
How can AI agents maintain context and prevent delivering misleading answers when searching research data?