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
"Embracing uncertainty means diving in without knowing the outcome and creating something new every time."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"People saying you should write a book is nice, but it’s not the real reason you should write one."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"The difference between director and principal often lies in whether you’re inspired more by leading people or focused on outputs and craft."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"I invited Mark to a user interview — he had no idea interviewing wasn’t for him but respected that skill deeply."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"User recordings are your most valuable asset but have become riskier due to biometric privacy laws."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Qualitative research really poses questions; quantitative methods let you investigate those questions rigorously."
Joshua NobleCasual Inference
October 6, 2023
"Empathy doesn’t come from reading a report—you don’t get close to users by just reading data."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"We are obligated to treat each other with kindness and respect; this is a safe and inclusive space."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"We often say don’t make me think. When that’s not possible, reuse and recycle those learnings."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
