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
"Always communicate next steps, timelines, and delays honestly with candidates; they will appreciate it and stay engaged."
Corey LongHiring in DesignOps: A Critical Study on How to Hire and Get Hired
September 23, 2024
"Always design a thing by considering it in this next largest temporal context — a day in a month, a decade in a century."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
"Human biases are the real problem behind algorithmic bias because organizations embed those biases first."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The future of urban living depends on our commitment to environmental justice."
Lena ShenkarenkoCollaborative Wireframing for Creating Team Alignment and Shipping Better Products
October 21, 2020
"We need to innovate how we innovate, expanding cultural and geographic perspectives in design."
Christian BasonExpand—Rethinking Design for Public Challenges
September 14, 2022
"Social opportunities to connect with each other actually offset the remote fatigue and isolation that many were feeling."
Nicole UmphressDelivering Design Education During a Global Pandemic: Lessons Learned
June 9, 2022
"Jazz soloists draw from a lifetime of patterns, sometimes quoting TV theme songs like the Muppets or Sanford and Son."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"If you told me about a conference like this 30 years ago, you could have gotten all the participants in the backseat of a minivan."
Bob BaxleyTheme 4: Intro
January 8, 2024
"If seeing a diverse participant pool is important to you, it's your responsibility to make sure your recruiters use it as a priority."
Megan CamposWhat Did I Miss? The Hidden Costs of Deprioritizing Diversity in User Research
March 12, 2021
