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."
Dig deeper—ask the Rosenbot:
More Videos
"Through DP&M, designers get more contextual detail than what might be captured in a Jira ticket."
Jon Fukuda Ellie KryslDesign Planning and Management Support
October 3, 2023
"Publishing a component library means anyone can update titles or roles, and it updates everywhere at once."
Saara Kamppari-MillerCartography for Design Communities
September 10, 2025
"The four superpowers of design include giving experts breathing room to do the deep work necessary to bring substance."
Kevin BethuneReimagining Design: Unlocking Strategic Innovation
June 8, 2022
"One-on-ones aren’t just reflective of a point in time but are a journey you go on together."
Daniel OrbachZero to One: Co-Creating Operating Models with your Team
September 23, 2024
"Everyone goes through quite an extensive application process, but it was stress-free and informal."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"I really want to be able to sign off on decisions and make sure that I’m preserving my agency as a UX professional."
Clara Kliman-SilverUX Futures: The Role of Artificial Intelligence in Design
June 7, 2023
"Make sure your leadership team knows your name."
Robin Beers Nalini Kotamraju Andy WarrPanel: Excellence in Communicating Insights
March 26, 2024
"I am not throwing away your UX."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"When you’re smashing silos, the first wall you try to break through always gets bloody."
Kristen Honey"Let’s Talk About Data and Crisis”: Public Digital Service Delivery = Open Data + Human Centered Design
November 18, 2021
Latest Books All books
Dig deeper with the Rosenbot
How did the Lab balance flexibility for individual project documentation with the need for an integrated knowledge system?
How can AI be integrated as a collaborator in creative workflows?
What lessons did Sean and Sarah share about sustaining knowledge management beyond the closure of a government design team?