How to Coach Enterprise Experimentation
Summary
In this talk, Alyssa Briggs shares her experience coaching enterprise experimentation, emphasizing that experimentation is a mindset for problem-solving by validating assumptions through small, fast tests. She highlights that executives often support experimentation in theory but struggle to embed it into daily work. Using Intuit as a case study, Briggs illustrates how simply training and embedding experiment coaches within teams transformed the company’s culture, enabling tens of thousands of experiments annually that generate millions in revenue. She describes three essential practices for experiment coaches: collaboratively planning experiments using an experiment grid, helping teams embrace and learn from failures by facing data honestly and conducting quick customer research, and catalyzing organizational change by spreading the coaching role and uncovering new opportunities for experimentation beyond product design. Briggs walks the audience through a live experiment about a name memory trick to demonstrate how to develop hypotheses and validate assumptions quickly. She also recounts a story where a small sales experiment disproved executives’ skepticism about a new product tier, leading to significant business impact and wider cultural adoption of experimentation. Briggs encourages everyone to adopt the experiment coaching mindset and start running small experiments to shift team behaviors and company culture.
Key Insights
-
•
Embedding experiment coaches within existing teams is key to sustaining a culture of experimentation.
-
•
Experimentation thrives on embracing small failures to avoid costly large ones.
-
•
Executives often support experimentation top-down, but real change happens when coaches integrate experiments into daily workflows.
-
•
The experiment grid is a powerful yet simple tool for collaboratively planning experiments by unpacking assumptions and defining testable hypotheses.
-
•
Most teams fail their first experiment, and coaches must help them face the data and learn rather than become discouraged.
-
•
Quick, informal customer research after an experiment helps uncover root causes and increases team engagement.
-
•
Consistently planning follow-up experiments builds momentum and prevents the 'one-and-done' pitfall.
-
•
Experiment coaching is not a full-time role but can be integrated as 10-20% of a team member’s responsibilities.
-
•
Experiments can test not just products but internal processes and business assumptions, unlocking broader innovation.
-
•
Demonstrating successful experiments with quantitative data can transform executive skepticism into enthusiastic support, driving significant business impact.
Notable Quotes
"If you’re afraid of failure, that’s okay. With experimentation, you’re going to fail—but in little tiny ways that don’t really matter."
"Executives get experimentation but often it doesn’t stick when people go back to their normal teams."
"The simple thing that worked at Intuit was training and embedding experiment coaches in teams."
"An experiment coach spends about 10 to 20 percent of their time helping the team change mindsets and actions."
"The most important tool is not for running experiments, but for planning them—the experiment grid."
"If we do X, then Y percent of people will do Z—that’s how you frame hypotheses to learn from both success and failure."
"It’s better to run lots of quick, cheap experiments to remove doubt than to wait for the perfect, statistically significant test."
"Nine out of ten teams fail their first experiment, which is normal but can be demoralizing."
"Helping your team face the data honestly and then diving into customer conversations helps uncover what went wrong."
"You know you’ve succeeded as a coach when you put yourself out of a job by giving away the role."
Or choose a question:
More Videos
"The design mindset was way more important than the bureaucratic mindset."
Sofía Delsordo Kassim VeraPublic Policy for Jalisco's Designers to Make Design Matter
December 8, 2021
"Healthy debate is key, and we should be biased toward a successful outcome, not our own ideas."
Product and Design at Bloomberg: A 15-year Evolution
December 6, 2022
"We don’t have dedicated user researchers, but designers and PMs conduct most research here."
Liza Pemstein Jane DavisScaling Research Via an Ops First Model at Clever
March 27, 2023
"It’s important to reflect on our work and careers to shape what comes next."
Kara KaneTheme One Intro
November 16, 2022
"Using a playbook helps codify domain knowledge and prioritization criteria for AI to apply."
Mark Interrante Harry MaxAI for Prioritization (3rd of 3 seminars)
July 11, 2024
"People with disabilities often pay more to buy from stores they trust are accessible and where they feel confident."
Sam ProulxOnline Shopping: Designing an Accessible Experience
October 3, 2023
"Product managers learn to attach at the end of every sentence something about money — no money, no attention."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"Designing healthcare means thinking about how your city, state, and nation work."
Juhan SoninDesign Now! The Agenda for Action
September 4, 2025
"Women’s empowerment is often glorified but doesn’t necessarily meet their needs beneath the surface."
Mansi GuptaDrawing from Feminist Practice to Make Inclusive Design Operational
September 9, 2022
Latest Books All books
Dig deeper with the Rosenbot
How do I handle credibility challenges and emotional barriers when working with medical professionals?
What role do templates play in structuring research reports for better repository management and AI parsing?
How can measuring team behaviors instead of just results improve trust and performance in design ops?