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."
Dig deeper—ask the Rosenbot:
More Videos
"I know who you are and I have opinions."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"Build relationships before you need them. You can’t create them when the house is on fire."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"You shouldn’t send another survey unless you’ve implemented changes and allowed time for behavior to adapt."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Self-report is not the end all; people often don’t know why they behave certain ways, especially regarding automatic motivations like deeply ingrained mental models."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"Human behavior is anything but linear, rational, or predictable."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"We forget a lot of details over time; documentation saves us from repeating mistakes."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"The absence of empathy and understanding is causing much of the pain in design."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"Around 14 to 20 designers is usually the tipping point where having a dedicated design ops person starts to make sense."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"Provoking and reframing perspective helps teams get unstuck by thinking in new and surprising ways."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
