Video: Lean Engineering: Engineering for Learning and Experimentation in the Enterprise

This video is only accessible to Gold members. Log in or register for a free Gold Trial Account to watch.

Most conference talks are accessible to Gold members, while community videos are generally available to all logged-in members.

Lean Engineering: Engineering for Learning and Experimentation in the Enterprise

Gold

Thursday, May 14, 2015 • Enterprise UX 2015

Bill Scott

VP Business Engineering, Paypal

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.