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
"Play invites curiosity, and curiosity allows us to imagine and create new worlds."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"The real trick is being able to say no gracefully and communicate your priorities effectively."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars) (Videoconference)
June 13, 2024
"A connection that I made when I was 14 years old helped me to fund my college education, find my wife, and get the job at ExxonMobil that I still have today."
Nick CochranGrowing in Enterprise Design through Making Connections
June 3, 2019
"Documentation helps explain the rationale and revisit decisions in the future, preventing repeated mistakes."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Germany is at the confluence of several factors that constrain digital services: large population, federal government layers, and strong data privacy concerns."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"Despite all the insecurities, most team members were willing to show up every week and challenge what they thought they knew."
Nova Wehman-BrownWe've Never Done This Before
June 4, 2019
"Artificial intelligence is about building human-like intelligence. This has opened up a golden opportunity for all of us to make a big impact."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"Having workers leave the airport and travel to the farm to self-isolate was simply not feasible – the province would have to be responsible for quarantine."
Gordon Ross12 Months of COVID-19 Design and Digital Response with the British Columbia Government
December 8, 2021
"Sharing my story with the engineering director opened something; vulnerability builds trust."
Tutti TaygerlyMake Space to Lead
June 12, 2021
