Visual management: making the state of work obvious without asking anyone

A display nobody acts on is decoration

Most plants already have boards. Very few have boards that change behaviour within the shift. The test is simple to apply and uncomfortable to fail: stand in front of the display and ask the nearest operator what it currently says and what they would do if it said something worse. If the answer is that the figures get typed up for a meeting, the board is reporting, not controlling. Reporting has its place and that place is an office. A visual control earns its wall space by triggering an action from someone within arm's reach of the process, while the shift can still recover.

You cannot show abnormal until you have defined normal

Every genuine visual control rests on a stated expectation: this quantity by this point in the shift, this tool in this shadowed position, this pressure inside this marked band, this rack empty by handover. Where no expectation exists, a display can only show what happened, which leaves interpretation to whoever is looking and produces argument rather than action. Visual management is therefore downstream of standard work and of an agreed plan for the day. Plants that skip that step end up with attractive graphics everyone reads differently, and with supervisors who quietly keep the real status in their heads.

Someone has to write on it, at a set time, by hand

Updating is the cost people underestimate. A board maintained by the improvement team decays the moment that team is busy elsewhere; a board written up by the team leader at fixed points in the shift survives, because the act of writing is itself the moment of noticing. Handwriting has an advantage that surprises managers: it forces a person to confront the gap rather than watch a system calculate it. The corresponding obligation is that writing must be quick. If filling in the display eats the supervisor's floor time, it will be done retrospectively from memory, and once it is fiction everybody knows.

The pull towards screens and away from the point of use

Screens are easier to justify and easier to ignore. They tend to migrate to walls where managers walk rather than where decisions are made, they show what the reporting system already holds, and they displace the small physical devices that do the real work: floor markings that make a missing pallet obvious, shadow boards, colour-coded material rails, a marked band on a gauge, a bin that is either full or not. The useful question about any proposed screen is which decision it changes and who makes that decision. If the answer names somebody in an office, it is a report.

Judge it by response time, not by tidiness

The measure of visual management is how quickly a deviation becomes visible and how quickly someone reacts to it. Walk an area cold, time nothing formally, and simply note whether you could identify the current problem yourself, then ask whether the person responsible already knew. A floor that looks organised while its problems are still discovered in the following morning's meeting has bought the appearance without the mechanism. Conversely, a scruffy area where a missing part is obvious within minutes of going missing is doing the job. Appearance and control correlate loosely, and confusing them is the standard mistake.

Frequently asked questions

Should we replace our whiteboards with digital displays?

Only where the digital version keeps the same audience and the same response. Screens are good at aggregating across shifts and at showing things nobody can count by hand, such as equipment state. They are poor at forcing a supervisor to confront a gap, and they drift towards management reporting. A common arrangement keeps the hand-written control at the process for hourly status, and uses screens for equipment condition and the plant-level picture, with every display owned by a named person.

How do we know we have too many boards?

Look at which ones were updated during the current shift, then ask who last changed a decision because of one. Displays multiply because each new initiative wants a wall and nobody is willing to take another team's board down. The working rule is that every display needs an owner, an update rhythm and a stated action for when it shows a problem. Anything failing all three should be removed, and removing it is usually noticed by nobody, which proves the point.

Who should own the information on the board?

The person expected to act on it, which almost always means the team leader or supervisor for that area rather than the improvement function. Ownership means they set the format, they write on it, and they answer for what it shows. When the improvement team owns the design, the board reflects what that team wants to see; when the area owns it, the board tends to get simpler, uglier and considerably more useful, because unnecessary content is a chore its owner will drop.