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
"Getting designers into a cadence of reviewing work with senior stakeholders was not a muscle the team had built."
Maggie DieringerCreating Consistency Through Constant Change
January 8, 2024
"Diagramming is kindness we give to ourselves and others to get our bearings on things we’re stuck on."
Abby CovertStuck? Diagrams Help
October 27, 2022
"We talked all about resilience, curated by myself yesterday."
Bria AlexanderDay 3 Welcome
September 25, 2024
"The trust gap stems from being repeatedly failed by a system, not innate risk aversion or imposter syndrome."
Mansi GuptaDrawing from Feminist Practice to Make Inclusive Design Operational
September 9, 2022
"They paid a vendor $800 million and launched a single form online, which is no longer in use."
Dan WillisFilling the Void
November 7, 2018
"Stress makes us stupid because our creative thinking gets cloudy when under pressure."
Laura WeissTurn Down the Heat: 3 Ways to Handle Conflict in the Moment
November 20, 2024
"We found design managers want team health, DesignOps managers want standardization, product managers want transparency, and producers want autonomy."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 8, 2022
"Digital exclusion is not a fixed status and can affect anyone at different points in life."
Yalenka Mariën Marie MervaillieDesigning for Digital Inclusion in the Belgian Government
December 8, 2021
"Being a positive deviant means confronting challenges with limited resources but innovative, community-based approaches."
Bria Alexander Ariel Kennan Charlotte Lee Sarah Brooks Emily Lessard Gordon Ross Joanne DongReflect and Chart Forward
December 10, 2021
Latest Books All books
Dig deeper with the Rosenbot
What hidden costs should be accounted for beyond license fees when budgeting for research tools?
Why is human synthesis and collaboration still critical despite AI advancements in research?
In what clinical workflow areas is AI currently being integrated and what are the main UX challenges associated?