Jidouka: Stop for Problems—Not Because Stopping Has Become Normal

In the Toyota Production System (TPS), Jidouka is often described as “automation with a human wisdom.” One of its most important principles is the authority—and responsibility—to stop a process when a problem occurs.

The purpose of stopping is not simply to halt production. It is to prevent defects from moving forward, make abnormalities visible, call for help, and correct the underlying problem.

The key phrase is: when there is a problem.

We stop when an abnormal condition threatens safety, quality, delivery, or the stability of the process. Conversely, when there is no problem, the process should continue.

Yet in many workplaces, stopping gradually becomes normal.

We stop because we need to go and get parts.

We stop because a machine is claimed to be in changeover.

We stop because someone leaves early.

We stop because an event is taking place.

Sometimes, we stop simply because we have become accustomed to stopping.

This raises an uncomfortable but necessary question:

Have we become too comfortable with stopping?

The Real Problem Is Not Always the Stop

Some stoppages are unavoidable. Machines fail. Suppliers experience disruptions. People face emergencies. Safety and quality must never be sacrificed merely to keep production moving.

The deeper concern is how the organization responds.

Where is the sense of urgency to contain the problem, restore the process, and prevent recurrence? Why do we continue stopping for the same reasons? Why are familiar disruptions accepted as part of the routine instead of treated as abnormalities demanding action?

When the same problem repeatedly stops a process, it is no longer an isolated incident. It is evidence that the organization has learned to accommodate the problem rather than eliminate it.

A repeated stop should trigger deeper questions:

What caused the abnormal condition?

Why was the problem not anticipated or detected earlier?

What is required to restart safely and quickly?

What temporary countermeasure can restore the process?

What permanent countermeasure will prevent recurrence?

Who owns the follow-up, and when will it be completed?

Without these questions, stopping becomes passive. With them, it becomes a mechanism for learning and improvement.

Psychological Safety Does Not Mean Operational Comfort

People should feel completely comfortable calling for help when they see a problem. They should never fear punishment for stopping a process to protect safety or quality.

But people should not become comfortable with the stopped condition itself.

These are two different ideas.

A healthy organization creates psychological safety around raising problems while maintaining operational urgency around solving them. Team members should be able to pull the andon without hesitation—and the organization should respond immediately.

The message should be clear:

“Thank you for identifying the problem. Now let’s work together to restore the process and ensure it does not happen again.”

If employees are afraid to stop, problems remain hidden. If the organization is comfortable remaining stopped, problems remain unsolved.

Neither condition reflects true Jidouka.

Treat Every Stop as a Signal

Consider what happens when a person’s heart stops. The situation demands an immediate response because every minute matters. People do not casually observe the condition, schedule a discussion for later, or accept it as normal. They react, call for help, begin recovery efforts, and focus on restoring function.

A stopped production process is not a medical emergency, but the analogy highlights an important leadership principle: the longer an abnormal condition continues without action, the more serious its consequences can become.

A short interruption can quickly grow into missed production, delayed deliveries, overtime, increased costs, employee frustration, and customer dissatisfaction.

So why do we sometimes allow a process to remain stopped for ten minutes before anyone responds?

Perhaps we have stopped viewing downtime as an abnormality. Perhaps repeated disruptions have lowered our expectations. Perhaps the organization measures downtime but does not create clear ownership for restoring the process and preventing recurrence.

Whatever the reason, a weak response to stoppages eventually becomes part of the culture.

Build a Culture of Rapid Response

A strong Jidouka culture requires more than permission to stop. It requires a disciplined response system.

When a process stops:

1️⃣ Respond immediately.

Make the problem visible and ensure that the right support reaches the area quickly.

2️⃣ Protect people and customers.

Confirm safety, contain potential defects, and prevent the problem from moving downstream.

3️⃣ Restore the process.

Apply a safe temporary countermeasure when appropriate so operations can resume.

4️⃣ Identify the true cause.

Do not confuse restarting the process with solving the problem.

5️⃣ Prevent recurrence.

Assign ownership, establish a deadline, and verify that the countermeasure works.

6️⃣ Learn from the event.

Share the lesson so similar processes can avoid the same failure.

The goal is not to criticize people for stopping. The goal is to prevent the organization from accepting recurring stoppages as normal.

Stop With Purpose

Jidouka does not celebrate stopping for its own sake. It uses stopping as a deliberate response to abnormality.

We stop to protect safety.

We stop to protect quality.

We stop to expose problems.

We stop so that we can learn, improve, and restart with confidence.

But we should never allow stopping to become the default condition.

Leaders must create an environment where employees are comfortable identifying problems but uncomfortable ignoring them. Teams should feel safe asking for help while maintaining a strong sense of urgency to restore the process. Every repeated stoppage should strengthen the organization’s determination to eliminate its cause.

The question is not simply, “Why did we stop?”

We must also ask:

“How quickly did we respond, what did we learn, and what are we doing to ensure that we do not stop for the same reason again?”

That is the discipline behind Jidouka—and the difference between merely stopping production and building a true culture of Kaizen.