How Lean Thinking Transforms Product Development: Principles, History, and Practice

Introduction

Lean thinking is the best way to realize the spirit of craftsmanship, aiming to deliver the best product to customers while reducing operational costs and improving efficiency. This article introduces Lean thinking and Lean product development.

Preface

Many readers may already know my recent book Lean Product Development Principles, Methods, and Practices , which shares deep experiences from Huawei, Ping An Technology, China Merchants Bank, and several startups. The book has been strongly recommended by leaders of engineering efficiency and project management at NetEase, Baidu, and Alibaba.

Definition of Lean Thinking

According to Wikipedia (citing the book *Lean Thinking*), Lean thinking is a new way of organizing human activity that aims to eliminate waste and deliver more value useful to individuals and society.

Eliminating waste is a means; increasing value is the ultimate goal.

Lean thinking applies to many domains, such as manufacturing, service provision, and product development.

Origins of Lean Thinking

Lean thinking originated in manufacturing, specifically from Toyota. Key milestones include:

1950‑1970s

During this period Toyota began developing and refining Lean concepts and methods, which became widely known after 1988.

1988

MIT Sloan’s *The Victory of the Lean Production System* compared Toyota’s approach with Western manufacturing, introducing the term “Lean” to the West.

1990

The book *The Machine That Changed the World* systematically described Lean production, bringing it into Western management thought.

Lean Production: Toyota Production System (TPS)

TPS, created by Taiichi Ohno, consists of a goal, pillars, and foundations. Its goal is high quality, low cost, and fast response.

The two pillars are:

Just‑In‑Time (JIT)

Produce the required quantity of product only when needed, enabling flexibility, waste elimination, and reduced lead time.

Kanban cards (blue for withdrawal, brown for production) signal upstream processes to start production, creating a pull‑based flow that aligns production with actual demand.

Jidoka (Automation with a Human Touch)

When an abnormality occurs, the system automatically detects it, stops production, and allows immediate problem solving at the source, preventing defective items from moving downstream.

These pillars form a contradictory unity: JIT promotes flow, while Jidoka stops flow to address quality issues, together ensuring smooth, high‑quality value delivery.

Beyond Manufacturing: Lean Thinking in Other Fields

In the 1990s, Lean thinking expanded beyond manufacturing into healthcare, government, accounting, IT, office work, design, and more, based on the five core principles outlined in the book *Lean Thinking*.

Five Core Principles of Lean

Define Value : Identify value from the customer’s perspective.

Map Value Stream : Identify and eliminate steps that do not add customer value.

Create Continuous Flow : Ensure value moves smoothly toward the customer.

Establish Pull : Let customer demand pull the value stream.

Seek Perfection : Continuously improve to eliminate waste.

Lean Product Development Framework

Lean product development adapts Lean principles to the uncertain, exploratory nature of product creation. Unlike manufacturing, product value is not predetermined; it must be discovered through iterative validation.

The framework consists of a goal, pillars (principles), and foundational practices (management and engineering). The goal is “smooth, high‑quality delivery of useful value.”

Smooth : Ensure continuous flow of value.

High Quality : Deliver outcomes that meet quality standards.

Useful : Provide value that customers are willing to pay for.

Principle 1: Explore and Discover Useful Value

Product development must acknowledge uncertainty—customers may not know what they need. Lean Startup embodies this by iterating through Build‑Measure‑Learn cycles to validate hypotheses and uncover viable business models.

Principle 2: Focus on and Improve Value‑Flow Efficiency

Value‑flow efficiency looks at the time from demand to delivery from the customer’s viewpoint, unlike resource efficiency which focuses on internal utilization. Prioritizing flow leads to end‑to‑end optimization, with resource efficiency improving as a result.

Kanban is an effective method for achieving flow‑centric improvement.

Connecting Lean Product Development and DevOps

Both aim for smooth, high‑quality delivery of value. DevOps integrates engineering practices (continuous delivery, automation) with management practices, complementing Lean product development.

Lean vs. Agile

Agile emphasizes rapid response and delivery, while Lean focuses on maximizing value itself. When flow is smooth, agility naturally follows. The Agile Manifesto, created in 2001, addressed software development challenges, but today we need an expanded view that includes end‑to‑end value streams across all functions.

Conclusion

Lean thinking provides a timeless framework for creating and delivering value. Whether applied to manufacturing, software, or any modern product, its principles—defining value, mapping the value stream, ensuring flow, pulling on demand, and pursuing perfection—remain essential for sustainable success.