Jidoka is one of the two pillars of the Toyota Production System. It is often translated as “automation with a human touch,” but the operational idea is broader: when an abnormality occurs, the process should detect it, stop or contain it, make the problem visible and prevent the defect from flowing downstream.
The Jidoka Logic
- Detect an abnormal condition.
- Stop or contain the process so the problem does not continue.
- Correct the immediate condition.
- Investigate the cause and improve the process so recurrence is less likely.
Andon and Visibility
An Andon is a visual or audible signal used to make an abnormality visible. In a warehouse this could be an exception screen for a scan mismatch; in manufacturing it may be a line signal; in an order process it can be a system block that prevents release when mandatory data is missing.
Supply-Chain Examples
| Process | Abnormality | Jidoka-style response |
|---|---|---|
| Receiving | PO quantity does not match receipt | Block posting and route to exception review |
| Picking | Wrong barcode scanned | System rejects scan before packing |
| Transport | Temperature excursion | Alert, hold shipment and assess disposition |
| Procurement | Supplier bank details changed | Stop payment workflow pending independent verification |
Jidoka vs Poka-Yoke
Jidoka is the broader principle of detecting abnormalities and stopping/containing the process. Poka-yoke is a mistake-proofing method used to prevent errors or make them immediately obvious. Poka-yoke can therefore support Jidoka.
See Poka-Yoke: Mistake Proofing.
Interview Question
Question: Why would a Lean system deliberately stop a process?
Answer: Continuing to produce or process defects creates more waste and hides the root cause. Jidoka makes the abnormality visible and contains it early so quality is built into the process rather than inspected only at the end.
Reference
Toyota Motor Corporation — Toyota Production System, Jidoka and Just-in-Time.
Comments 1