Summary
Bill begins by recounting his experience at Netflix, where he led multiple simultaneous experiments and learned that 95% of UI code was thrown away, which shifted his mindset to designing for throw-away ability and viewing the UI layer as an experimentation layer. At PayPal, he confronted legacy technology stacks and a resistant culture, but with top-down support, he initiated cultural and technological transformations focused on rapid, user-centered iteration. Bill highlights the power of co-locating engineers, designers, and product folks to maintain weekly user studies and iterate checkout experiences, significantly improving customer satisfaction and business results. He introduces the concept of shearing layers in software stacks to separate stable, secure core layers from volatile experimentation layers, allowing calculated risk-taking. Bill stresses the need to shift organizational culture from delivery-centric to learning-centric, enabling teams to be empowered with continuous customer feedback and collaboration. He discusses democratizing engineering by leveraging internal open source (GitHub) and creating KrakenJS, an open-sourced Node.js framework, which increased developer engagement and reduced onboarding overhead. Bill critiques Agile’s lack of strategic direction and describes how integrating lean UX practices alongside Agile gives it a “brain” by grounding backlogs in real customer problems. He concludes with three essential lessons: achieve shared understanding via a common vocabulary, foster deep collaboration across disciplines, and maintain continuous customer feedback to keep teams aligned with user needs. Throughout, Bill emphasizes embracing failure as incremental learning and the importance of engineering infrastructures designed expressly for learning and change.
Key Insights
-
•
Netflix’s experimentation approach led to discarding around 95% of UI code annually, requiring design for throw-away ability.
-
•
Engineering’s highest value is enabling learning, not just building durable systems.
-
•
At PayPal, slow legacy stacks forced months-long changes that impeded innovation and led to cultural resistance.
-
•
Introducing shearing layers in software stacks helps separate stable secure components from volatile experimental layers.
-
•
Rapid user testing with co-located teams catalyzes accelerated learning and better product outcomes.
-
•
Democratizing innovation through internal open source practices like GitHub and KrakenJS enabled wider participation and faster adoption.
-
•
Agile alone lacks strategic direction; combining it with lean UX grounds backlog creation in real user problems.
-
•
Smaller, autonomous 'two-pizza' sized teams promote faster, higher-quality development than large monolithic teams.
-
•
Continuous customer feedback and embedding user context within teams prevents disconnected, misguided solutions.
-
•
Failure should be incremental and small to enable learning and avoid costly big mistakes.
Notable Quotes
"I started thinking of the UI layer as the experimentation layer."
"Engineering’s number one goal should be to enable learning."
"Organizations contain antibodies — people who resist change but often have good intentions."
"We locked ourselves away for 12 to 18 weeks with customers every week — the rhythm was incredibly powerful."
"Most organizations have a culture of delivery, but they need to move to a culture of learning."
"Great teams, if given enough context, will do smart things."
"We democratize the code base internally to create an intersourcing model, like open source inside the company."
"Agile needs a brain — without user context, it’s just a machine cranking out code."
"Failure is inevitable, but failing in small increments is the key difference."
"Continuous customer feedback soaks your teams with the context of the customer and problem set."
Or choose a question:
More Videos
"Knowledge is power; empowering communities leads to better conservation outcomes."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"Sometimes doing working sessions together to strategize and solve problems can be really beneficial for these new practitioners."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"Launching a design system is not a sprint, there’s no end, it’s always a continuous process."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Tell tight, brief stories of insights focused on impact, not on how you conducted your research."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"Accessibility is an ongoing process where we iterate, improve, and expand, and mobile-first makes the journey easier."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"Documentation and making findings visible even without a dedicated research librarian helps maintain program momentum."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"Culture is the most influential factor impacting people's perceptions and values today."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"We move here. We never actually become New Yorkers."
John DevanneyThe Design Management Office
November 6, 2017
"The most important thing is producing something that gives a perspective nobody else in the organization can bring."
Katy MogalBut Do Your Insights Scale?
March 12, 2021