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."
Dig deeper—ask the Rosenbot:
More Videos
"A kaleidoscope helps us see changing patterns to perceive new images and pursue new possibilities."
Etienne FangPower of Insights: Why sharing is better than silos with Uber’s Insights Platform
December 16, 2019
"The question for hiring managers is how to move from expecting people to be UX researchers to inviting them to become UX researchers."
Victor M. GonzalezPracticing Learners and Learning Practitioners
March 10, 2021
"If we learn X, we will make decision Y, but if we learn Z, we’ll make the opposite decision."
Roberta Dombrowski Sam Duong WoloszynskiMaking Research a Team Sport
March 11, 2022
"Design history files must document every design decision for FDA audits—it's far more rigorous than typical usability tests."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"Use the latest version starring feature so your team only gets updates when they’re ready, avoiding constant notifications."
Jaime CreixemsBest Practices when Creating and Maintaining a Design System
June 7, 2023
"Shapers combine human and machine intelligence and amplify each other’s strengths."
Tricia WangFrom Users to Shapers of AI: The Future of Research
March 25, 2024
"Knowing your value as a person means not giving everything to situations that don't give back."
Shahrzad SamadzadehWhat Is My Value? Two Takes and Some Mistakes
January 8, 2024
"MacGuffins are design artifacts that catalyze collaboration and new ways of working rather than being valuable in themselves."
Jorge ArangoDesign as an Antidote to VUCA
May 9, 2019
"We do about a hundred free community sessions a year where anyone with membership can attend."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
Latest Books All books
Dig deeper with the Rosenbot
What strategies help manage contradictory or late feedback in long projects?
How can small government design teams leverage knowledge management to drive capacity building across diverse agencies?
How can teams embed inclusive design practices without overhauling existing product development workflows?