Most people first meet the 8 wastes on a laminated poster in a factory canteen. TIMWOODS, it says, with a clip-art conveyor belt underneath. The problem is that poster suggests wastes belong to the shop floor. They do not. A nurse walking across a ward to find supplies, an accountant rekeying data someone already entered, a marketing team waiting three days for legal sign-off on routine copy: same eight wastes, different setting.
Understanding each waste through real examples, across industries, turns the acronym from something teams can recite into something they can actually see.
What waste means in Lean
In Lean, waste, or muda, is any kind of action or process that doesn't provide value to the customer. If your customer would not pay for it, it is waste. That definition is intentionally broad. It covers obvious things like scrap and rework, but it also catches the invisible drains: the admin sign-off that adds three days of waiting, the report nobody reads, the skill no one asks the operator about.
Not all waste can be eliminated. Some activities, like machine setups or safety checks, count as necessary waste. They do not add direct customer value but cannot be skipped. The goal is not total elimination. It is systematic reduction: shrink the setup time, batch the safety checks, make what cannot be removed as lean as possible.
The concept originated in the Toyota Production System and has become the foundation of continuous improvement programs worldwide.
Where the 8 wastes came from
Taiichi Ohno, the father of the Toyota Production System, originally identified the seven wastes, also known as TIMWOOD. He categorised these unproductive manufacturing practices to remove them from work processes.
The 8th waste, non-utilised talent, was added later. The original Toyota Production System did not acknowledge it. But over time, practitioners recognised that underusing a workforce's knowledge, creativity, and problem-solving ability is itself a form of waste, and arguably the most expensive one. It became the S in TIMWOODS, for Skills.
Two acronyms, same eight wastes: TIMWOODS and DOWNTIME
If you have heard both terms and wondered whether they describe different frameworks, they do not. Both map to the same eight categories. The only difference is the letter order.
| Letter | Waste | What it means |
|---|---|---|
| T | Transport | Unnecessary movement of materials and products |
| I | Inventory | Stock that sits instead of flows |
| M | Motion | Excess movement by people |
| W | Waiting | Idle time between process steps |
| O | Overproduction | Making more than needed, sooner than needed |
| O | Overprocessing | Doing more than the customer asked for |
| D | Defects | Work that needs redoing |
| S | Skills | Non-utilised talent and capability |
DOWNTIME stands for Defects, Overproduction, Waiting, Non-Utilized Talent, Transportation, Inventory, Motion, and Extra-Processing. Use whichever your team will remember.
Here is each waste, what it looks like away from the factory floor, and one concrete action to reduce it.
1. Transport: unnecessary movement of materials and products
Transport waste is any unnecessary movement of products or materials between process steps. It includes extra handling, excessive conveyance, inefficient facility layouts that force things to travel further than they should.
In a warehouse, this might look like receiving goods at one end of the building, storing them at the other, then moving them back for dispatch. In an office, it looks like a document being emailed to five people for sequential review when a shared workspace would let everyone see it at once.
Transport waste makes materials more susceptible to damage and defects, adds wear and tear to equipment, and can lead to premature fatigue. Every unnecessary move is an opportunity for something to go wrong.
This week: Map one physical path a document, part, or file takes through your workplace. Count the handoffs. If there are more than three, ask whether the layout or the process is the problem.
2. Inventory: stock that sits instead of flows
Inventory means anything waiting: raw materials, work-in-progress, finished goods, unread reports, unactioned approvals. Excess inventory ties up working capital, costs money to store, and runs the risk of damage, obsolescence, and delay.
A hospital stores thousands of consumable items. Over-ordering ties up budget and risks expiry. In an office, a shared inbox with six hundred unread messages is inventory waste. Nothing is flowing. Everything is sitting.
Inventory waste hides problems. If you always have buffer stock, you never feel the pain of an unreliable supplier, so you never fix the supply chain.
This week: Identify one item, physical or digital, your team keeps "just in case." Calculate what holding it costs: storage space, expiry risk, the interest on the cash tied up. Decide whether the buffer is cheaper than fixing the root cause.
3. Motion: excess movement by people
Motion is not Transport. Transport moves the product. Motion moves the person. It is any excess movement by employees not directly adding value: looking for tools, excessive walking to get materials, poor ergonomics causing strain.
The classic manufacturing example is an operator walking twenty metres to a tool cabinet forty times a shift. That is eight hundred metres of non-value-adding walking every day.
In a hospital, a nurse might spend more time walking to supply rooms than at the bedside. In an office, someone working across three different software platforms, copying data from one to another, is in motion waste. The screen work looks static, but the mental motion of context-switching and rekeying is real.
This week: Shadow one person for half an hour. Time how long they spend looking for things, walking, or switching between systems. Show them the number. People rarely notice their own motion waste until it is measured.
4. Waiting: idle time between process steps
Waiting is idle time when no work is being done. It comes from equipment failures, delayed materials, the next step in the process not being ready.
Waiting is often the largest single waste in service environments. A team member waits for a manager to approve a purchase order. A developer waits for a code review that sits in a queue for two days. A patient waits for test results that were run yesterday but not yet reviewed.
The data bears this out. Guidewheel benchmark data from over 3,000 tracked machines shows the weighted average runtime was only 54.54% and the median runtime was just 32.04%. More than half of available machine time is idle. People time looks similar.
This week: Pick one recurring handoff in your team's workflow. Measure how long work sits waiting at that handoff versus how long it takes to actually complete. The ratio will tell you whether the bottleneck is capacity or process design.
5. Overproduction: making more than needed, sooner than needed
Overproduction means producing more products than the customer has ordered. It overstocks inventory and cascades into extra transportation, storage, and handling waste.
In a service setting, overproduction looks like printing a fifty-page monthly report that two people skim. Or building a feature in a software release that no user asked for and no user uses. Or running a training session for thirty people when only eight needed the content.
This week: Find one recurring output your team produces, a report, a meeting deck, a summary email, and ask who actually uses it. If the answer involves a shrug, stop producing it for a month and see who notices.
6. Overprocessing: doing more than the customer asked for
Overprocessing means going beyond customer requirements: over-engineering products, using unnecessarily tight tolerances, or adding features customers will not pay for.
A machined component with a surface finish spec ten times tighter than the application requires is overprocessing. So is a sixty-slide board presentation when a one-page summary would answer the same question. So is a purchase approval chain with four signatories when two would cover the risk.
Overprocessing often masquerades as quality. The team feels proud of the extra effort. The customer does not notice. The cost is real regardless.
This week: Review one deliverable your team produces. Find the part that takes the most effort. Ask: does the customer ask for this, or do we? If you cannot name the customer requirement it serves, it is a candidate for reduction.
7. Defects: work that needs redoing
Defects are usually considered the worst of the wastes because they require reworking or scrapping. Scrapping and reworking adds cost without adding any value for the customer.
The manufacturing example is familiar: a batch of components fails inspection and must be remade. In an office, it is a data entry error that makes its way into a client invoice, triggering a correction, an apology, and a financial adjustment. In healthcare, it is a medication error caught before administration, or worse, not caught.
Each defect consumes the resources of the original work plus the rework. The cost multiplier is never one-to-one. The rework disrupts whatever the person should have been doing instead.
This week: Log every rework event your team handles for five working days. Categorise by root cause. A pattern will emerge within the first week, and the biggest category is your next improvement project.
8. Non-utilised talent: the 8th waste
Non-utilised talent was not acknowledged by the original Toyota Production System. It was added later because the gap was too large to ignore: the people doing the work every day have the most detailed understanding of how it could be done better.
The consequence is inefficient, stale processes and a workforce that does not feel comfortable offering suggestions. The person closest to the work knows exactly what is wrong and exactly what would fix it. If no one asks, that knowledge stays unused. The waste compounds: the problem persists, the worker disengages, and the improvement that would have paid for itself ten times over never happens.
This is the waste that eats all others. Standardise a process without consulting the people who run it, and Motion, Waiting, and Defects wait around the corner.
This week: Pick one recurring problem in your team's workflow. Ask the person closest to it what they would change. Write their answer down. Do not debate feasibility. Just capture it, and take one step toward making it happen.
How to spot waste: waste walks and value stream mapping
Identifying waste requires structured observation. A waste walk is a structured approach where a team walks through a workspace observing workflow to identify instances of TIMWOODS wastes. It works because you see things in the physical space that you filter out when sitting at your desk.
Value stream mapping complements the waste walk by putting the entire process on one page: every step, every handoff, every delay. Together, the walk and the map turn vague feelings of inefficiency into a list of specific, actionable wastes.
SimplicityHub has both an 8 Wastes Assessment Template and a Waste Identification Checklist that give you a structured starting point for waste walks and VSM exercises. Rather than beginning with a blank sheet, a template ensures you cover all eight categories systematically.
The real cost: what the data says about hidden capacity
The Guidewheel benchmark data puts hard numbers behind what practitioners have always suspected: most operations run far below their true capacity. With a weighted average runtime of 54.54% and a median of just 32.04% across over 3,000 tracked machines, the hidden capacity waiting inside most operations is enormous. Waste elimination is not a marginal gain. It is an untapped shift's worth of output.
The data also reveals where the pain concentrates. Material and supply issues caused an average of 334.4 lost hours per production line per year, with each event lasting nearly two hours, far longer than mechanical breakdowns. Waiting for materials is often a planning problem dressed as a supply chain problem.
Changeover variability adds another layer: a median variability of 56.6% means the same changeover can take wildly different amounts of time from run to run. That inconsistency is a clear signal of extra-processing and waiting waste. Standard work and data visibility are the fix, and they cost far less than a new machine.
The 8 wastes framework persists because it works at any scale. A team of five can use it. A multinational plant network can use it. The categories do not change when the context does. A defect is a defect whether it is a faulty weld or a billing error. Waiting is waiting whether it is a blocked assembly line or an unread approval sitting in someone's inbox. Learn to see the wastes, and improvement stops being a programme. It becomes a habit.