Lean is easier to understand through examples than definitions. This guide pairs common problems with the lean tool that addresses them.
The shop-floor examples are typical situations, not case studies of named companies. The examples outside manufacturing come from published sources.
Key takeaways
Each lean tool answers a specific kind of waste, such as waiting, searching or rework.
The tools work in combination, because they support each other.
The same ideas apply outside factories, in hospitals, offices and software teams.
Toyota: where the examples start
The Toyota Production System is the original lean example. Toyota describes it as resting on just-in-time and jidoka.
Just-in-time means each process makes only what the next process needs, when it needs it. Jidoka means machines and people stop when something goes wrong, so problems are fixed at the source.
Most of the examples below are one of these two ideas, applied to a specific problem.
Long changeovers: SMED
Problem: a press takes a long time to change from one part to the next. So the plant runs large batches and holds a lot of stock.
Lean fix: the team films a changeover. It separates internal steps, done while the press is stopped, from external steps done while it runs. Tools and dies are staged in advance.
Result: shorter changeovers make smaller batches practical. The SMED page walks through the method.
Stockouts and overstock: kanban
Problem: a line runs out of some parts while others pile up, because orders follow a forecast rather than actual use.
Lean fix: a two-bin kanban system. When the first bin empties, its card triggers a refill while the line works from the second bin.
Result: stock is replaced as it is used. E-kanban software does the same with barcode scans when there are many parts or suppliers.
Searching for tools: 5S
Problem: operators spend time looking for tools, gauges and paperwork.
Lean fix: a 5S event sorts out what is not needed and gives every remaining item a marked place, such as a shadow board.
Result: missing items are obvious at a glance. The 5S and kaizen guide explains how to keep it that way.
Repeat defects: poka-yoke and andon
Problem: the same assembly error keeps reaching final inspection.
Lean fix: an operator pulls the andon when a part will not fit. The team finds the cause and adds a poka-yoke fixture that only accepts the part the right way round.
Result: the error is prevented at the station rather than caught later. Andon software can record each call and the response time.
Unbalanced line: takt time
Problem: some stations wait while others are overloaded, and output falls short of demand.
Lean fix: the team calculates takt time and rebalances work so each station's cycle time sits just under it. The takt time calculator helps with the numbers.
Result: work flows at the pace of demand, and the bottleneck becomes visible.
Lean in healthcare
Virginia Mason in Seattle began applying the Toyota Production System to health care in 2002. Its system includes the idea that staff can stop the process when they see a safety problem.
That is jidoka, applied to patient safety instead of car parts.
Lean in software and startups
Software teams use kanban boards with work-in-progress limits to keep work flowing. The guide on why limiting WIP makes teams faster explains the effect, and flow metrics tools measure it.
Startups apply lean to product development with build-measure-learn, from Eric Ries's The Lean Startup. The smallest useful test replaces a full product launch.
Finding your own example
Walk your process and look for the eight wastes, from waiting to unused talent. The eight wastes page lists them.
Pick the one that costs the customer most and match it to a tool above. The lean manufacturing guide shows how the tools fit together.
Frequently asked questions
What are examples of lean manufacturing?
Which lean tool fixes long changeovers?
Is lean only for factories?
Where did lean manufacturing start?
Choosing E-Kanban Software?
Read the buying guide: what to look for, mistakes to avoid and questions to ask vendors.