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 need to work on relationships with stakeholders because that’s how things get done in complex systems."
Boon Yew ChewMaking Sense of Systems—and Using Systems to Make Sense of the Enterprise
June 6, 2023
"Customers benchmark your company to their last best experience, often outside of your industry."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Solving one task in the design process can generate issues or benefits in different teams."
Patrizia Bertini Alexandra Mengoni LeónPushing DesignOps’ Influence into New Global Markets
September 9, 2022
"Design Ops brings the joy back into design."
Jacqui FreyScale is Social Work
March 19, 2020
"We have to meet them where they are. Designers need to learn the language of business. That’s a very, very important lesson."
Robert SchwartzWe're Here for the Humans
June 9, 2017
"I’ve literally relearned how to walk."
Tamara HaleWar Stories LIVE! Tamara Hale
March 30, 2020
"If you are silent about your pain, they will kill you and say you enjoyed it."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"The job market is cyclical — tough times pass and opportunities come back around."
Dave Hoffer Joanne WeaverUX Job Search AMA #3 with Joanne Weaver and Dave Hoffer
July 16, 2025
"We ended up doing an average of five labs per quarter covering 12 to 15 research questions, which helped avoid design delays."
Feleesha SterlingBuilding a Rapid Research Program
May 18, 2023
