Visual Management: Make Problems Visible at a Glance
Normal vs. abnormal, instantly
The purpose of visual management is one sentence: anyone walking past should be able to tell, within seconds, whether things are normal or abnormal. Not after reading a report. Not after asking a supervisor. At a glance. A green zone with one unit in it is normal. A red zone overflowing is abnormal. A board with every box checked is normal. A board with today's box empty at noon is abnormal. Plants without visual management hide their problems in spreadsheets and shift reports, where they ripen quietly. Plants with it hang their problems on the wall, where they get fixed today.
Boards that get read, and boards that don't
A board gets read when it answers the three questions the team actually asks: where are we against the plan, what is blocking us, and who owns the fix? A board gets ignored when it answers questions nobody asks — corporate metrics, last month's results, a wall of charts updated by someone who left. The rule is brutal and useful: if a board has not changed since last week, it is wallpaper, and wallpaper should come down. The best boards are hand-updated by the team, every shift, because the act of updating is itself the check. A board updated by hand is a conversation. A board updated by software is a screensaver.
Andon and signals: stop and fix
Andon is visual management with a voice: a light, a cord, a signal that says "this station needs help, right now." The principle behind it is the one most plants resist: stop the line to fix the problem instead of passing it downstream. Passing a defect forward feels productive — the line keeps moving — but it multiplies the cost of the defect at every step it survives. Stopping feels expensive for thirty seconds and is cheap for the shift. Andon only works if the response is real: a light nobody answers teaches the floor to stop pulling the cord, and then you have the worst of both worlds — a system that looks responsive and a floor that knows it is not.
Color, floor marking, and visual standards
Color is a language, and it must be consistent or it is noise. One color for walkways, one for work in process, one for scrap, one for danger — the same on every line, in every building, so a transferred operator reads the floor on day one. Floor marking works the same way: a marked square says "this much, here, no more," and an empty square says "something is missing" louder than any email. Visual standards turn the whole plant into a document anyone can read, which is exactly what leaders check on their daily walks — see Leader Standard Work — and what The Lean Culture Blueprint builds into the operating system. Keep the visual check in your pocket: https://apps.apple.com/us/app/lean-culture-advisory/id6790203662