What Is Abnormality?

Lean TPS Basic Thinking on abnormality, Standardized Work, and Stop Call Wait response

Abnormality is the starting point of Lean TPS. It defines where control begins and where leadership must act. Without abnormality, there is no trigger for response or mechanism to protect Quality.

In most environments, abnormality is treated as an interruption and absorbed through workarounds. Output may continue, but execution is separated from the conditions required to produce Quality, and instability is managed after the fact.

In Lean TPS, abnormality is a signal that execution has moved outside the defined condition required to produce Quality. This condition must be restored before work continues.

Lean TPS prevents continuation under abnormal conditions by requiring immediate response at the point of work.

“Not normal equals abnormality” is a governing rule. Execution either matches Standardized Work or it does not. There is no acceptable deviation.

Without a defined normal condition, abnormality cannot be detected and Quality cannot be controlled. Inspection and rework compensate for this absence of control.

Lean TPS defines normal through Standardized Work, makes deviation visible, and enforces response through Jidoka and Stop Call Wait. Abnormality is exposed, contained, and addressed as it occurs.

Standardized Work, Jidoka, and Stop Call Wait connect execution, control, and continuous improvement into a single system.

Defining Abnormality

An abnormality is any deviation from a defined standard. This establishes the condition required to control execution and protect Quality at the point of work.

Most organizations operate with incomplete standards. Work is described but not defined by sequence, timing, and outcome. Variation is tolerated if output appears acceptable, making abnormality subjective and delaying response.

Lean TPS removes this subjectivity by defining execution. The method, sequence, and timing aligned to takt are fixed. Any deviation is an abnormality.

This creates a binary condition. The defined state is either met or not met. There is no acceptable deviation, enabling immediate detection and response.

Abnormality appears in many forms, including sequence errors, timing deviation, missing tools, incorrect material condition, defects, and incomplete information. Each represents deviation from the defined standard required to produce Quality.

Abnormality is defined by deviation from the method, not outcome alone. Acceptable results produced outside the method are hidden variation.

Lean TPS shifts focus from inspection of results to control of execution. Quality is governed at the point of work.

Standardized Work as the Condition for Normal

Standardized Work defines what normal is. It establishes the condition required for work to produce Quality consistently.

It defines three elements: sequence, timing relative to takt, and expected outcome. These are conditions that must be met.

When followed, execution is stable because variation is removed at the source. When not followed, abnormality is introduced immediately, regardless of output.

Standardized Work is not documentation. It is the operating condition of the system, governing execution in real time and enabling immediate detection of deviation.

When Standardized Work is not defined, hidden abnormality occurs where deviation does not trigger response.

Lean TPS eliminates this condition by defining work precisely.

Visibility of Abnormality

Abnormality must be visible at the point of occurrence.

Lean TPS establishes visibility as a control requirement. Abnormality is seen immediately by both the operator and the leader. This is achieved through visual control embedded in the work environment.

Visual control defines the expected condition and makes deviation obvious. Work areas are defined, tools and materials have fixed locations, and visual indicators distinguish correct from incorrect conditions. Real time signals expose abnormality immediately.

The purpose is control of execution. The condition of the work is evident without explanation, allowing immediate recognition and response.

Jidoka and the Requirement to Stop

Jidoka prevents continuation when the defined condition is not met. It enforces standards in real time and prevents deviation from being absorbed by the system.

Stopping contains the abnormality at the point of occurrence and creates immediate focus for response. Containment protects the product. Focus protects the process.

This establishes control during execution by preventing abnormal conditions from propagating through the system.

Most systems avoid stopping and instead manage abnormality through rework or inspection after the fact, separating execution from control.

In Lean TPS, execution resumes only when the defined condition is restored.

Stop Call Wait as a Structured Response

Stop Call Wait defines how the system responds to abnormality. It is a required sequence that ensures deviation is contained, understood, and corrected before work continues.

Stop: Execution is halted immediately to contain the condition. Call: Support is engaged to respond. Responsibility is shared and brings the required capability to the point of abnormality. Wait: Work does not resume until the condition is understood and a countermeasure is applied, preventing temporary fixes.

Stop Call Wait also drives learning. Each abnormality becomes a defined event that develops capability and improves the system.

Abnormality and Muda

Every abnormality is connected to waste. In Lean TPS, waste is any activity that does not contribute to producing Quality under defined conditions, making it visible through deviation from the standard.

Abnormality exposes these conditions at the point of work. The form of deviation indicates the type of waste present, such as imbalance, poor layout, or failure to maintain process conditions.

Restoring the condition addresses the immediate impact but does not prevent recurrence.

The purpose is to understand why the condition failed. Abnormality becomes the entry point for analysis by revealing the factors that allowed waste to occur.

Root Cause Through 5 Whys

The 5 Whys method traces abnormality to its source. It is a structured approach to understanding cause and effect and identifying the condition that allowed the abnormality to occur.

Each question moves the investigation deeper, from what happened to why it happened and the conditions that made it possible. The first identified cause is rarely the true source.

The objective is not to assign blame but to identify the system condition that failed to prevent the abnormality.

The progression moves from observed deviation to system design, examining why the method was not followed, why the standard was unclear, and why the process did not prevent the deviation.

