A Selectively Scrappy Approach to ResearchOps
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
"Some of the most important decisions for service design happen on whiteboards among engineers, often without service design representation."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"Reviewing decisions out loud held everyone accountable and made it harder for Jeff to forget or change his mind."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Kristen wrote the book Design of Orgs for Design Orgs and her experience partly informed this canvas."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"These aren't linear; every circle or box has multiple lines into it—our work does not fit neatly into trees or pyramids."
John CutlerThe Alignment Trap
November 29, 2023
"Diagrams allow us to emotionally hit pause and come back ready to dig further."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Side-pav proposals answer what’s going on, why it matters now, what you propose, what action to take, and what benefit comes from it."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"We can’t just think technology or innovation will solve our problems; we have to embrace and work with those problems."
Devon PowersImagining Better Futures
March 9, 2022
"Your primary function as a research team is to build a culture of research, not just react to project requests."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Your short term memory is the context window; too big, and the model has trouble accessing everything."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
