New to this topic?
We recommend reading these guides first to get the most out of this one:
Jidoka
Pillar #2 of TPS
Stop
Fix Before Passing
Andon
Signal the Abnormality
Zero
Defects Forward

What Is Jidoka?

Jidoka is one of the two pillars of the Toyota Production System (alongside Just-in-Time). Translated as "autonomation" or "automation with a human touch," it means building the ability to detect abnormalities into the process itself — and stopping immediately when one is found.

The core principle: never pass a defect to the next process. Every operator has the authority and responsibility to stop the line when they see a problem. This feels counterintuitive — stopping production costs money. But passing a defect forward costs far more: it multiplies through downstream processes, becomes harder to find, and eventually reaches the customer.

The Origin Story

Jidoka dates to Sakichi Toyoda's automatic loom in 1896. He built a mechanism that stopped the loom automatically when a thread broke, preventing defective cloth from being produced. One operator could then monitor dozens of looms instead of watching one constantly. The machine detected its own problems — that is autonomation.

The Four Steps of Jidoka

Detect the AbnormalityThe process itself identifies that something is wrong. This can be a machine sensor, a poka-yoke device, an operator's trained eye, or an automated vision system. The key: detection happens at the source, not downstream.
StopProduction stops immediately. The machine shuts down, or the operator pulls the andon cord. No "let me just finish this batch" — stop now. The cost of stopping for 5 minutes is always less than the cost of producing 50 more defects.
Fix the Immediate ProblemRestore normal conditions. Replace the broken tool, adjust the setting, remove the defective part. Get the line running again as quickly as possible. This is containment.
Investigate and Prevent RecurrenceAfter production resumes, do root cause analysis. Why did the abnormality occur? Install a permanent countermeasure so the same problem never happens again. This is where poka-yoke and process improvement live.
Detect
Stop
Fix
Prevent
Jidoka cycle: detect → stop → fix → prevent. Each cycle permanently improves the process.

The Andon System

Andon is the visual and audible signal system that supports jidoka. When an operator detects a problem, they activate the andon (pull a cord, press a button), which triggers a light, a sound, and a display showing which station needs help.

SignalMeaningResponse
🟢 GreenNormal operationNo action needed
🟡 YellowOperator needs assistance (but can continue for now)Team leader responds before the next cycle
🔴 RedLine stopped — abnormality that cannot continueTeam leader + supervisor respond immediately

Andon Only Works If Leaders Respond

If an operator pulls the andon cord and no one comes, they will never pull it again. The response time to an andon call is one of the most important metrics in a jidoka culture. Target: team leader responds within one cycle time. If response is slow, operators will stop using the system and defects will flow downstream.

Building a Stop-and-Fix Culture

The technical system (sensors, andons, poka-yoke) is the easy part. The cultural shift is harder: convincing everyone that stopping the line is good, not bad.

Culture ShiftFromTo
Stopping the line"You stopped production! What happened?""Thank you for stopping. What did you catch?"
Defect ownership"QC will catch it downstream""I will never pass a bad part forward"
Problem responseInvestigate after the shift (if at all)Root cause within the shift
Operator authority"Keep running, we will sort it later"Every operator can stop the line

Levels of Built-In Quality

LevelMethodEffectiveness
1. End-of-line inspectionInspector checks finished productWeakest — defects already made, cause hard to trace
2. Successive inspectionNext operator checks previous operationBetter — quick feedback, but still after the fact
3. Self-inspectionOperator checks their own work each cycleGood — immediate feedback at the source
4. Source inspectionPoka-yoke prevents the error from occurringBest — defect is impossible, not just detected
✅ Jidoka Culture
  • Operators empowered to stop the line
  • Andon calls responded to within one cycle
  • Every stop triggers root cause investigation
  • Poka-yoke installed for every recurring defect
  • Quality metrics owned by production, not just QC
❌ Inspection Culture
  • "Quality is QC's job, not mine"
  • Defects passed forward and sorted at the end
  • Line stops are punished or discouraged
  • Same defects recur because root causes are not fixed
  • Inspection headcount grows instead of prevention investment

🎯 Key Takeaway

Jidoka means quality is built into the process, not inspected after the fact. Give every operator the authority to stop, respond instantly when they do, fix the root cause permanently, and install poka-yoke so the problem can never recur. Over time, your line stops less — not because people stopped pulling the andon, but because there are fewer problems to detect. That is built-in quality.

Interactive Demo

Simulate a production line with and without Jidoka. See how automatic defect detection prevents quality escapes.

⚑
Try It Yourself
Jidoka β€” Autonomation Simulator
β–Ό
Introduce a defect, then run the line. Without Jidoka, defects pass through all stations. With Jidoka enabled, the line stops at the inspection station, triggers an andon alert, and contains the defect.
🏭
Raw Material
βš™οΈ
Machining
πŸ”§
Assembly
πŸ”
Inspection
πŸ“¦
Packaging
0
Total Runs
0
Defects Shipped
0
Defects Caught
0%
Escape Rate
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check β†’
🏭
Free Process Modeler
Map your production flow, find bottlenecks & optimize staffing. No login required.
Try It Free →
Free forever · No credit card

Stop reading, start doing

Model your process flow, optimize staffing with Theory of Constraints, and track every shift — all in one platform. Set up in under 5 minutes.

Start Free → Try Process Modeler