This shifts focus to the system. If abnormality occurs, the system allowed it.

Lean TPS treats abnormality as a system condition. The 5 Whys method links deviation to the structure that produced it and defines where improvement is required.

Sustained improvement depends on identifying root causes at the system level so countermeasures prevent recurrence.

Kaizen as the Response to Abnormality

Kaizen is the structured response to abnormality. It continues the response initiated by Stop Call Wait by converting learning into defined improvement.

Once the cause is understood, a countermeasure is developed to eliminate the condition that allowed the abnormality and prevent recurrence.

Kaizen may involve changes to sequence, timing aligned to takt, tools, or visual controls. In some cases, the standard is redefined based on a proven method.

The objective is to eliminate the condition that created the abnormality, increasing process stability and the ability to produce Quality consistently.

Kaizen results in a new standard. Without updating the standard, improvement is not sustained.

Standardization and Kaizen operate as a closed loop: the standard defines the condition, abnormality exposes deviation, analysis identifies cause, and Kaizen establishes a method that removes it.

This cycle is continuous, strengthening the process and building the capability to respond to abnormality.

Leadership Responsibility in Abnormality

Abnormality defines the role of leadership in Lean TPS. Leadership operates at the point of execution, where abnormality occurs and where Quality must be protected.

In many systems, leadership reviews results after performance. This separates leadership from the conditions that created those results and delays response.

When deviation occurs, leaders respond immediately to contain the condition, restore the defined state, and ensure the cause is understood.

Leaders ensure Standardized Work is defined and maintained, and that abnormality is visible at the point of work. They respond without delay, support root cause analysis, and ensure countermeasures are implemented and sustained.

Leadership is embedded within execution. Abnormality creates a required response and removes discretion.

If abnormality occurs and no response follows, the system is not functioning as designed. Control is created through consistent, immediate response.

Quality as a Governed Condition

Quality in Lean TPS is not an outcome measured after production. It is a condition maintained during execution.

Abnormality enables this control. When deviation is detected and addressed immediately, the process is prevented from operating outside the conditions required to produce Quality.

When Quality is governed at the point of execution, reliance on inspection, rework, sorting, and post process correction is reduced because variation is contained at the source.

These activities do not create Quality. They exist when execution continues under abnormal conditions. Lean TPS removes the need for compensation by governing execution directly.

This requires discipline. Work stops when abnormality occurs and resumes only when the condition is restored. Leadership responds immediately and consistently.

Without these conditions, Quality becomes reactive. Lean TPS maintains Quality in real time through defined standards, visible abnormality, enforced response, and disciplined execution.

Stability and Learning

Abnormality serves two functions in Lean TPS: it protects stability and drives learning.

Stability is maintained by stopping and restoring the defined condition, containing variation and preventing it from spreading.

Learning occurs through analysis and Kaizen, where causes are identified and countermeasures eliminate the condition.

These functions are inseparable. Ignoring abnormality loses stability and prevents learning. Restoring flow without understanding allows recurrence.

Lean TPS requires both. Each abnormality restores the process and strengthens it, reducing variation and improving capability over time.

The System Perspective

Abnormality must be understood at the system level. Events at the point of work are symptoms of conditions created by system design and governance. Treating abnormality as a single event limits response to containment. Treating it as a system condition enables prevention.

Recurring abnormality indicates the system cannot maintain the required condition. The issue is not repetition but the absence of conditions that prevent it.

These conditions are structural, including mismatched demand and capacity, inadequate Standardized Work, insufficient visual control, inconsistent leadership response, and incomplete training. When these gaps exist, abnormality is expected.

Addressing abnormality at the system level removes these conditions and prevents recurrence. The objective is not repeated response but a system where abnormality cannot occur under normal conditions.

Lean TPS links abnormality to system design. Each occurrence tests whether execution is maintained within defined limits and drives changes to restore and sustain the condition.

The Most Important Principle

The most important principle in Lean TPS is Standardized Work. It defines the operating condition of the system. Without it, execution cannot be controlled and Quality cannot be protected.

Standardized Work defines method, sequence, timing, and expected outcome, establishing the baseline for all execution.

Without it, abnormality cannot be defined, detection cannot occur, and Quality cannot be controlled. Improvement cannot be sustained.

Standardization provides the foundation for Lean TPS by defining conditions, enabling detection, supporting response, and creating a baseline for learning.

All other elements depend on it. Jidoka, visual control, Stop Call Wait, and Kaizen require a defined condition to function.

With Standardized Work, these elements operate as a system to create control, protect Quality, and sustain continuous improvement.

Conclusion

Abnormality is not a disruption. It is the signal that the system is functioning as designed. It exposes deviation, triggers response, and enables learning.

Lean TPS ensures abnormality is visible and addressed immediately, not managed after performance is affected.

Standardized Work defines the condition for Quality. Jidoka enforces stopping. Stop Call Wait defines response. Kaizen converts each occurrence into improvement.

Most systems manage results after they occur. Lean TPS controls the conditions that produce those results in real time.

Abnormality connects execution, response, and learning into a system that protects Quality and strengthens performance.

Read the full article here: https://leantps.ca/what-is-abnormality-in-lean-tps/