Discussion
Summary
Jeff recounts the Ask Alexis project, a promising advice service launched by a team in New York that ultimately failed due to lack of full-time commitment, illustrating the challenge of scaling part-time initiatives. Melissa shares a similar experience with a simplified payroll app at Intuit that was canceled after strategic concerns about disrupting existing products led to a loss of experimentation discipline. They discuss Netflix's usability experiment where a simple design unexpectedly outperformed expert-picked options, highlighting that users are often less proactive than assumed. The panel emphasizes the importance of cultural acceptance of failure and humility even among experts, and the need to hire team members who thrive on business constraints and hypothesis-driven work. Bill and Alyssa add insights on prototyping strategy and overcoming internal company barriers to experimentation, including tactics for restricted corporate environments and sustaining behavioral change. The speakers converge on the necessity of strong vision paired with openness to data, continuous iteration, and understanding stakeholder perspectives to foster successful innovation.
Key Insights
-
•
Partial team commitment can doom even promising projects like Ask Alexis, underscoring the need for dedicated resources to scale.
-
•
Experimentation success can be overturned when strategic business pressures refocus teams away from data-driven iteration, as seen in Melissa's payroll app case.
-
•
Users often prefer simpler, less customizable experiences, contrary to expert expectations, as demonstrated by Netflix's simple grid winning over more complex UX.
-
•
Organizational culture must accept being wrong openly to enable iterative product success and honest experimentation.
-
•
Hiring emphasizes designers and product people who thrive under constraints and can think in hypotheses rather than simply artistic expression.
-
•
Prototyping should be aligned with what the team needs to learn next, whether that is validating value or testing technical performance.
-
•
Throwaway and evolutionary prototypes both have roles; balancing speed of ideation and closeness to production is critical.
-
•
Sustained behavioral change experiments require framework and measurement designed for longer-term user engagement rather than immediate clicks.
-
•
In restrictive enterprise environments, small internal experiments and ally-building are key to expanding a culture of testing.
-
•
Effective evangelism of experimentation depends on tailoring communication to the audience, whether executives, engineers, or designers.
Notable Quotes
"We had to kill the Ask Alexis product because the level of commitment needed couldn't happen with part-time consultants."
"After the payroll app was on the roadmap, folks started asking where's the revenue, and then they wanted to change the direction without experimentation."
"The Netflix grid experience that was simplest and offered no genre picking actually won, showing users are lazier than they think."
"Just because you've been right in the past doesn't guarantee you'll be right in the future."
"We hired designers who speak product, think in hypotheses, and love constraints rather than just artistic ideas."
"You have to ask yourself, what's the least amount of work you need to do to get the learning you want from a prototype."
"The developer who refused to run experiments bragged about success, but it was actually a flop once we ran the test properly."
"If you're changing workflows in experiments, you need to keep track of impacted teams like call centers to avoid resistance."
"Finding allies within an enterprise and demonstrating success is how you get a foothold for experimentation culture."
"Experimentation pitching must use the language and values of who you're trying to convince in the organization."
Or choose a question:
More Videos
"A society that is designed is better than one that is simply built."
Bob BaxleyTheme 4: Intro
January 8, 2024
"Giving people time and space to think individually and pressure test with AI before group discussion prevents dominance by power."
Kurt McCullochFaster alone, further together: Rebuilding collaboration in the age of AI research
March 10, 2026
"If you fix the problems for marginalized communities, you really fix them for everyone."
Irina Tikhonova Kari DietrichSmall Wins, Big Impact: Leveraging and Elevating User Engagement
December 9, 2021
"Research is seen as an adjunct to design, often missed in road mapping and strategic planning."
Renee BouwensLanding Product Impact: Aligning Research as a Foundational Driver for Delivering the World’s Best Products
December 15, 2023
"I’m exceptionally qualified to talk about design systems because I’ve never used one until recently."
Nalini P. KotamrajuAn Organizational Story: Salesforce Lightning Design System
June 9, 2016
"AI helped me produce nearly 80 posts in a year; without AI, that pace would be impossible."
Changying (Z) ZhengPractical DesignOps: From Ideas to Tools That Teams Actually Use
September 25, 2025
"The community is a big tent - welcoming diverse perspectives and geographies to define and shape civic design."
Rachael Dietkus, LCSW Victor Udoewa Jennifer StricklandEverything You Need to Know about the Civic Design 2022 Call for Presentations
May 17, 2022
"Begin every research project with the end in mind by framing what impact you hope to drive."
Roberta Dombrowski Sam Duong WoloszynskiMaking Research a Team Sport
March 11, 2022
"It's not a match-winning pass if no one catches it."
Megan Blocker Mujtaba Hameed Victor UdoewaPanel: Excellence in Impact
March 25, 2024
