What Software Needs to Learn from Physical Product Delivery

Mass production in the early 20th century taught engineering‑based organizations how to deliver complex physical products, and the complexity of those products has only increased with the integration of electronics and software. For example, modern cars contain dozens of electronic control units and over 200 million lines of code, making software a major cost driver.

Most large organizations excel at managing physical and electronic product delivery but lag behind in handling large‑scale software codebases, as evidenced by rising software‑related automotive recall rates that now match those caused by hardware defects.

The growth of software complexity suggests that recall rates will continue to climb unless the manufacturing methods that improved automotive quality—such as lean production—are applied to software. Cars are becoming computers on wheels, yet the industry has not fully transferred lean principles to software development.

Many organizations still view software as a project with fixed timeframes and budgets, ignoring lifecycle cost and profitability metrics. By applying product‑development and lean principles—organizing teams like assembly lines, focusing on lead time, and aligning delivery with a customer‑pull value stream—software companies can achieve the same level of quality and efficiency seen in physical manufacturing.

Donald Reinertsen’s work on product‑development flow emphasizes the need to structure delivery as a product value stream that ensures uninterrupted flow of value to customers. This mindset reveals software delivery as a complex collaborative network requiring processes, feedback, and traceability.

Adopting these practices, which are already used by the most innovative software firms, can help other organizations catch up and shape the future of software delivery.