Lean Production and Kanban: Insights from NUMMI and Their Application to Modern Software Development

In 1982 General Motors closed the Fremont Assembly Plant, but in 1984 it partnered with Toyota to create the NUMMI joint venture, rehiring the former workers and sending them to Japan to learn the Toyota Production System (TPS). Within three months NUMMI produced near‑perfect cars at lower cost.

The workers repeatedly emphasized teamwork, describing how TPS places quality as the highest priority and empowers employees to stop the line, pull an "andon" rope to summon managers, and collaboratively solve problems, leading to continuous improvement.

Key TPS concepts include respecting people, granting workers authority to halt production, and involving everyone in system redesign, contrasting sharply with traditional Taylorist management that treats workers as interchangeable machines.

Lean thinking, illustrated by the "Lean Thought House" model, highlights two pillars—respect for people and continuous improvement—providing superior value over tools like waste‑reduction or Kanban alone.

Since the early 2000s, lean principles have migrated to software development, influencing agile practices such as Kanban and Scrum. David Anderson’s book "Kanban Method" identifies overload and resistance to change as major challenges, proposing a pull‑based value‑stream approach to minimize waste and improve flow.

The article lists practical lean practices for software teams, including value‑stream visualization, limiting work‑in‑progress, managing queues, reducing batch size, applying DevOps, rapid feedback, and decentralised decision‑making.

After General Motors’ bankruptcy in 2009, NUMMI closed in 2010 and was later acquired by Tesla, beginning a new chapter.

For more DevOps and R&D operations insights, follow the DevOpsHub WeChat public account.