Lean Engineering: Engineering for Learning and Experimentation in the Enterprise

Key Insights

• •

  At Netflix, 95% of the UI layer was thrown away within a year, reframing UI as an experimentation layer rather than durable software.

• •

  Engineering's primary goal should be enabling learning, partnering closely with design and product teams.

• •

  Different parts of a software stack have different risk profiles; applying the concept of shearing layers helps accept more risk on the user interface layer to enable faster learning.

• •

  Organizations contain 'antibodies'—cultural and organizational forces resistant to change—that must be understood and navigated to drive transformation.

• •

  PayPal's transformation was accelerated by a top-down mandate combined with intense cross-functional collaboration and frequent user testing.

• •

  Using internal GitHub and open source paradigms democratizes code access and innovation, allowing anyone to contribute and experiment.

• •

  Prototyping should be considered a first-class engineering activity, not a separate or lesser process.

• •

  Agile methods lack an inherent ‘brain’; embedding continuous customer feedback and real user context into the backlog gives Agile teams direction and purpose.

• •

  Engineering teams that share vocabulary and deeply collaborate with designers and product managers produce better outcomes.

• •

  Embracing small incremental failures enables faster learning and avoids the risk of large-scale failures that can paralyze organizations.

Notable Quotes