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
"Embracing uncertainty means diving in without knowing the outcome and creating something new every time."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"Don’t write a book expecting to retire on royalties; this is a specialized field with modest sales."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Levels can mean really different things at different companies, so ask a lot of questions about expectations for each level."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Finding out more about these most active users is a key priority this year, said our CEO at the board presentation."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"Processing limits and licensing terms currently restrict how much video and audio these AI tools can handle."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Difference-in-differences lets you study treatment effects in groups that start in very different places by looking at trends."
Joshua NobleCasual Inference
October 6, 2023
"Storytelling helps gain people’s attention, build empathy, and improve understanding and recall of key points."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"We made a very intentional choice to build in five minute breaks after every talk based on feedback and experience."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"When you design for the edges, you make things better, more fluid, more customizable for everyone."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
Latest Books All books
Dig deeper with the Rosenbot
What steps help build trust and healing in communities affected by historical traumas during engagement?
What benefits come from integrating apprenticeship or internship models into design education?
Why is design education’s emphasis on critical making important, and how does it interrelate with critique and theory?