01 · Turn visibility into a decision
Turn visibility into a decision
Visual management makes an operating condition understandable where the work happens. Its value comes from shortening the gap between noticing an abnormality and taking an appropriate action. A coloured sign or large screen is only a display until someone can use it to determine what should happen next. Design around four questions: what is normal here, what is happening now, how do those differ, and who responds?
Separate information from control. A map showing where packaging is stored provides information. An outlined space with a maximum of six replenishment carts exposes excess inventory. A signal that calls for replenishment when two carts remain provides a decision rule. An interlock preventing dispatch without a completed identity scan provides a stronger control. Choose the strength according to risk, not visual appeal. A fragile sticker should not carry the entire burden of protecting a high-consequence decision.
02 · Define the normal condition first
Define the normal condition first
Observe work before adding signals. Agree the required sequence, capacity, quality condition and authorised exceptions. If the team has not decided how many parcels may wait at a release station, a painted box cannot establish that limit by itself. Determine capacity from the space, safe access, handling requirements and flow design, then represent it visibly. Avoid arbitrary limits selected to make the workplace look tidy.
Locate the cue where the decision occurs. Put the carrier-service confirmation beside the scan result, the hold status on the parcel container, and the queue limit at the lane entrance. A dashboard in a distant office may report congestion later but cannot directly help the person about to add another cart. Check visibility from the normal working position, at realistic lighting and viewing distance.
Use labels, shapes or position in addition to colour. People should distinguish “ready”, “hold” and “awaiting supervisor” without relying exclusively on red and green. Include units and a timestamp on changing information. A stale value presented as current is an operational hazard even if its typography is excellent.
03 · Worked example: a visible dispatch lane
Worked example: a visible dispatch lane
At fictional Northbank, released and held parcels share a bench. A packer assumes any parcel on that bench is ready for the next vehicle. The improvement creates two clearly labelled positions: “release verified” and “hold: do not load”. Each hold container carries the parcel identifier, reason and responsible role. The verified lane has six marked cart positions and an upstream signal when four are occupied.
At 15:20, five positions are occupied and a sixth cart approaches. The signal does not mean everyone must work faster. The dispatch lead checks whether loading is available, discovers that the vehicle arrival is delayed, and temporarily stops feeding the lane. Upstream work moves to another authorised carrier route where demand exists. The team records the delay and protects access around the release bench.
A held parcel has a damaged barcode. Its visible status prevents accidental loading while the supervisor resolves identity. Once the required checks pass, the supervisor updates the electronic record and transfers it to the verified lane. Moving the parcel changes its physical status, but the move is not a substitute for the authorised release record. The physical and digital signals must agree.
04 · Give every signal a response
Give every signal a response
For each abnormality, define immediate protection, ownership and escalation. If the queue exceeds its limit, who checks downstream readiness? If a scan fails, who can resolve it? If nobody responds within the agreed interval, what happens? A signal that has been raised repeatedly without action teaches people to ignore it. The review should therefore assess response completion as well as the number of alerts.
Northbank distinguishes a temporary condition from a persistent problem. A single vehicle delay prompts containment and recovery. Three similar delays in a week prompt a separate investigation involving transport planning. The operator is not expected to diagnose the complete logistics system while protecting the lane. Immediate response and systemic improvement have different time horizons, and both need ownership.
Avoid rewarding the disappearance of alerts. A low alert count can mean excellent performance, but it can also mean broken sensors, suppressed reporting or fear of escalation. Ask whether the signal accurately reflects reality and whether a useful response followed. Visible problems are information for improvement, not evidence that the person who revealed them performed poorly.
05 · Test understanding and maintain the system
Test understanding and maintain the system
Test the visual with an experienced operator, a new starter and someone from the following shift. Ask each person to interpret a normal condition, an abnormal condition and a missing-information condition. Observe the action they take. If their interpretations differ, simplify the signal or clarify the standard. A designer’s explanation after the test does not establish that the unaided visual works.
Assign ownership for updating changing information and replacing damaged cues. Northbank’s shift handover includes a short walk of the release lane: do physical quantities match the lane board, are hold labels current, and can all floor markings be seen? The team removes an old “urgent carrier” sign because it conflicts with the new authorised release sequence. An outdated cue can be more dangerous than no cue because it appears to grant permission.
Review the system when layout, products or software changes. A six-cart limit is not automatically appropriate for a new cart size. A projected screen may be readable in winter darkness but fail in summer glare. Maintenance should preserve meaning, legibility and actionability rather than merely replace materials.
06 · Avoid visual clutter and unintended behaviour
Avoid visual clutter and unintended behaviour
Common failures include displaying everything, using colour without explanation, posting targets without current status and locating cues away from the decision. Too many competing messages create search work. Prioritise safety, quality and flow decisions, then remove items that do not support an observable action. A visual management system can be simple without being simplistic.
Consider behavioural effects. A board ranking individual dispatch speed may encourage workers to bypass verification or send difficult parcels elsewhere. Northbank instead displays lane flow, quality exceptions and shared support needs. Individual coaching happens respectfully with context. The visual system helps the team manage the process rather than publicly attribute every variation to a person.
Advanced digital signals need the same discipline as physical ones. Document data latency, missing inputs and system failure behaviour. If a screen goes offline, provide a clear fallback status; do not leave its last green value looking live. Connect alerts to a response route with adequate capacity. A rapid signal is useful only if the receiving team can understand and act on it.
07 · Choosing signal strength
Choosing signal strength
Consider how quickly a wrong action can become irreversible. For a low-risk replenishment decision, a clearly labelled minimum level and routine response may be enough. For a parcel identity decision, combine visible status with an electronic permission check because a person can move a parcel into the wrong lane. Test how the signal behaves under realistic distraction, queue pressure and equipment failure. Northbank deliberately places its hold sign on the container and blocks electronic release, so the physical cue and the system rule support the same decision. Redundant protection should be purposeful; duplicating several weak signs does not necessarily create a strong control.
Connections
Related methods and phase use
Placed under Control because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
- Lean Enterprise Institute: Visual Management
- Lean Enterprise Institute: Visual Management and Lean Behavior
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.