Which lean manufacturing tool fixes which production problem?
Start from the loss you can see on the floor, then pick the tool built for it.
| Production problem | Lean manufacturing tool | What it does |
|---|---|---|
| Cluttered, hard-to-read workplace | 5S | Organises the area so abnormal conditions stand out |
| Every operator does the job differently | Standard work | Sets the current best method as the baseline |
| Too much work in progress | Kanban | Produces only what the next process has used |
| Long changeovers, large batches | SMED | Cuts setup time so small batches pay |
| Breakdowns and slow running | Total productive maintenance and OEE | Keeps machines available and measures the losses |
| Defects reaching the next step | Poka-yoke and jidoka | Make errors hard to make and stop the line when one occurs |
| Production out of step with demand | Takt time | Paces output to customer demand |
| Nobody sees where lead time goes | Value stream mapping | Shows every step from order to delivery |
| The same problem keeps returning | PDCA, 5 whys and A3 | Find and fix the root cause |
Where should a plant start with lean manufacturing tools?
Start with the tools that make problems visible: 5S, a simple visual board and standard work for the busiest line. Visibility comes before improvement, because you cannot reduce a loss nobody can see. Add value stream mapping once the area is stable, then choose flow tools (kanban, takt time, SMED) where the map shows waiting and inventory.
Are lean manufacturing tools enough on their own?
No. Tools find and fix problems; they do not keep the gains. A 5S blitz or kaizen event lifts results for a few months and then slips unless daily routines hold the standard in place: tiered daily management, gemba walks and layered audits. This is the difference between using lean tools and running lean manufacturing as a management system.
Example
A packaging line lost about two hours a shift to changeovers and unplanned stops. The team ran a quick value stream map, split changeover tasks into those done while the machine runs and those that need it stopped (SMED), posted stops by cause on a board at the line, and wrote the new changeover as standard work. Stops by cause were reviewed at the start of every shift, so the new method stuck.