8 Wastes / Muda
Run a waste walk that ends with measurable opportunities
A waste walk is useful when it helps you understand how work really moves. It is not a tour for finding people who look busy or idle. Define a process or product flow, go to the place where the work happens, observe before proposing solutions and record specific evidence. The goal is to leave with a small number of measurable opportunities that can be investigated and verified.
- Define scope
- Observe
- Classify
- Measure
- Investigate
- Return and verify
Before the walk: define the scope
Choose one process, product family, service flow or handoff - not the whole plant at once.
State the purpose: what flow or problem are you trying to understand?
Know the expected demand, standard, quality requirement or process condition when it matters to the observation.
Bring the people who know the work into the conversation. Observe the process; do not score individual effort.
Do not bypass safety, quality, regulatory or required controls in the name of removing waste.
What to look for
| Waste | Observation questions | Possible evidence |
|---|---|---|
| Defects | Where is work corrected, repeated, sorted or scrapped? | count; defect type; rework minutes; material affected |
| Overproduction | Where is work made earlier or in greater quantity than current need? | produced vs demand; queue/WIP; schedule signal |
| Waiting | Where is work stopped for material, information, approval, equipment or the next step? | minutes/event; frequency; queue age |
| Non-utilized talent | Where does the system fail to use knowledge, capability or improvement ideas? | task/capability mismatch; blocked idea; repeated avoidable clerical work |
| Transportation | Where does material or information travel without changing the required output? | trips; distance; touches; handoffs |
| Inventory | Where is raw material, WIP or finished work accumulating beyond current need? | quantity; age; days of supply; WIP |
| Motion | Where do people repeatedly walk, reach, search or reposition without advancing the work? | steps; distance; search time; frequency |
| Extra-processing | Where is work duplicated or performed beyond the actual requirement? | extra steps; repeat inspection; duplicate entry; minutes |
Record before you solve
For each observation, capture a plain description, the process/location, the waste category, what evidence exists, the observed frequency and duration/quantity, the current requirement or demand when relevant, and what still needs to be learned. If a hazard appears, route it to the appropriate safety process rather than treating the safety issue as merely a Waste countermeasure.
Quantify without inventing certainty
Start from observed data. Example: 12 minutes of waiting x 6 events per shift = 72 minutes per shift. If the observation period is short, label any extrapolation as modeled. Do not multiply released labor time by an hourly rate and call it realized cash savings unless actual spending changes and the evidence supports that classification.
Separate category, cause and countermeasure
The waste category names the pattern. Root-cause work explains why it happens. The countermeasure is the change you test. Keeping those three separate prevents a checklist from turning into a list of preferred solutions. Use 5 Whys or Fishbone when the cause is not yet understood; use Process Map or Time Study when the flow or timing needs more evidence.
5 Whys · Fishbone · Process Map · Time Study
Return and verify
A waste walk is incomplete if the team never returns to the process. After the countermeasure, repeat the same measurement where practical. Record the before condition, the after condition and any tradeoff or new risk. Then classify the value honestly: capacity/time released, realized cash, cost avoidance, modeled opportunity, countermeasure investment and recurring cost are different things.