Summary
Megan Blocker will talk about how to decide where to invest your precious time and attention for maximum impact. In other words, where is it most important for your team to get serious about ResearchOps, and where is it okay to stay scrappy? How can you grow sustainably by picking and choosing your battles? It all depends on your goals, your context, and your priorities. We’ll talk about a framework for making those decisions, and about how applying it worked for our growing team.
Key Insights
-
•
Scaling research requires balancing skill levels, organizational scale, culture, and leadership buy-in.
-
•
You don't need formal research titles to do research; skills can be distributed across designers, PMs, and others.
-
•
A small research team serving a large organization can leverage apprenticeship and education models to expand impact.
-
•
Building a large, engaged user testbed quickly is possible with minimal resources and has strategic benefits.
-
•
Leadership buy-in is signaled not just by budget but by leaders seeking out research to guide decisions.
-
•
Organizational culture shapes how you implement research — entrepreneurial cultures allow quicker experiments, hierarchical ones require stakeholder management.
-
•
Developing reusable tools, templates, and playbooks helps scale quality research across a growing organization.
-
•
Scrappy grassroots efforts can lead to formalized, systematic research programs over time.
-
•
Continuous storytelling and advocacy are essential for gaining and maintaining leadership support.
-
•
Research scale and focus need continual reassessment as team size, culture, and buy-in evolve.
Notable Quotes
"I realized that dedicating my time and energy into something that wasn’t going to be used was not a good use of my time."
"Research skill and talent can be present in many different kinds of people, you don’t have to have research in your title."
"In a hierarchical culture, you ask permission; in an entrepreneurial culture, you ask forgiveness."
"We made a 250-person testbed grow to 1200 people in under a week just through one email campaign."
"If you want access to those names, you got to come through us and show your research plan, which helped us ensure quality."
"We focused on interviewing and synthesis because those methods were most likely to be employed by our product managers."
"Offers of championship from leaders, like 'What do you need from me?' are strong signs of buy-in."
"Our education program isn’t just basic info—it builds empathy and literacy across the whole product team."
"Scrappy grassroots methods never fully go away; you always need to ask where you can get scrappy next."
"Stakeholder analysis and managing stakeholders is critical in hierarchical cultures to maintain trust."
Or choose a question:
More Videos
"We are co-creating with the product organization to make sure everything fits seamlessly rather than being separate."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"Innovation is invention multiplied by adoption multiplied by inclusion."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Prototyping is not about usability, it’s about exploring the idea."
Gretchen AndersonScaling the Human Center
June 8, 2017
"If anyone’s pay goes up, we move the whole pay scale so equity and fairness are maintained by the entire team."
Chelsea MauldinLet's Talk About Money
November 17, 2022
"Building design communities in legacy companies means bringing other disciplines into the fold."
Lada GorlenkoTheme 3: Introduction
June 10, 2021
"Designing for the real world means dealing with practical constraints and making refinements in the face of compromise."
Craig VillamorResilient Enterprise Design
June 8, 2017
"The fundamental things do apply as time goes by."
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"Great research doesn’t automatically have the intended impact because people may not want their minds changed."
Robin BeersBeyond Insights: Researchers as Organizational Change Catalysts
March 25, 2024
"Design requires teams because you can't be expert in everything—from pixels to hardware to databases."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
Latest Books All books
Dig deeper with the Rosenbot
What features does Rosenbot offer to help UX learners deepen their knowledge through follow-up prompts?
What strategies motivate cross-functional teams to input their research findings into a centralized repository?
Why does AI still fall short in fully automating proposal writing for bespoke research projects?