The 8 Wastes of Lean (TIMWOODS)

The eight wastes of lean are the eight categories of non-value-adding activity that lean sets out to remove: defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra-processing. They are remembered by the acronyms DOWNTIME and TIMWOODS, and together they name every way work consumes resources without adding value the customer will pay for.

This is the field reference to the eight wastes themselves. It is deliberately different from two neighboring guides: muda, mura, and muri covers how unevenness and overburden generate waste in the first place, and lean manufacturing covers where the eight wastes sit inside the five lean principles and the full toolkit. Here the job is narrower and deeper: one clear definition, one plant-floor example, and one detection tip for each of the eight, plus both mnemonics so you can teach it on the floor. In lean terms, these eight are the forms of muda pure waste, the third and most visible of the three Ms.

What are the eight wastes of lean?

The eight wastes of lean are defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra-processing. Every one of them describes activity that consumes time, labor, space, or material while adding nothing the customer values. The list is a lens, not a scoreboard: you walk a process, name what you see in these eight terms, and that naming turns a vague sense of "this is slow" into specific, attackable targets.

One waste often hides another. Overproduction creates inventory; inventory creates transportation and motion; batched work creates waiting; and all of it buries defects until they are expensive to find. That chain is why lean treats overproduction as the most dangerous waste of the eight, and why value-stream thinking looks at the whole flow rather than one station.

Where did the eight wastes come from?

The original list was seven wastes, defined by Taiichi Ohno as part of the Toyota Production System in the mid-twentieth century. Ohno's seven were transportation, inventory, motion, waiting, overproduction, over-processing, and defects, focused strictly on the physical production process. When lean spread to Western companies in the 1990s, practitioners added an eighth, non-utilized talent, to name the waste of not tapping the knowledge and problem-solving of the people doing the work. That eighth waste is why a real lean program depends on an employee suggestion system and shop-floor problem solving, not just tooling changes.

What do DOWNTIME and TIMWOODS mean?

DOWNTIME and TIMWOODS are two mnemonics for the same eight wastes, differing only in order and in what the letters spell. DOWNTIME is the more common today because the word itself reminds you that waste is lost production time. TIMWOODS is the older seven-waste mnemonic TIMWOOD with an S added for skills. Use whichever sticks on your floor; the wastes are identical.

What are the eight wastes, one by one?

Here is each waste in DOWNTIME order, with a plant-floor example and one way to detect it on a walk. This is the working reference to keep by the line.

1. Defects, work that has to be scrapped or reworked. Example: mislabeled cases that get pulled, relabeled, and repacked. Detection tip: watch for any rework loop, a bin marked "hold," or a station where operators inspect and fix rather than build. Track it as defect tracking and roll it up with DPMO.
2. Overproduction, making more, sooner, or faster than the next process needs. Example: running a full pallet of a component because the changeover is painful, when the next step will use a quarter of it this week. Detection tip: look for output that goes to a shelf instead of the next operation. This is the root waste; kill it and inventory, transport, and waiting shrink with it.
3. Waiting, idle time when work or people sit for the next step. Example: an operator standing by while a machine finishes a cycle, or a line stalled for a missing part. Detection tip: count the seconds a person or part is doing nothing; waiting shows up as the gaps in a value-stream map.
4. Non-utilized talent, failing to use people's knowledge, skills, and ideas. Example: the operator who knows exactly why a fixture jams but was never asked, so the fix never happens. Detection tip: ask how many improvement ideas came from the floor last month; a blank answer is the waste.
5. Transportation, moving material that the movement itself does not improve. Example: forklifting WIP across the plant to a stager and back because two processes are laid out far apart. Detection tip: trace the physical path of one part on a spaghetti diagram; every long line is transport waste.
6. Inventory, more raw material, WIP, or finished goods than flow requires. Example: weeks of components stacked at a line "just in case," aging and hiding quality problems. Detection tip: look for stacks between steps and rising inventory turnover days; excess inventory is stored overproduction.
7. Motion, unnecessary movement of people at the workstation. Example: an operator reaching, twisting, and walking to a shared tool cart every cycle. Detection tip: watch one operator for ten cycles and count steps and reaches; that is motion you can design out with point-of-use tools and 5S.
8. Extra-processing, doing more work than the customer requires. Example: polishing a surface that will be hidden, or double-keying the same data into two systems. Detection tip: ask which steps the customer would pay extra for; the ones nobody would are candidates. Poka-yoke often removes the checking steps added to catch defects.
9. (TIMWOODS order note) Skills is the same waste as non-utilized talent above; the two mnemonics simply place it differently.

How much of your lead time is actually value-adding?

In most unimproved processes, the share of total lead time spent actually transforming the product is small, often a single-digit percentage, with the rest consumed by the eight wastes. The gap between the moment a part enters and the moment it ships is mostly waiting in queues, sitting as inventory, and being moved. That is the prize lean chases: not making the value-adding steps faster, but removing the waste that surrounds them.

How do the eight wastes relate to muda, mura, and muri?

The eight wastes are the eight forms of muda, the most visible of the three Ms, but muda is usually a symptom of the other two. Mura (unevenness) makes a process lurch between overload and starvation, which throws off surplus inventory and idle waiting. Muri (overburden) pushes people and machines past their limits, which produces defects and breakdowns. Attack the eight wastes without addressing the mura and muri feeding them and the waste grows back. The full treatment of that relationship, including the classic overloaded-truck example, is in muda, mura, and muri; the point to carry here is that the eight wastes are what you see, and the three Ms are often why.

Which waste should you attack first?

Attack overproduction first, because it is the engine that creates most of the other seven. When you stop making more than the next process needs, the inventory between steps drains, the transport and motion that inventory demanded disappear, and defects surface faster because there is no pile to hide in. The practical levers are pull systems like kanban level scheduling, and small batches, which is why short changeovers matter so much to lean. After overproduction, let the data pick the target: a value-stream map shows where lead time actually goes, and defects usually earn priority next because they are the waste the customer feels directly. This is also where the eight wastes connect to equipment metrics, since setup, minor stops, and rework map onto the six big losses that drag OEE.

How do you make the eight wastes visible?

Waste is easy to name in a training room and hard to see in daily production, because most of it is normal. The wait feels like the way things are, the extra move feels like the job, and the small pile of WIP feels like being ready. Making waste visible takes two things: a regular gemba walk where leaders go look at the actual flow, and data that surfaces the waste automatically instead of waiting for someone to notice. When downtime, scrap, and slow cycles are captured live at the station rather than reconstructed from memory at end of shift, the eight wastes stop being an abstraction and become a Pareto you can work down. That shift from paper reconstruction to real-time capture is what CLS built with Harmony (see the CLS case study), and it is what keeps a waste-elimination program from quietly sliding back. No rip-and-replace, just the waste made visible enough to act on.