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
"I’ve never stopped designing completely, even as a manager or director, but the balance shifts toward strategic work."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles (Videoconference)
February 22, 2024
"Our UI focused on saving time, making the workflow one button and enabling manual edits and regeneration for error recovery."
Jennifer Kong[Case study] Journeying toward AI-assisted documentation in healthcare
June 5, 2024
"Think critically about what we're sharing, who we're sharing with, and how we share to ensure understanding and action."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"Having a pool of interested users and tracking their participation helps avoid participant fatigue and internal bottlenecks."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"We deliberately use project folders as work-in-progress spaces before migrating insights into the main hub."
Michelle Bejian Lotia Anne-Marie MorellRolling Out a Repository: How Zapier Centralizes Insights from Across their Organization
March 28, 2023
"Failure is easy but recovery is really hard, especially the higher up you are in leadership."
Tutti TaygerlyVideconference: How to Work with Difficult People with Tutti Taygerly
June 25, 2020
"Our chief information officer Fletcher Breven has always seen his role as providing a productive environment for IBMers—it’s our North Star."
Patrick CommarfordDesign Staffing for Impact
January 8, 2024
"We’re building and securing better frameworks and futures rather than tangible, countable widgets."
Frances YllanaTheme 2 Intro
September 24, 2024
"You have to design frameworks for the busy executive in the back of the limo."
Mujtaba HameedFrameworks for Excellence: Using Visual Thinking and Communication to Elevate Your Research
March 26, 2024