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
"When we train AI on what we have done in the past, we will just do the same more efficiently, not better."
Samuel ProulxFrom Standards to Innovation: Why Inclusive Design Wins
November 19, 2025
"72% of people surveyed had never used the design system before, showing a gap in understanding despite having skilled teams."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"We’re always designing for ourselves, even on days when we don’t have full physical capabilities."
Lija HoganPractical Principles of Inclusive Research
March 27, 2023
"Transformation isn't just about ideas, it's about infrastructure."
Jenny PriceFrom Tradition to Transformation: Unlocking Startup Agility in a Legacy Enterprise
September 10, 2025
"Many people keep all their research in shared drives, but without strict naming conventions, it gets harder to find anything."
Michele MarutResearch Repositories Reconsidered
February 14, 2019
"We’re moving toward a contextual enterprise, where everything is relevant and adaptive to the user’s situation."
Greg PetroffSoftware as Material—A Redux
June 6, 2023
"Design principles have to be guiding ways and opportunities for conversations, not a strict scorecard."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"I joined the design ops team about six months after it was created, and I'm not the head but part of its leadership."
Chris MosesStretching the Definition of DesignOps with Product Development
November 7, 2018
"Fast is not a virtue in and of itself; moving slower and acting with intention ensures you go in the right direction."
Caroline Jarrett Erin WeigelHave fun with statistics?
December 12, 2024
