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
"Don’t schedule your pilot during the holidays — our first pilot had one graduate because it went through December."
Marjorie Stainback Kelsey KingmanTransforming Strategic Research Capacity through Democratization
October 24, 2019
"We should reconsider the savior complex designers sometimes have — we’re not all powerful."
Alexandra SchmidtWhy Ethics Can't Save Tech
November 18, 2022
"Responsible systems are systems that keep humans in control."
Carol SmithOperationalizing Responsible, Human-Centered AI
June 7, 2023
"Using ChatGPT strategically increased my visibility and invited me into more strategic product meetings within my company."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"My manager says never ask me to take a day off, just tell me — it’s a huge cultural shift."
Allison SandersOperating with Purpose
January 8, 2024
"We did a blended approach with a visual refresh first to minimize differences between old and new and buy time."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Your short term memory is the context window; too big, and the model has trouble accessing everything."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
"Friction in a situation can cause a person to switch thinking styles, not personality types."
Indi YoungThinking styles: Mend hidden cracks in your market
January 8, 2025
"Mature research repositories are rare, and return on investment depends heavily on scale, governance, and organizational structure."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community
August 27, 2020
Latest Books All books
Dig deeper with the Rosenbot
How do disabilities exist on a spectrum and what are examples of situational and temporary disabilities?
How can large healthcare organizations foster coherence and collaboration to better respond to complexity?
How can parallelizing activities like hiring and market discovery speed up time-to-market in new country launches?