Andon Communication Board: Real-Time Metrics for Efficient Workflow Adjustments

Andon communication board showing real-time production metrics at Toyota BT Raymond, including unit counts, overtime adjustment, and Takt time calculations for aligning production flow with customer demand.
The Andon communication board shows Lean TPS in action. By making production data visible, teams at Toyota BT Raymond align workflow with Takt time, respond to problems instantly, and maintain stability. Real-time visibility turns data into action, reinforcing teamwork, learning, and continuous improvement on the shop floor.

The Andon communication system is one of the clearest examples of how Lean TPS connects people, process, and performance. It is not a display board for data. It is a living control system that links production activity to real-time decision making, ensuring that flow, quality, and teamwork remain visible and aligned with the daily plan.

At Toyota BT Raymond, the Andon board is the pulse of production. Every number, color, and signal represents the current condition of the line. It shows how many units have been completed, how many remain, and how much time is available to achieve the target. This visibility transforms management from supervision to support. Problems are no longer hidden within reports; they are seen, discussed, and acted upon immediately.

In this example, the Andon communication board displays a clear summary of performance. As of 3:17 p.m., 118 units have been completed out of the daily target of 192. The Andon system announced two hours of overtime at 2:00 p.m. to help meet the target. With 74 units remaining, the team is 15 units behind schedule. Available time equals 450 minutes, setting the Takt at 2.34 minutes per unit. With the extended 570 minutes including overtime, the actual Takt Time adjusts to 2.97 minutes per unit. This simple calculation aligns the team with the new daily rhythm.

The purpose of Andon communication is to make abnormality visible. It tells the truth about the situation in real time so the team can respond. When production is behind, the cause is investigated immediately. Leaders ask what is preventing flow and what countermeasure is needed. When production is ahead, the discussion shifts to stability and improvement.

Andon also strengthens respect for people. Instead of waiting for instructions, operators and team leaders take ownership of their area. They can call attention to problems as they occur. This open communication prevents blame and promotes teamwork. Each signal, whether a light, number, or sound, represents a request for help.

The daily routine of reviewing Andon performance builds discipline. It reinforces how Lean TPS operates as a system of learning. Every fluctuation in pace or quality becomes a learning opportunity for the team. The board is not there to monitor individuals; it is there to reveal the system’s behavior and support improvement.

By connecting data, people, and action, Andon communication keeps production aligned with customer demand while maintaining quality. It teaches that information must flow just as smoothly as material. When used correctly, Andon turns management into a real-time coaching system where problems are visible, countermeasures are tested, and performance becomes predictable.

This approach represents the essence of Lean TPS: stability through visibility, leadership through support, and improvement through participation.

A Lean TPS system requires that execution is governed by three questions that define control. The required condition for execution must be explicitly defined through method, sequence, timing, and outcome. The point at which the condition is violated must be immediately recognizable during execution. The response required when the condition is not met must be enforced without delay. When these three elements operate together, execution is controlled and Quality is maintained as a condition of the system. Control precedes improvement because improvement depends on a stable and defined state of execution. When conditions are not defined, exposed, and enforced, improvement activity operates on an unstable system and results do not hold. Work continues under abnormal conditions, variation accumulates, and outcomes remain inconsistent. When control is established, improvement operates within defined boundaries and reinforces the condition that governs execution. Quality exists only when the required condition is maintained during each cycle of work. Quality is not achieved through measurement or inspection after execution. Quality is protected through enforcement of conditions during execution. When the condition is not met, work does not continue, and response restores the defined state before execution resumes. This enforcement prevents deviation from propagating and maintains stability at the source. A Lean TPS system requires that continuation under abnormal conditions is not permitted. When work continues despite violation of method, sequence, timing, or outcome, control does not exist and the system becomes dependent on judgment. Deviation is absorbed into normal work, and Quality is degraded. When continuation is prevented, the system enforces the boundary between normal and abnormal states and maintains control of execution. The system extends beyond individual elements and requires integration across condition definition, exposure, response, and learning. When these elements are aligned, execution is governed, leadership responds as required, and learning is embedded through repeated cycles of confirmation and correction. This integration establishes a system that maintains control and protects Quality as a condition of execution. Further development of this system requires expansion into condition design, response structure, and leadership integration at scale. The next stage addresses how conditions are constructed, how response is embedded across functions, and how governance is sustained across the organization.
Lean TPS governance image showing how conditions, deviation detection, and enforced response control execution.
Industrial Engineering and Toyota Production System comparison showing governance, stop authority, and no continuation under abnormal conditions in Mixed-Model Human–Humanoid environments
Industrial Engineering develops system capability through analysis and optimization. The Toyota Production System governs execution in Mixed-Model Human–Humanoid environments by enforcing stop authority and preventing continuation under abnormal conditions.
Governance as the missing link in continuous improvement systems showing standard operating procedures, visual control, Andon stop, Jidoka, and required leadership response to protect Quality
Continuous improvement systems fail when governance is absent. Standard operating procedures, visual control, Andon, and Jidoka must function together to stop execution, require leadership response, and protect Quality at the source
Toyota Production System Quality progression showing governing conditions, abnormality detection, and enforced response across operations
Quality in the Toyota Production System governs execution. Work continues only when conditions are met, abnormality is visible, and response is required.
Diagram illustrating Jishuken as deliberate buffer reduction within Lean TPS governance, showing how reduced manpower, inventory, and cycle time expose management behavior and test Quality protection under disciplined control.
Improvement without governance amplifies variation. Jishuken deliberately reduces buffer to expose whether leadership discipline can protect Quality under tighter operating conditions. Stability under compression confirms governance maturity.
Lean TPS Swiss Cheese Model showing four aligned cheese slices representing Organizational Systems, Leadership Governance, Task Conditions, and Point of Execution, with layered penetration paths demonstrating Quality containment.
A visual representation of the Lean TPS Swiss Cheese Model™, demonstrating how layered governance architecture progressively protects Quality from Organizational Systems through to Point of Execution.