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
"Managers were asking for user stories but hadn’t done any analysis or design — they didn’t understand the scope."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"If you have somebody on your team for three years, for five years, that’s amazing from a longevity perspective given enterprise legacy and complexity."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"Continuous onboarding is like drinking water in sips throughout the day, not a gallon all at once."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"A government designer aims to reduce UX variation while a contractor may optimize only their single product, creating potential conflicts."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Move fast and break things doesn’t work when you’re designing for cancer patients or disaster victims."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"Generative fill is now the most used tool in Photoshop, with 3 million users and over 2.3 billion images generated."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Creating and holding space is like putting bumpers up in bowling so people know they won’t fail if they engage."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Regulations are design problems, not just technical ones, influencing how we create products and experiences."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"A design ops career ladder can look like a step stool unless you create multiple tracks for growth and specialization."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
