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
"We’re entering an information era because information itself is infrastructure and has actual monetary value."
Bram WesselEnterprise Information Architecture
January 10, 2020
"Learning and knowledge management isn’t just about quality of work, it’s deeply tied to retaining people and motivation."
John DevanneyThe Design Management Office
November 6, 2017
"We try to figure out who needs to be in the room to hear it — research is how we build team cohesion."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"No two re-platforming journeys are exactly the same, and there isn't one single formula that works every time."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"The cultural context can dramatically change how long data remains relevant or when it expires."
Iulia CornigeanuQuantQual Book Club: Small Data
March 8, 2024
"Write grammatically simple sentences with fewer commas and use the active voice to improve clarity."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"Quantitative data boils complex situations down to single numbers that are easy to grasp and discuss."
Rima Campbell Amrit S BhachuIncrease Productivity and Drive Business Impact
September 24, 2024
"By starting to categorize risk in detail, you naturally lead to better prompts and better evals."
Peter Van DijckHands-on AI #2: Understanding evals: LLM as a Judge
October 15, 2025
"Whose story gets told, the participant or the researcher, is also a question of knowledge production."
Bilan HashiThe Tension Between Story Collecting and Story Telling in Research
March 10, 2021
