Lean teams know how to follow a part through the plant. Few follow the information that travels with it. Yet a large share of the delays on the shop floor are not caused by material, but by a document, a number or a decision that arrives late.
An information waste walk makes that visible in two hours.
The five information wastes
The classic wastes have an information version:
- Waiting: for a drawing, a release, a decision, a call back.
- Transport: paper carried to an office, a clipboard collected at the end of the shift.
- Overprocessing: the same number written on paper and typed into a system, sometimes twice.
- Defects: the wrong version of an instruction, a typing error in a quantity.
- Searching: walking to find the current document or the person who knows.
How to walk
Form pairs and give each pair one piece of information to follow through one shift: a production order, a machine stop, a drawing, a quality result. Each pair records where the information is created, where it is used, how long it waits and how often it is retyped.
In one machining hall with twelve machines the walk produced this picture:
| Information | Delay | Typed |
|---|---|---|
| Machine stop and reason | 5 days until the weekly report | 2 times |
| Quantity per order | until the end of the shift | 2 times |
| Current drawing and program | 10 to 20 minute walk | 0 |
| Call for maintenance | 14 minutes average | 0 |
| First part release | 25 minutes average | 1 time |
Read the result
Every line is a candidate for a use case, and some are not digital at all. The walk to the drawing may be solved by a terminal at the machine. It may also be solved by a fixed document place and a rule that engineering updates it.
Three questions sort the findings:
- How much time or capacity does it cost per week? Minutes times frequency.
- Can it be fixed without software? A standard, a route, a rule.
- If not, what data would solve it? That is the use case.
The machine stop in the example costs the most: losses are known five days late and nobody can act on them. It became the first use case: automatic machine states with a reason for every stop.
Measure before you change
Write down the delays and retyping counts before any system arrives. This baseline is the only honest way to show the benefit later. Without it, the project report will compare the new system with a memory.
Involve the people who wait
Operators and team leaders know where they wait. Invite them to walk, not only to watch. People who found the waste themselves will use the solution that removes it, and they will tell you early when it does not.