Visual Management on the Shop Floor: 10 Examples That Work

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

Visual management makes the standard, current state and gap visible at a glance. See 10 shop floor examples, from shadow boards to andon, and how to use them.

Visual management makes the status of work readable where it happens, so that the standard, the current state and the gap between them can be seen at a glance. This article is for lean managers who want practical examples for the shop floor, not a theory lecture. It shows ten examples that work, the principles behind them, a rollout plan, a worked example with numbers and the mistakes that turn boards into decoration.

Key points

• Visual management makes the status of work readable at a glance, so that everyone involved can see the standard, the current state and the gap.
• Ten examples that work: shadow boards, floor marking, colour coding, kanban boards, andon, 5S, daily boards, pace boards, point-of-use standards and dashboards.
• A visual tool needs a rule and a response. An andon is defined by who answers it and how fast, not by the light.
• Many teams stop at indicators. Move up to signals and controls, which change behaviour more than a posted number does.
• Keep boards alive with a named owner, a daily routine and a regular review. A board that nobody uses is theatre.

What is visual management?

The Lean Enterprise Institute describes an andon as a visual management tool that highlights the status of operations in an area at a single glance. That sentence also describes the purpose of the whole practice. A guide on visual management tools quotes the same institute: the status of the system can be understood at a glance by everyone involved. The guide's own working definition goes one step further: the practice makes the standard, the current state and the gap between them visible, so that deviations announce themselves.

Three words matter here. Standard: what should be. Current state: what is. Gap: the difference, which tells the team where to act. A board that shows only the current state, with no standard to compare, is a number on a wall.

The benefits of visual management are transparency and speed. A visual management system helps teams share information, see the workflow and react to real-time changes. Visual aids and visual cues replace long explanations, and effective visual management lets a team work collaboratively on the same picture.

Visual management is part of the daily rhythm of shop floor management. Boards, signals and markings give the team and its leaders the same picture, without a report or a meeting to explain it.

What principles make it work?

The same guide lists three principles. They are a good test for every visual tool.

1. Make the standard visible. A number needs a reference point. Show the target next to the actual value.
2. Make the deviation obvious. The gap should be visible at a glance, without calculation.
3. Make the response obvious. Someone should know who acts, and by when.

The guide also describes four levels of control, credited to Gwendolyn Galsworth: indicator, signal, control and guarantee. An indicator shows information. A signal calls for attention. A control makes the right action easier or the wrong one harder. A guarantee prevents the error altogether. The guide notes that most teams stop at indicators, which rarely change behaviour. So when you review a board, ask what level each element is on, and whether it can move up one step.

Which 10 examples work on the shop floor?

Each of these appears in the guide's list. Use them as a menu, not as a checklist to complete.

1. Shadow boards. An outline marks the place of each tool, so a missing tool shows at once and nobody has to count.
2. Floor and lane marking. Lines show where material, traffic and people belong. Keep the colours consistent, and reserve red for danger and emergency equipment, as the guide suggests.
3. Colour coding. Colour encodes state so that it can be read without reading. It fails when there are too many colours, or when one colour means different things in different areas.
4. Kanban boards and cards. They show where work sits in the flow. A kanban is a signal, and the card or the work in progress limit is the control. A board without limits is just a to-do list.
5. Andon. A signal that calls a named responder to an abnormality. A typical andon is an overhead board with numbered rows, one per workstation, and a number lights up when a sensor, a cord or a button reports a problem. It summons a quick response from the team leader.
6. 5S markings and standards. 5S is a set of Japanese terms for workplace practices that support visual control. Labels, marked places and photos of the target state make order checkable.
7. Daily management boards. A board per area that shows safety, quality, delivery and cost, plus an action list. The team meets at it each day.
8. Production pace boards. A board that compares planned and actual output per hour, so the team sees at once whether it is on pace.
9. Standard work at the point of use. The current method, shown as a short instruction or photo at the workstation, where it is needed.
10. Digital dashboards. Screens that show the same information in real time. They are useful when data comes from several systems, and they fail if they sprawl into vanity metrics.

Some plants also use a heijunka box, a tool for distributing kanban at fixed intervals to level production. It works as a visual tool only if it truly releases the work.

How do you roll out visual management?

Start with one area and one problem.

1. Choose a problem the team feels. For example: searching for tools, unclear priorities, or stops that nobody answers.
2. Write the standard. What should be: the position of the tool, the target per hour, the response time to a call.
3. Pick one tool that fits. A shadow board for tools, a pace board for output, an andon for stops. One tool, not five.
4. Show the standard and the actual side by side. Use simple symbols, one or two colours and large numbers.
5. Define the response. Who acts when the signal appears, and in what time? Write it on the board.
6. Build it with the team. The people who use the tool know where it must stand and what it must show.
7. Place it where decisions are made. At the cell, at eye level, not in the office.
8. Review after four weeks. Remove what nobody uses, change what does not help and add one new element.

How do you keep the boards alive?

The most common failure is a good launch followed by a slow decline. The guide describes this as board theatre: boards built for visitors and never used by the team. Prevent it with three habits.

• A named owner. One person updates the board and answers questions about it. Without an owner, the board goes stale.
• A daily routine. Use the board in a short daily meeting. A board that is not used in the meeting will not be read.
• A regular review at the gemba. Gemba is the Japanese word for the real place. Leaders who walk the shop floor and ask about the boards signal that they matter.

Over time, treat each board as an object of continuous improvement. Ask what the team still cannot see, and which indicator can become a signal or a control.

Example: response time with an andon

This is an illustration with made-up numbers.

A line runs two shifts, five days a week. It has 15 stops per shift that need a team leader. Before the change, the operator walks to find the team leader, and the average time until help arrives is 6 minutes. The line stands still while it waits.

• Stops per week: 15 × 2 × 5 = 150.
• Waiting time per week: 150 × 6 = 900 minutes, or 15 hours.

The team installs an andon with a light and a call button, and agrees that the team leader reaches the line within 2 minutes.

• New waiting time per week: 150 × 2 = 300 minutes, or 5 hours.
• Saving: 900 − 300 = 600 minutes, or 10 hours per week.

At a takt of 3 minutes per unit, 600 minutes is 600 ÷ 3 = 200 units of capacity per week that the line would otherwise lose. This holds only if the line really stops during the wait and the team leader meets the 2 minutes. These are assumptions. Measure your own response times before and after.

Common mistakes

• Board theatre. A board built for visitors and never used by the team changes nothing.
• Indicators without controls. Information is posted, but behaviour stays the same.
• Red with no response. A red that means nothing is worse than no colour at all.
• Too many colours, too many metrics. If everything is highlighted, nothing is. Keep a few measures that the team can influence.
• Stale boards. A board that depends on someone with other priorities will be out of date within weeks.
• Copying the artifact without the rule. A heijunka box that does not release the work, or an andon that nobody answers, is decoration.

How software can help

Paper boards are right for a start. They fall behind when plans change during the day and when data comes from several systems. Software can show the same picture on a screen, updated in real time. iFAKT's Polaris Analyzer provides KPI dashboards across all modules that compare planned and actual values in production. Treat any dashboard as a visual management tool: it needs a standard, a visible gap and a defined response, and it must be used at the meeting.

Next step

Pick one cell and one problem, write the standard and set up one visual management tool that shows the gap. Review it with the team after four weeks and decide whether it needs a signal or a control.