Definition
Lean Methodology (or Lean Manufacturing) is a production management system born at Toyota in the 1950s-70s, formalized as the “Toyota Production System” (TPS) by Taiichi Ohno. The term “Lean” was coined in 1988 by MIT researchers studying Toyota, publishing their findings in “The Machine That Changed the World” (1990).
The essence of Lean is maximizing customer value while minimizing waste (muda). It identifies 8 types of waste: transportation, inventory, motion, waiting, overproduction, over-processing, defects, and unused talent.
How it works
Lean is based on 5 fundamental principles:
1. Define value: identify what creates value from the customer’s perspective. Only activities the customer is willing to pay for are value; everything else is potential waste.
2. Map the value stream: visualize all activities (value stream mapping) that bring a product/service from concept to customer. Identify waste and bottlenecks.
3. Create continuous flow: eliminate interruptions and batch processing. Ideally, the product flows from first to last step without queues or accumulation.
4. Establish pull: produce only what is requested by the next process (pull), instead of building inventory in advance (push). The Kanban system is a pull technique.
5. Seek perfection: continuous improvement (kaizen). Each iteration reduces waste and moves closer to perfect flow. There is no final state, only continuous progress.
Main tools and techniques
Value Stream Mapping (VSM): diagram showing all steps of a process, distinguishing value-adding activities from waste. Identifies lead time, cycle time, and accumulation points.
5S: method for organizing workspace (Sort, Set in order, Shine, Standardize, Sustain). Reduces time lost searching for tools or materials.
Kanban: visual system to manage workflow and limit work-in-progress (WIP). Originally physical cards, now often digital boards.
Just-In-Time (JIT): produce/deliver exactly when needed, in the quantity needed. Reduces inventory and makes problems immediately visible.
Jidoka (autonomation): automatically stop production when a defect is detected, to avoid propagating errors. Includes poka-yoke (error-proofing).
Andon: visual system (lights, displays) to signal problems in real-time. Anyone can activate it to stop the line.
Adoption beyond manufacturing
Lean Software Development: adaptation of Lean principles to software development, formalized by Mary and Tom Poppendieck (2003). Direct influence on Agile and DevOps. Eliminates waste like context switching, handoffs, waiting, unused features.
Lean Startup: Eric Ries methodology (2011) to validate business models through rapid Build-Measure-Learn cycles. Minimizes waste by building MVP (Minimum Viable Product) and iterating on real feedback.
Lean Healthcare: application to hospitals and clinics to reduce waiting times, medical errors, costs. Virginia Mason Medical Center is a famous case study, with 30-40% reductions in patient lead times.
Lean Government: Some public agencies (e.g., UK Government Digital Service) use Lean to simplify bureaucratic processes and improve citizen services.
Practical considerations
Cultural change required: Lean is not a set of tools, but a philosophy. It requires team empowerment, tolerance for stopping when problems are found (andon), and long-term focus. In command-and-control cultures, superficial adoption fails.
Measurability: key metrics include lead time (total time from order to delivery), cycle time (active processing time), throughput, and takt time (pace required to meet demand). Metrics must be visible and used for improvement, not punishment.
Integration with Agile: many Agile practices derive from Lean (e.g., kanban, WIP limits, retrospectives as kaizen events). Lean is more focused on flow and efficiency, Agile on feedback and adaptability; they complement each other.
Resistance to change: eliminating waste reveals hidden problems (e.g., reducing inventory exposes quality defects). This can create resistance from managers accustomed to buffers to hide problems.
Common misconceptions
”Lean is only cost reduction”
No. Lean reduces costs as a consequence of eliminating waste, but the primary goal is to increase customer value and response speed. Toyota invests heavily in R&D and quality.
”Lean means doing more with fewer people”
Not exactly. Lean eliminates unnecessary work (waste), freeing people for value-adding activities. Mature Lean companies reassign these people to innovation, process improvement, or expansion.
”Lean requires stability and high volumes”
False. Lean was born at Toyota precisely to handle variety (mixed-model production). The principles apply even to single batches or high variability (e.g., personalized services, software).
”Lean is only for operations”
No. Lean applies to all processes: product development, sales, accounting, HR. “Lean Thinking” extends the principles to the entire organization.
Related terms
- Kanban: visual pull system, core Lean technique
- Agile Software Development: methodology incorporating Lean principles
- DevOps: applies Lean thinking to complete software lifecycle
- CRISP-DM: data science methodology that can benefit from Lean principles
Sources
- Womack, J. P., Jones, D. T., & Roos, D. (1990). The Machine That Changed the World
- Liker, J. K. (2004). The Toyota Way: 14 Management Principles from the World’s Greatest Manufacturer
- Poppendieck, M. & Poppendieck, T. (2003). Lean Software Development: An Agile Toolkit
- Ries, E. (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses
- Lean Enterprise Institute: https://www.lean.org/