Efficiently Scaling Research as a Team of One
Summary
Key Insights
-
•
Transitioning from academia to corporate research is driven by the desire for faster impact despite adapting to a new pace.
-
•
Ad hoc research without formal processes limits organizational buy-in and impact.
-
•
Gaining buy-in from leadership is key to securing budgets, tools, and resources for research.
-
•
An ops-first approach to UX research helps scale research activities and onboard new team members efficiently.
-
•
Empowering product managers and other teams to conduct quality research increases overall research throughput.
-
•
Training and interactive mentorship ensure scientific rigor and consistent research quality when delegating research tasks.
-
•
Storytelling with real user learnings helps shift perception of research from ad hoc to essential and pattern-driven.
-
•
Research proposals framed around saving time and reducing iterations resonate well with leadership.
-
•
Building a shared codebook and involving interview teams in coding fosters consistent qualitative data analysis.
-
•
Even with a single researcher, implementing research Ops can enable multiple parallel research tracks.
Notable Quotes
"I transitioned out of academia because I wanted to work faster and create immediate impact rather than slow, layered processes."
"Research is actually a sales role – you have to show off a little to get buy-in from the top."
"People started asking if a pattern we'd seen in one user occurred in others, and that led to formalizing qualitative analysis."
"Without buy-in, you can’t get budgets approved or tools put in place to grow research practices."
"Ops-first means standardizing processes so we can scale and onboard new team members quickly."
"I can’t work 24 hours a day; efficiency and empowering others to do some research is how I stay effective."
"Before giving someone access to research tools, we do a 60-minute one-on-one training to cover the essentials."
"It’s like knowing how to drive a car doesn’t mean you can drive a semi; research has do’s, don’ts, and methodologies."
"If we test now, we’ll save two or three iterations waiting for organic user feedback later."
"Creating shared coding schemes and having teams do first-pass coding helps maintain consistency in qualitative analysis."
Or choose a question:
More Videos
"A lot of our work still happens in spreadsheets, because they’re flexible and dynamic."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Skills are like onboarding material for the model; you write them as simple markdown files that describe workflows or tools."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
"Most enterprises are not emotionally safe places; people can’t just leave emotions at the door."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"The Last of Us 2 was the first console game a completely blind person could play from start to finish by adding innovative, customizable accessibility features."
Sam ProulxAccessibility: An Opportunity to Innovate
June 8, 2022
"Design is finally where it can shine — solving human problems beyond just product design."
Wendy JohanssonAn Education on Design Education for Orgs
June 10, 2021
"There will be session notes and sketch notes so you don’t have to take notes yourself unless you want to."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"If you could pre-book your carry on baggage into the overhead locker, wouldn’t that be great?"
Stephen PollardClosing Keynote: Getting giants to dance - what can we learn from designing large and complex public infrastructure?
November 7, 2017
"A movement needs to stand for something, be collective, hopeful, sustainable, and tangible."
Uday Gajendar Adam RichardsonFrom AI to Zeitgeist: Theory as the design antidote to AI hype
March 27, 2025
"We may need to borrow research techniques from journalists, actuaries, epidemiologists, ethicists, and science fiction writers."
Leah BuleyClosing Plenary: The Crisis of Digital
March 31, 2020
