Lean teams use jidoka to build quality in at the source instead of inspecting it in later. Stopping feels costly in the moment but prevents batches of bad parts. Each stop also becomes a chance to learn and improve the process.
Where it comes from
Jidoka traces back to Sakichi Toyoda's automatic loom, which stopped itself when a thread broke. It became one of the two pillars of the Toyota Production System, alongside just-in-time.
At a glance
Detect, stop, signal, fix
Swipe sideways to see the whole diagram.
How to apply Jidoka
- 1
Detect the abnormality
Use sensors, error-proofing devices or clear visual standards so abnormal conditions are noticed immediately. Detection should not depend on someone remembering to check.
- 2
Stop the process
Have the machine stop automatically, or give the operator authority to stop. The goal is that no defect passes to the next step.
- 3
Signal for help
Link the stop to an andon so a leader responds quickly. Make the location and type of problem visible.
- 4
Fix the immediate problem
Contain any suspect parts and restore normal conditions. Restart only once the process is producing good work again.
- 5
Find and fix the root cause
Investigate why the abnormality happened using tools like five whys. Add a countermeasure, often a poka-yoke, so it does not recur.
Worked example (illustrative)
A bottling station adds a sensor that stops the capper when a cap is missing or crooked. The stop lights an andon, and the team leader clears the jam and quarantines the last 20 bottles for a check. The capper stops about 9 times in the first week, nearly all from one point in the cap chute. The team adjusts the chute, and stops fall to 1 or 2 a week. Before the sensor, crooked caps were found only at the end of the line, often after a full case had been packed.
Common mistakes
- Letting the line keep running with known defects to protect output numbers.
- Restarting after the quick fix without investigating the root cause.
- Relying on end-of-line inspection instead of detection at each step.
When Jidoka is not the right tool
Some processes, such as continuous chemical flows, cannot simply stop. There, jidoka means detecting the problem early and containing it, then fixing the cause.
Stopping also needs a response. A stop without fast help only lowers output.
Jidoka meaning
Jidoka means stopping a process at the first sign of an abnormality, so defects do not move downstream. It is often translated as automation with a human touch.
Jidoka and just-in-time are the two pillars of the Toyota Production System.
Autonomation
Autonomation is the English word often used for jidoka. A machine detects a problem and stops itself, so one person can watch several machines.
The human part matters as much as the machine part. People also stop the line, often with an andon cord or button, when they see a problem.
The first minute after a stop: two examples
These examples are illustrative. A press stops because a sensor finds no part in the die. The light shows yellow, the team leader arrives within about a minute, removes the misfed blank and checks the last few parts. If the cause is not clear, the press stays stopped while the team asks why the feeder misfed.
A build pipeline stops a release because 2 of 1,400 automated tests fail. Nothing ships. The engineer who made the last change is alerted, reproduces the failure and either fixes it or reverts the change. The team then asks why the defect was not caught earlier, such as a missing test at the point of the change.
Jidoka, andon and poka-yoke
Jidoka is the principle. Andon is the signal that shows a stop and calls for help. Poka-yoke devices detect or prevent specific errors.
Guides on this topic
- Lean healthcare: principles, tools and how to startLean healthcare applies lean methodology to patient care. See the principles, hospital wastes, tools, patient flow and how to start in a clinic or ward.Read the guide
- Root cause analysis example: 6 worked samples and a templateA root cause analysis example for six settings, from a machine stoppage to warehouse picking errors, plus root cause statement wording and a free one-page RCA template.Read the guide
- How to write an A3 report: step by step, with an exampleHow to write an A3 report section by section, with a filled A3 example, coaching questions for each box and a free printable A3 template.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production (Productivity Press, 1988)
- 2.Toyota Motor Corporation, Toyota Production System (global.toyota, checked October 2026)
- 3.Jeffrey K. Liker, The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer (McGraw-Hill, 2004)