Menu
Jidoka (Autonomation): The Lean Pillar Explained

Jidoka (Autonomation): The Lean Pillar Explained

Jidoka is "automation with a human touch," a TPS pillar that detects abnormalities, stops the line, and forces root-cause fixes. See the 4 steps and modern uses.
Jidoka (Autonomation): The Lean Pillar Explained

Key takeaways

See our roundup of the analytics layer that surfaces the signals Jidoka acts on.

  • Jidoka, often translated as autonomation or automation with a human touch, is one of the two pillars of the Toyota Production System, alongside Just-in-Time.
  • It follows four steps: detect the abnormality, stop, fix the immediate condition, and investigate the root cause so the defect never recurs.
  • Jidoka builds quality into the process by stopping the flow the moment a defect appears, which protects OEE Quality losses and reduces unplanned downtime hidden inside micro-stops.
  • Modern jidoka uses sensors, PLC signals, computer vision, and digital andon to detect abnormalities in real time and trigger a parts-ready work order on the responsible technician's phone.

Jidoka is a Toyota Production System pillar that means "automation with a human touch." It gives machines and operators the ability to detect an abnormality, stop work immediately, fix the immediate condition, and investigate the root cause, so defects are never passed downstream and quality is built into every process.

What does jidoka mean in lean manufacturing?

Jidoka means "automation with a human touch," and it is the rule that work must stop the instant an abnormality is detected so a defect is never passed to the next process.

The Lean Enterprise Institute defines it as "providing machines and operators the ability to detect when an abnormal condition has occurred and immediately stop work." It is sometimes called autonomation , which captures the idea that the machine itself, not a babysitter, decides whether the part is good.

The word is written 自働化 in Japanese. Toyota deliberately added the human radical 人 inside the standard kanji for "automation" to signal that the machine now has a kind of human judgment. The translation "automation with human wisdom" comes from Toyota's own corporate history.

Where did jidoka come from?

Jidoka started in a weaving shed, not a car plant. In the early 1900s, Sakichi Toyoda built an automatic loom that stopped on its own the moment a single thread broke. Before that, one bad thread could ruin a whole roll of cloth while the loom kept running. After it, one operator could safely tend several looms, because each one would simply stop and signal if anything went wrong.

That invention seeded the modern Toyota Production System. As Toyota's official history puts it, jidoka "was created from the enthusiasm and practices of Sakichi Toyoda in automatic loom development," and was later carried into car manufacturing by Taiichi Ohno.

What are the two pillars of the Toyota Production System?

The two pillars of the Toyota Production System (TPS) are Just-in-Time and Jidoka. JIT is about making only what is needed, when it is needed, in the amount that is needed. Jidoka is about never letting a defect move forward. One controls flow, the other controls quality. Take either away and the house collapses.

PillarQuestion it answersMain toolsWhat it protects in OEE
Just-in-TimeHow do we keep the right thing flowing at the right rate?Takt time, pull, kanban, heijunkaPerformance, Availability
Jidoka (autonomation)How do we stop the moment something is wrong?Andon, poka-yoke, in-station quality checks, line stopQuality, Availability

If you want a refresher on how these losses are scored, our guide to Overall Equipment Effectiveness walks through the math, and the Six Big Losses framework shows exactly where jidoka events show up in your numbers.

What are the 4 steps of jidoka?

The classic jidoka cycle has four steps. Skipping any of them turns jidoka into a fancy stop button.

  1. Detect the abnormality. A sensor, vision system, gauge, or trained operator notices that the process has left its standard. The earlier the detection, the cheaper the fix.
  2. Stop. The machine, the cell, or the line stops on its own, or the operator pulls an andon. The moving target is now still, so the team can actually see what is happening.
  3. Fix or correct the immediate condition. Clear the jam, replace the broken tool, restart the cycle, so production can resume. This is first aid, not surgery.
  4. Investigate the root cause and install a countermeasure. Once the line is moving again, the team runs a structured root-cause analysis (5 Whys, fishbone, FMEA) so the same abnormality cannot return.

Jidoka vs full automation: what is the difference?

Full automation just keeps running. Jidoka stops on purpose. A fully automated line with no jidoka can produce thousands of bad parts before anyone notices. A jidoka line produces one bad part, freezes, and turns that single event into a permanent improvement.

Toyota's loom story is the perfect contrast. A normal mechanical loom in 1900 kept weaving even after a thread snapped. Toyoda's loom stopped. The total output per shift went up, not down, because the operator could now tend several machines and nobody had to sort through ruined cloth at the end.

The cost of not stopping

The dollars are loud. Independent industry research from Siemens and Senseye found Fortune Global 500 industrial firms lose roughly 11 percent of yearly turnover to unplanned downtime, and the average automotive plant loses more than $2 million per hour when a major line goes down.

Most of that pain starts as a small abnormality that nobody stopped to look at. Jidoka is the discipline that catches it on second one, not minute sixty.

How does andon support jidoka?

Andon, the Japanese word for "lamp," is the signal layer of jidoka. When a machine or operator detects an abnormality, a coloured light, board, or now a digital tile tells the supervisor and the maintenance team exactly what stopped, where, and why. Andon makes the stop visible, which is what triggers the human response.

