01 · Purpose
What Lean helps us understand
Lean is a way of improving how organisations create value. It begins with the outcome people need and examines the whole process that produces it. The aim is to make useful work flow reliably, recognise problems early and improve the system with the people doing the work. Manufacturing provides many historical examples, but the questions also apply to logistics, education, healthcare and administrative services.
Imagine a customer waiting for a spare part. Each warehouse department reports that it is busy and meeting its local targets, yet the customer still receives the part late. Lean directs attention to the order’s journey: where it waits, how it moves, what information is missing, which work must be repeated and whether the next step is ready. Busy departments and a well-performing end-to-end process are not automatically the same thing.
Begin with a clear question: what outcome is needed, by whom, when, and to what standard? “Process more orders” is incomplete if the extra orders are inaccurate or do not reach the customer when needed. Productivity, quality, reliability, workload and safety must be considered together.
Lean is a system, not a collection of shortcuts
A tidier workplace, less stock or a faster task can help, but each change must improve the process’s purpose. Removing a necessary buffer before replenishment is reliable may create shortages. Increasing picking speed while generating packing errors may move the problem downstream. Judge the effect on the whole process, not only the local activity.
02 · History
From weaving machinery to automotive production
Toyota’s industrial roots include Sakichi Toyoda’s work on weaving machinery. His looms incorporated mechanisms that detected abnormal conditions and stopped operation, preventing faults from continuing unnoticed. Toyota identifies this development as an origin of jidoka: making abnormalities visible and building quality into the process. Toyota’s account of the birth of jidoka.
The Type G automatic loom was developed in 1924. Toyoda Automatic Loom Works was established in 1926, and a patent-rights agreement with Platt Brothers followed in 1929. The move into vehicles built on this industrial experience; Toyota Motor Co., Ltd. was established in 1937. These were successive developments, not a single invention that instantly created modern Lean. Toyota Industries’ history; Toyota’s automotive beginnings.
Toyota describes TPS through two pillars: jidoka and Just-in-Time. Kiichiro Toyoda’s thinking helped develop Just-in-Time, while Taiichi Ohno and others helped turn these ideas into a working production system over time. The term lean production was coined by John Krafcik during MIT research in the late 1980s; Womack and Jones later articulated five Lean principles in 1996. Toyota on TPS; LEI on lean production; LEI on Lean principles.
The historical lesson is practical. A machine running continuously is not necessarily producing value: if it makes faulty output, continued operation increases the problem. The same reasoning applies when an office system rapidly creates incorrect invoices or a warehouse prints labels for orders that cannot yet be dispatched. Recognise the abnormality, contain its consequences and investigate it.
03 · Toyota’s production system
Quality at the source and work at the right time
Jidoka
Make an abnormal condition visible and prevent it from continuing unchecked. Equipment can stop automatically; people can also signal and stop a process when an abnormality requires attention. The operating system needs a response, not just a warning light.
Just-in-Time
Provide the required item, in the required quantity, when it is needed. This depends on coordinated flow, replenishment and the ability to respond to problems. It is not an instruction to remove all inventory regardless of demand or supply reliability.
These concepts follow Toyota’s description of the two TPS pillars. Read Toyota’s explanation.
In our warehouse example, an incorrect part identifier is detected at the checking point. Passing the order onward to keep the packing line busy would transfer the defect. A jidoka-oriented response makes the mismatch visible, contains the affected order and brings the relevant person to resolve the abnormality. After recovery, the team investigates why the mismatch was possible.
For replenishment, suppose the packing team withdraws cartons from a defined stock location. A visible withdrawal signal can trigger replacement in a controlled quantity. Before reducing the stock level, establish consumption, replenishment time, variation and the consequence of a stockout. The buffer should be justified by operating conditions and reviewed as those conditions improve.
The two pillars interact. A replenishment system is difficult to trust if defective items arrive unpredictably. Quality checks become less effective when large queues conceal where a problem originated. Flow and quality need to be developed together.
04 · Lean principles
Follow value through the process
A widely used formulation describes five principles: value, value stream, flow, pull and perfection. They provide a way to reason about improvement; they are not five isolated projects. Lean Enterprise Institute’s explanation.
| Principle | Core idea | Original warehouse example |
|---|---|---|
| Value | Understand the outcome the customer needs. | The correct spare part reaches the agreed destination when needed. |
| Value stream | Examine the connected work producing that outcome. | Trace one order across acceptance, release, picking, packing and handover. |
| Flow | Reduce avoidable interruption between useful steps. | Address orders waiting for missing information between picking and packing. |
| Pull | Connect upstream work with downstream need. | Replenish a defined packing-stock quantity in response to consumption. |
| Perfection | Continue improving rather than treating one change as final. | Review the new operating method as demand, errors and constraints change. |
For application, distinguish customer value from an organisation’s internal preference. A report may be easy to produce and still fail to provide information the recipient needs. Ask how the output is used before deciding that more reporting means more value.
Value-creating work must also be supported by safe and reliable operating arrangements. Some activities do not directly transform the output but remain necessary under current conditions. Examples can include required traceability records and checks protecting a critical operation. Identify why they are necessary; do not remove them merely because they are labelled non-value-adding.
A useful first classification is value-creating work, currently necessary non-value-creating work, and avoidable waste. This is a basis for investigation, not permission to bypass legal, safety or customer requirements. Redesigning a process can reduce the need for some checks, but evidence and authorisation must precede their removal. LEI on waste and current necessity.
Respect for people is essential to how improvement is carried out. Listen to the people who encounter the problems, make difficulties discussable and support the capability to investigate them. A target that forces staff to conceal defects or skip needed checks undermines learning. Involving staff also helps the team understand the difference between the documented process and the work that actually happens.
05 · Six Sigma
A complementary focus on variation and defects
Motorola’s own history dates the development of its Six Sigma quality process to 1986. Six Sigma therefore has a different origin from Toyota’s production system. Over time the two traditions have been combined in Lean Six Sigma. Motorola’s historical timeline.
Consider two packing processes. Both average six minutes per order. One usually takes five to seven minutes; the other often takes two minutes but sometimes takes twenty. Their averages conceal different experiences for the next operation. Variation matters because a process with unpredictable output can make planning difficult even when its average looks acceptable.
Six Sigma strengthens the discipline of defining measures, assessing measurement reliability, examining variation and testing explanations. Sigma (σ) denotes standard deviation in the statistical setting. A process’s relationship to specification limits depends on its location, spread, stability and distribution; one average or one “sigma level” does not describe all of those conditions.
The often-quoted 3.4 defects per million opportunities relies on a particular long-term shift convention. It is not the defect probability of every unshifted process whose limits sit six standard deviations from its mean. At this stage, understand the distinction between a management convention and a statistical model; the measurement and capability guides develop the calculations and assumptions. ASQ on Six Sigma; our capability guide.
These are complementary emphases, not exclusive territories. Lean also uses evidence and variation matters to flow; Six Sigma projects can address delays and waste. Select methods for the problem rather than insisting that every project contains the same quantity of Lean and statistical tools.
06 · Seeing waste
TIMWOODS: eight categories to investigate
TIMWOODS is a memory aid for Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects and unused Skills. The traditional TPS list contains seven wastes; unused talent was added as an eighth category in wider Lean practice. DOWNTIME is another memory aid for the same broad eight categories, arranged differently. LEI’s seven wastes; LEI on the eighth waste.
Show all eight wastes in one reference table
| Letter | Waste | Meaning | Original example |
|---|---|---|---|
| T | Transportation | Unnecessary movement of materials or work. | Moving a completed order to a distant staging area, then bringing it back for labelling. |
| I | Inventory | Stock or work accumulating beyond what the process needs. | Released orders queue between picking and packing without a justified operating purpose. |
| M | Motion | Unnecessary movement by people or equipment during work. | A packer repeatedly walks away to retrieve tape and reaches across an awkward workstation. |
| W | Waiting | Time lost because the next activity cannot proceed. | A picked order waits for a missing customer reference before its label can be completed. |
| O | Overproduction | Producing more, or earlier, than downstream need justifies. | Preparing a large batch of labels for orders not ready for release. |
| O | Overprocessing | Doing more processing than the required outcome needs. | Entering the same shipment details into two systems without a necessary control purpose. |
| D | Defects | Output failing a requirement, with correction or loss resulting. | The wrong part is packed and must be replaced before handover. |
| S | Unused skills | Failing to use people’s knowledge, capability and ideas. | Experienced staff know why order references go missing but are excluded from the investigation. |
Distinguish similar-looking wastes
Transportation concerns movement of the work or material; motion concerns movement within performing the work. A trolley carrying orders across the building illustrates transportation. A worker repeatedly bending to reach a tool illustrates motion. The same situation can contain both, but the distinction helps select the right observation and response.
Overproduction concerns quantity or timing; overprocessing concerns unnecessary work content. Producing ten unused copies of a report is overproduction. Reformatting a required report three times without a recipient need is overprocessing. Making a required item correctly but too early can still be overproduction.
Inventory and waiting can be two views of the same queue. Fifty orders in front of packing constitute work-in-process inventory; the delay experienced by an order is waiting. Avoid adding the same cost twice just because it appears under two categories. Record the actual burden: units held, time elapsed, space occupied and effect on the required output.
A waste label is a starting point, not a verified cause
“Waiting for information” describes an observed delay. It does not establish why the information is missing or which change would prevent it. Trace cases, understand definitions and interfaces, and test explanations before selecting a solution. A waste walk should lead to questions and evidence rather than a list of accusations.
Some inventory, movement or checks may be necessary under current conditions. State what justifies them and investigate opportunities to change those conditions. Removing stock without resolving unreliable replenishment can create waiting and overburden elsewhere. The useful outcome is a better-performing system, not simply a lower count of labelled waste activities.
07 · Looking beyond waste
Muda, mura and muri work together
Muda refers to waste, mura to unevenness, and muri to overburden. These ideas broaden investigation beyond whether a particular task adds value. LEI’s discussion of the three concepts.
| Observed condition | Concept | Original investigation question |
|---|---|---|
| Orders are released in one large afternoon wave. | Mura: workload is uneven across the day. | What determines release timing, and is the wave required? |
| The wave exceeds packing capacity before carrier collection. | Muri: workload exceeds the team’s workable capacity. | What are the actual capacity, time constraints and safe work conditions? |
| Orders queue, staff search for misplaced items and errors require correction. | Muda: waiting, motion and defects consume resources. | Which burdens arise, and how are they connected to release and capacity? |
This fictional scenario suggests a connection to investigate: uneven release may create overload, which may contribute to queues and errors. It is not proof of causality. Compare actual release patterns, available capacity and affected cases. Reducing walking at a workstation may help, but it will not necessarily solve an afternoon overload caused upstream.
Avoid interpreting the three concepts as a rigid sequence that always dictates the first action. Immediate containment may be needed for a safety or quality risk. For sustained improvement, examine how workload, capability, replenishment and work methods interact.
Reveal how unevenness can create overburden and waste
1. A batch-release rule concentrates orders in the afternoon. Establish this pattern from actual release records.
2. Compare the release workload with workable packing capacity and the collection cutoff. The pattern may overload the operation.
3. Trace the consequences: queues, searching, correction and missed handover. Treat the connection as an explanation to test, not a cause already proved.
4. Evaluate the system response. A faster workstation might help, but it may not resolve a release pattern that still exceeds downstream capability.
08 · From principles to investigation
Where DMAIC fits
Lean supplies a way to think about value, work and improvement. DMAIC supplies a structured investigation for an existing process problem: agree the gap, establish a reliable baseline, verify explanations, test changes and sustain the result. It supports Lean Six Sigma, but it is not the definition of Lean and is not required for every small improvement.
A straightforward local change with a well-understood cause may be managed through a proportionate improvement cycle. A recurring problem crossing several teams, with uncertain causes and a material performance gap, benefits from more structured investigation. In either case, define success, use credible evidence and check consequences rather than assuming that the first idea will work.
In the warehouse case, identifying waiting is the observation. Agreeing which dispatch problem matters belongs in Define. Measuring the extent and variation belongs in Measure. Establishing why particular orders wait belongs in Analyze. Testing a changed release or information process belongs in Improve. Maintaining ownership, standards and a response to deviations belongs in Control.
09 · Further reading
Historical sources and professional foundations
The historical statements and named concepts above link to their sources at the point of use. The warehouse examples, comparisons and application guidance are original teaching material. Toyota and Toyota Industries provide the organisational history; Motorola provides the Six Sigma milestone; the Lean Enterprise Institute and ASQ provide professional explanations.
This introduction is the starting point for a foundations section. It establishes the ideas needed before DMAIC; individual foundations topics can be developed into more detailed guides as the knowledge centre grows.