The 7 Wastes of Lean Manufacturing: How to Spot Them on Your Shop Floor
Every manufacturing process contains work that adds value and work that does not. The trouble is that the work which adds nothing rarely announces itself. It hides inside routines that feel normal, in the extra walk to fetch a tool, the pallet of stock waiting for a machine, the report nobody reads. Lean manufacturing gives this hidden work a name. It calls it waste, and it sorts it into seven recognisable types. The 7 wastes come from the Toyota Production System, the foundation of modern lean principles, where they were identified as the main drains on productivity that creep into any operation over time. Learning to see them is one of the most useful skills a team can build, because waste that stays invisible never gets removed and reducing waste is where most lean gains come from. This guide walks through each of the 7 wastes of lean manufacturing in turn, with the everyday signs that give each one away on the shop floor. The 7 Wastes of Lean Manufacturing A common way to remember the seven is the word TIMWOOD, formed from the first letter of each: Transport, Inventory, Motion, Waiting, Overproduction, Overprocessing and Defects. The mnemonic is handy on a walk, though the real skill is recognising what each one looks like in practice. 1. Transport Transport waste is the unnecessary movement of materials, parts or product from one place to another. Moving things is sometimes unavoidable, but every extra journey adds time, risk of damage and cost while changing the product not at all. It tends to be a symptom of layout. When a part travels back and forth across a site between steps that could sit closer together, transport waste is usually the reason. On the floor it shows up as forklifts and trolleys in constant motion, materials crossing the same aisle several times, and long gaps between consecutive operations. A quick way to find it is to trace the path a single part takes from goods in to finished product. The more that line doubles back on itself, the more transport waste there is to remove. 2. Inventory Inventory waste is stock sitting idle: raw materials, work in progress or finished goods held in greater quantity than the process needs right now. Excess inventory ties up cash, takes up space and hides other problems, because a generous buffer lets a team carry on without noticing the breakdown or delay that created the pile in the first place. The signs are physical and hard to miss once you look for them. Stacks of work in progress between stations, storage areas filling up, batches made well ahead of demand, and stock that gathers dust before it is used. Tighter production scheduling is often where the cure starts, matching what is made to what the next step actually needs. 3. Motion Where transport is about moving the product, motion waste is about the unnecessary movement of people. It covers the reaching, bending, walking and searching that operators do because tools, materials and information are not where they need to be. Each movement is small, but repeated thousands of times a shift it adds up to real lost time and avoidable strain. Watch an operator at one station for a few minutes and the waste appears: steps taken to fetch a tool that could be within arm’s reach, time spent hunting for a document, awkward stretches for parts stored too far away. Well run 5S audits attack this directly, organising a workspace so everything an operator needs sits where the work is done. 4. Waiting Waiting waste is idle time, when people or machines stand ready but unable to work. It happens when a step is starved of what it needs. The previous operation has not finished, a material has not arrived, an approval is outstanding, or a machine has stopped and nobody is yet free to fix it. The resource is available and paid for, yet producing nothing. It is one of the easiest wastes to see and one of the most revealing. Operators standing idle, machines stopped mid shift, queues of work building in front of a bottleneck while earlier stations sit quiet. Honest downtime data turns these moments from anecdote into evidence, showing how often the waiting happens and what keeps causing it. 5. Overproduction Overproduction is making more than is needed, or making it earlier than it is needed. Lean treats it as the most serious of the seven, because it sets off most of the others. Producing ahead of demand creates inventory to store, transport to move it and waiting further down the line, and it ties up effort that could have gone to what the customer actually wants now. It often looks like productivity, which is exactly what makes it dangerous. Machines kept running to hold utilisation figures high, large batches made because the changeover is awkward, products built to a forecast that has already moved on. A shift towards steadier flow production, where each step makes only what the next one is ready to take, is the lasting answer. 6. Overprocessing Overprocessing is doing more to a product than the customer needs or values. It is effort spent on tolerances tighter than the specification, finishes nobody asked for, checks duplicated across several stages, or paperwork filled in twice because two systems do not talk to each other. The work feels diligent, yet it adds cost without adding worth. Spotting it takes a harder look than the others, because the activity is usually well intentioned. The questions to ask are simple. Does this step change anything the customer would pay for? Is this inspection already done elsewhere? Is this form recorded twice? Wherever the answer is no, overprocessing is quietly draining time and attention. 7. Defects Defects are products or outputs that fail to meet the standard and have to be scrapped, reworked or corrected. This is the most visible waste and often the most expensive, because a defect consumes everything already
How to Build a Continuous Improvement Process That Actually Sticks
Walk into almost any plant and you will find the remains of a continuous improvement push. A faded board in the corner, a folder of suggestion forms nobody reads, a set of targets from a project that wrapped up eighteen months ago. The intent was real. What was missing was a way to keep it going once the launch buzz wore off and the next urgent problem walked through the door. That is the hard part. Starting a continuous improvement programme is easy, because enthusiasm is cheap at the beginning. Keeping one alive through the months when nothing feels dramatic is what separates plants that improve year after year from those that lurch from one initiative to the next. A continuous improvement process is the system that carries the work through those quiet months, turning the occasional burst of effort into a steady habit that survives staff changes, shifting priorities and the daily pull of firefighting. This guide covers what a continuous improvement process actually is, why so many of them fade within a year, and how to build one that holds. What a Continuous Improvement Process Really Is The word process is doing a lot of work in that phrase. An improvement project has a start, a finish and a problem it was created to solve. A continuous improvement process has none of those edges. It is an ongoing loop of spotting an issue, making a small change, checking whether it helped and then doing it again, repeated so often that it stops feeling like a separate activity at all. Most plants already have a method to hang this on. The PDCA cycle gives the loop its plan, do, check and act rhythm, and lean thinking supplies a steady stream of waste to remove. The framework matters far less than the discipline of keeping the loop turning when no crisis is forcing it. Seen that way, achieving continuous improvement has less to do with any single initiative and more to do with whether the loop has quietly become routine. The contrast between the two approaches is worth setting out plainly. Aspect One off improvement projects An embedded improvement process Trigger A crisis, audit finding or annual push Part of the daily routine Frequency Occasional, when time allows Continuous, every shift Ownership A central team or outside consultant The people who run the process Visibility Buried in a report On a board the whole team can see What happens to gains Fade once attention moves on Held in place through standard work Why Most Continuous Improvement Efforts Fade Before building a process that lasts, it helps to know exactly how they tend to die. The failures are remarkably consistent from one site to the next, and the same common barriers come up time after time: Look closely and they share a single cause. Improvement was added on top of an already full working day, so it was always going to lose when something more urgent arrived. A process that sticks is one that is built into the day rather than balanced on top of it. How to Build a Continuous Improvement Process That Lasts A durable process rests on five conditions. None is complicated on its own. The skill is in putting all five in place at once and letting them reinforce each other. Start small and anchor to a real problem Ambition kills more improvement programmes than apathy. A plan to transform a whole site at once spreads effort so thin that nothing moves, and the lack of visible progress drains belief fast. A process that lasts starts narrow, in one area or on one line, on a problem people can actually see. A changeover that routinely overruns by twenty minutes is a far better starting point than a goal to improve efficiency, because everyone can picture it and everyone can tell when it gets better. Whatever the problem, it needs a baseline in numbers before anyone touches it. Without a clear before, there is no honest after, and the most demoralising outcome in any programme is hard work that cannot be shown to have changed a thing. Win something small and visible first, then widen out from there. Build improvement into the daily rhythm Improvement only survives when it owns a slot in the working day that nothing else is allowed to take. The most dependable way to protect that slot is a layered cadence of short, structured meetings. A brief daily huddle at the start of each shift surfaces yesterday’s problems and today’s risks in a few minutes. Tiered tier meetings then carry the issues a frontline team cannot solve up to the people who can, so nothing stalls for want of a decision. When the rhythm is fixed and short it stops competing with the work and becomes part of it. The changeover problem gets aired at the huddle the next morning, not parked for a quarterly review that may never come. Put improvement in the hands of the front line The operators running a process see its faults first and understand them best, yet in most plants they are the last to be asked and have no easy way to flag what they notice. A continuous improvement process that lasts hands them a direct line. A connected worker approach lets frontline teams log a problem or an idea the moment it happens, while it is still fresh and specific, rather than losing it to the end of a busy shift. Structured gemba walks put leaders out on the floor where the work is done, asking what is getting in the way instead of waiting for a report to tell them. Ownership is the quiet engine of the whole thing. People protect what they helped build, and they quietly drop what is handed down to them. Make problems and progress visible Improvement fades in the dark. When the only record of performance is a monthly report, a problem is weeks old before anyone reacts and