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
"Design ops should coordinate initiatives, measure impact, and advocate for designer happiness as a business metric - Peter Bosma."
Bria Alexander Patrizia Bertini Peter Boersma Jon Fukuda Dave Malouf Theresa Slate Changying (Z) ZhengCharting the future of DesignOps: A community workshop
April 18, 2024
"There always has to be a human option if you’re not getting what you need from the AI."
Kate KalcevichDesigning inclusively with AI
June 5, 2024
"Lonely workers think about quitting their job twice as frequently as non-lonely workers."
Kat VellosOpener: The Other L Word
January 8, 2024
"Every output should have at least three source links, almost like citations in a research paper."
Savannah CarlinDon't botch the bot: Designing interactions for AI
June 4, 2024
"You want to flex one or two variables to create range scenarios—best case, middle case, and worst case."
Giff ConstableFinancial fluency for product leaders: AMA with Giff Constable
April 11, 2024
"You need a thoughtful operation managing your democratization program to keep it on track and adaptable."
Lija HoganDoing more with more: Lessons from the Front Lines of Democratization
March 9, 2022
"Use clear and obvious terms in taxonomies—unusual acronyms won’t make sense to GPT or others."
Jorge Arango[Demo] How to re-categorize content at scale using LLMs
June 5, 2024
"When you use more accessible products internally, you make it easier to hire and retain people with disabilities."
Saara Kamppari-MillerTheme Three Intro
October 4, 2023
"Having a single workspace for the branded house makes it easier for designers not to dip and dive between spaces, reducing complexity."
Ryan Matthew Alex KurchevDesignOps without Boundaries: Building More with What You Have
September 10, 2025
Latest Books All books
Dig deeper with the Rosenbot
Why do 3D print settings need manual adjustment when scaling models, and how did Kritika handle this?
How should a design system be used or adapted when working with AI-assisted design tooling?
How can emerging communities of practice support designers and facilitators working with social complexity?