A modern andon does three jobs at once:

  • Calls for help from the right person, not the whole shift.
  • Logs the stop with a reason code, so the data exists for later analysis.
  • Starts the clock on response time and repair time, which feeds MTBF and MTTR calculations.

How does jidoka protect OEE?

Jidoka shows up in two of the three OEE factors.

  • Quality. Because the line stops before a defect propagates, scrap and rework drop. The defects that do happen are captured at the source, not at final inspection.
  • Availability. Counterintuitively, a line that stops more often when something is wrong stops less in total, because the same fault no longer recurs. This is where jidoka attacks the hidden enemy of unplanned downtime: micro-stops. Plants that rely on manual reason-code logging typically miss a large share of short 1 to 5 minute stops because operators wave them off as normal. Sensor-driven jidoka logs every one.

Performance, the third factor, also benefits indirectly, because cycle-time slow-downs are themselves abnormalities a jidoka system can catch.

What does jidoka look like in a modern factory?

The looms changed but the principle did not. Today, jidoka shows up as:

  • Poka-yoke (mistake-proofing) fixtures that physically prevent a part from being loaded the wrong way.
  • Vision systems on the line that compare every part to a reference image and reject mismatches.
  • PLC and OPC-UA tags wired to OEE software, so the cell stops and signals the second a parameter goes out of band.
  • Digital andon on shop-floor screens and phones, replacing the old red, yellow, green light tower.
  • Closed-loop work orders that automatically open in a CMMS when an abnormality is detected, complete with the fault code, recent machine state, and the right spare parts.

Is computer vision a form of jidoka?

Yes. A camera that watches the cycle, recognises a stoppage or a quality drift, and flags it without operator input is a textbook jidoka device, the 2026 version of Toyoda's broken-thread stopper.

Fabrico uses computer vision to capture the true cause of downtime , including the micro-stops operators tend to wave off, then turns each event into a prioritized, parts-ready digital work order on the technician's phone with a QR-enforced checklist. That is the fault-to-fix loop the old andon cord was always trying to close.

Jidoka implementation checklist

Use this as a 30-minute audit of any line you are trying to bring under jidoka discipline.

  • Every machine has a defined "abnormal" condition with a specific sensor, vision check, or operator standard.
  • The line can stop itself, or an operator can stop it, without asking a supervisor.
  • An andon signal reaches the right responder in under two minutes.
  • Every stop event creates a logged record with reason code, duration, and machine.
  • Every recurring abnormality has an open countermeasure in the improvement system.
  • The data feeds your TPM pillars, especially planned maintenance and quality maintenance.

Common jidoka mistakes

Three patterns kill jidoka programs:

  1. Stopping without learning. The team clears the jam and restarts, but never asks why. The same abnormality recurs every shift. Jidoka without step 4 is just expensive interruption.
  2. Punishing the andon puller. If operators feel they will be blamed for stopping the line, they will not stop it. Jidoka collapses the moment psychological safety does.
  3. Bolting on sensors without a response loop. Detection without a routed work order produces alarms, not improvement. The handoff from "abnormality detected" to "right person fixing it" is where most digital jidoka projects break.

How jidoka connects to kaizen and TPM

Every jidoka stop is raw material for kaizen. The four-step cycle ends with a countermeasure, which is what kaizen runs on. Over time, those countermeasures harden into standardised work, poka-yoke devices, and preventive maintenance tasks, which is exactly the connective tissue between jidoka, TPM, and built-in quality.

See jidoka close the loop on your line

If you want to see what jidoka looks like when detection, andon, and the work order all live in one system, take a short tour of Fabrico. We will show how a vision-detected micro-stop becomes a routed, parts-ready work order before the operator has finished writing the shift report.

Frequently asked questions

What is jidoka in simple terms?

Jidoka is the rule that work must stop the moment something abnormal happens, so a defect is never passed down the line. It is often translated as automation with a human touch, because the machine itself, not a human babysitter, decides whether to keep running.

What are the four steps of jidoka?

The four steps are: detect the abnormality, stop the process, fix the immediate condition so production can resume, and investigate the root cause and install a countermeasure so the same problem cannot recur.

What is the difference between jidoka and automation?

Standard automation keeps running until told to stop. Jidoka stops itself the instant it detects an abnormality. That single difference is why a jidoka line produces one defective part and freezes, while a fully automated line without jidoka can produce thousands before anyone notices.

Is jidoka the same as andon?

No. Andon is the signal layer (the light, board, or digital alert) that tells people the line has stopped and why. Jidoka is the wider principle: detect, stop, fix, and prevent recurrence. Andon is one of jidoka's main tools.

How does jidoka affect OEE?

Jidoka protects two of the three OEE components. It directly improves Quality by catching defects at the source, and over time improves Availability by eliminating the root causes of repeat stoppages, including the under-reported micro-stops that quietly drain OEE.

Is computer vision considered jidoka?

Yes. A vision system that monitors a process, recognises an abnormality, and signals or stops without human input is a modern jidoka device. It is the 2026 equivalent of Sakichi Toyoda's loom that stopped on a broken thread.

Latest from our blog

Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration