From Passion to Execution: A Story of Evolving Research Maturity at LinkedIn
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
"Different stakeholders tackle the delivery problem differently, which gave us necessary divergent thinking."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"In jazz, the structure is head, I solo, you solo, then back to head—repeated often and universally."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"Ways to reduce extraction in research is by embedding community-led practices rather than holding the keys to knowledge ourselves."
Sarah FathallahLessening the Research Burden on Vulnerable Communities
March 30, 2020
"Co-creation between users and technology determines if this AI evolves to be useful or harmful."
Peter Van DijckBuilding the Rosenbot
June 4, 2024
"You can’t have a hackathon without free food."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
"Think of a creative professional as an ideas athlete or a creativity Olympian."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Language matters—make your OKRs user-centric and customer-focused to avoid them feeling like overhead."
Bria Alexander Benson Low Natalya Pemberton Stephanie GoldthorpeOKRs—Helpful or Harmful?
January 20, 2022
"War gaming can be used by advocacy groups to test moves against policymakers and lobbyists before taking real-world actions."
Terry BuckmanWargaming (An Introduction)
August 10, 2023
"The pressures in large organizations make it hard for teams to see the value of empathy and cross-team connection."
Matt StoneScaling Empathy, A Case Study in Change Management
June 11, 2021
Latest Books All books
Dig deeper with the Rosenbot
Why do current capitalist incentives make systemic and community-focused tech solutions difficult to implement?
How can product teams ensure they prioritize meaningful user outcomes over rapid AI-powered development speed?
What key skills do researchers use to align teams and create organizational coherence?