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
"The biggest myth of all is you can't teach creativity."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Find your senior executive ally who understands design and go talk to them first — it works."
Amy MarquezINVEST: Discussion
June 15, 2018
"Trust is built by showing you’re there to help make them succeed, not just push your agenda."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"It took a lot of relationship building and conversations to break down the perception that designers' time was owned by particular teams."
Alicia MootyDesign Staffing Models
September 30, 2021
"I believe there's really no such thing as a boring place at the state of mind."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"We can’t complain about not having a seat at the table if we don’t offer one of our own."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Our principle is that whatever we build must help researchers avoid becoming a silo."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"People don’t actually hate innovation; they like their jobs and feel threatened by change."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Data analysts and user researchers rarely work together effectively, which is one of the biggest missed opportunities."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
