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
"Drag and drop ease, and collaborative affinity diagramming in the tool, were unexpected but very welcome advantages."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Not everyone has the same capacity to aspire to a future; this is critical when working with marginalized communities."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Adobe’s Kickbox is a fantastic professional development tool, but it doesn’t drive new lines of business."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Leadership needs to be just as behind accessibility as the designers and professionals doing the work."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"You can’t make your team happy, no one can ever make anyone else happy ever, ever."
Tess DixonC'mon Get Happy
September 29, 2021
"Cross-functional relationships often matter more to output than relationships within the immediate team."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Communication matters—sending an email to an executive with spelling mistakes can ruin your respect."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"At Sage Sure, we build paved roads so people can choose to drive on them or carve their own path."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
Latest Books All books
Dig deeper with the Rosenbot
In what ways does storytelling help insights cut through corporate and organizational noise?
How do I handle tagging and linking to existing related work without overwhelming myself?
How have changes in communication technologies historically affected collective knowledge building, and what might AI's role be?