Visual Management in Lean: Andon, Problem Boards and Huddles

Lean visual management for small teams: make normal obvious, signal problems with andon, use problem-solving boards and run short huddles.

Gidoka · Last reviewed October 24, 2026 · 6 min read

In lean thinking, a good visual display doesn't just report status. It answers one question fast: is everything normal right now, and if not, who is responding? A wall of charts can be informative and still fail that test. A single red light that brings a team leader running passes it.

That idea comes straight from the Toyota Production System, where making abnormalities visible is tied to stopping, fixing and preventing problems. This guide covers the lean side of visual management: the signals that separate normal from abnormal, the andon and the problem-solving board, quick audit boards for leaders, and the short huddles that turn what's visible into action.

If your team already tracks work on a task board, think of this as the layer underneath: signals for problems, and a routine for responding to them.

What Visual Management Means in Lean

The Lean Enterprise Institute (LEI) defines visual management as placing all tools, parts, production activities and indicators of system performance in plain view, so the status of the system can be understood at a glance by everyone involved. LEI cross-references it with two Toyota ideas, andon and jidoka.

Jidoka is one of the two pillars of the Toyota Production System. Toyota's own description explains it as "automation with a human touch": when an abnormality occurs, such as an equipment problem, a quality problem or a work delay, the machine stops itself or the operator stops the line by pulling a stop cord. When equipment stops, Toyota says, the andon, a problem display board, lights up to notify workers, so people need only respond when there is an abnormality instead of watching over equipment.

The lesson for any team: visual management is about seeing problems early, so they get solved at the source instead of passed along.

Make Normal Obvious First

You can't spot an abnormality unless normal is defined and visible. A guide on mistake-proofing published by the Agency for Healthcare Research and Quality (AHRQ) treats 5S as a way of building "visual systems," which share information in the work environment so people can "know by looking."

Hypothetical examples for a small workplace:

An outlined spot on a shelf for each tool, so a gap means something is missing.
A line marked on a supply bin at the reorder point.
A tray for incoming paperwork with a card showing the expected same-day volume.
A posted, one-page standard next to the task, so anyone can see how it should be done.

Each answers "is this normal?" without a question being asked.

The Andon: A Signal That Calls for Help

LEI describes andon, Japanese for "lamp," as a visual tool that shows the status of operations at a glance and signals whenever an abnormality occurs. A typical andon is an overhead board with numbers for each workstation; a number lights when a sensor detects a problem or an operator pulls a cord or pushes a button, and it summons a quick response from the team leader. Colored lights on machines, red for problems and green for normal, are another form.

LEI also explains Toyota's fixed-position stop: when an operator pulls the cord, the line keeps moving until the product reaches the end of the workstation, so the team gets a chance to fix the problem first. If it isn't solved in time, the line stops there, at a point where the stop doesn't disrupt the other workstations' work.

The light is the easy part. The response is what matters. LEI lists response to andons as one of the five major tools of day-to-day leader standard work.

For a small team, an andon can be as simple as a colored card on a desk or a flag in a team chat. The rule that makes it work is that someone responds promptly and helpfully, and nobody is made to feel foolish for raising it.

The Problem-Solving Board

LEI describes a production analysis board as a display, often a large whiteboard beside a process, showing actual performance against plan, typically hour by hour. When output doesn't match the plan, the problem is recorded and a cause is sought.

LEI stresses that the board is a problem-identification and problem-solving tool, not a scheduling tool, and notes it is sometimes more appropriately called a problem-solving board.

A hypothetical version for a small order-packing team:

Columns for each hour, with planned orders packed and actual orders packed.
A comments column where anyone writes what got in the way, such as "label printer jammed" or "item out of stock."
At day's end, the team scans the comments for repeats and picks one to fix.

The comments column is the most valuable part. It turns a scoreboard into a list of problems to solve.

Audit Boards for Leaders

LEI describes the kamishibai board as a visual control for audits that makes normal versus abnormal conditions clear. It gives leaders a schedule for when to visit a process and what to check, building "go and see" into their routine. LEI explains that a circle means the right quality, quantity and standardized work were found, a triangle means an abnormality was observed and corrected, an X means corrective action is needed, and an empty box means team support didn't occur.

For a small business, this might be a few cards, each with one thing to check, such as whether the morning checklist was used or whether the safety exit is clear. The owner pulls one card each day and checks it in person.

Huddles That Act on What's Visible

LEI describes huddles as brief meetings, usually done standing up, held at tracking boards. They identify where expected results aren't being achieved and who needs to investigate causes and try countermeasures. In healthcare, LEI notes, huddles are quick meetings of a team working on a shift or a common project, and typically last less than 30 minutes.

A lean-style huddle is short and points at the boards:

What was abnormal since the last huddle?
What did we do about it, and did it hold?
What needs help today, and who owns it?

Keep it to the problems the displays have surfaced, rather than a round of individual updates.

Pitfalls

Signals nobody responds to; people stop raising them.
Boards used to blame individuals, so problems get hidden.
Displays that track everything, so nothing stands out.
Using a problem-solving board as a production schedule, which LEI specifically warns against.
Leaders who never visit the boards in person.

Key takeaways

In lean, visual management exists to make abnormal conditions obvious so people respond quickly.
Define and display "normal" first; 5S and posted standards make problems visible.
An andon is a signal for help; the value is in the prompt response, not the light.
Problem-solving boards compare plan with actual and record what got in the way.
Kamishibai audits and short standing huddles keep leaders and teams acting on what the displays show.

Sources

Spotted something out of date? Let us know.