Lean teams use visual management because problems that can be seen get solved faster. When the normal state is obvious, an abnormal one stands out without a report or a meeting.
Where it comes from
Visual controls are part of the Toyota Production System, where andon lights, kanban cards and marked locations let people see the state of production without asking.
At a glance
From seeing to preventing
Swipe sideways to see the whole diagram.
How to apply Visual management
- 1
Decide what people need to know
List the questions a team member or leader asks during a shift: are we on plan, where does this go, is the machine running, what is the next job.
- 2
Make the standard visible
Show the normal state with floor markings, shadow boards, labels, min and max lines and posted standard work.
- 3
Make the status visible
Show actual against plan with hour-by-hour boards, andon lights and kanban boards, updated at the point of work.
- 4
Make problems visible
Use red markers, a problem board or an andon call so an abnormal condition stands out immediately.
- 5
Link visuals to action
Agree who responds to each signal and how fast. A board that nobody acts on soon gets ignored.
Worked example (illustrative)
A machining cell posts an hour-by-hour board with a target of 24 parts an hour and a column for the reason when an hour falls short. On the first morning, two of four hours come in at 17 and 18, and both reasons say parts were waiting for a first-off inspection. The team leader checks the board every hour and takes that reason to the improvement meeting. The cell gets its own gauge for first-off checks, and short hours from that cause drop from two most mornings to about one a week.
Common mistakes
- Putting up boards full of charts that are updated weekly by someone outside the team.
- Making signals visible without agreeing who responds and how fast.
- Adding so many visuals that the important ones get lost.
When Visual management is not the right tool
Where most work happens on screens, as in software or back-office teams, a wall board can fall out of date. A shared digital board that the team updates as it works may serve better.
Visual management and andon cord signals
An andon cord is visual management at its most direct: one pull turns a light on and calls for help. Kanban cards, floor markings and 5S shadow boards are quieter visual controls.
Visual boards are the center of a daily management system, where the team reviews them in a short huddle.
Levels of visual devices
Gwendolyn Galsworth sorts visual devices by how much they do. A visual indicator only tells, like a label or sign. A visual signal grabs attention, like an andon light. A visual control limits what people can do, like a marked floor space that holds only so many pallets. A visual guarantee makes the wrong action impossible, which is poka-yoke.
The diagram above follows a similar ladder. When a problem keeps coming back despite a sign, move one level up rather than adding another sign.
Three questions every visual must answer
Visual management links a clear standard, a visible current state and an agreed response. Test any board, sign or screen against three questions:
What should be happening?
The expected order, target, limit or standard.
What is happening now?
Current work, results or exceptions.
What happens when there is a gap?
The response, the owner and the route to escalation.
A visual that only answers the second question is information, not a management tool. Visuals also do different jobs: a delivery chart informs, a shelf label guides placement and an alert tied to a response plan triggers action. Pick the simplest format that supports the decision.
Designing a visual around a decision
Start with a repeated decision that now needs searching, asking or guessing, such as which request to handle next or when a delay needs escalating. "Reviewers cannot tell ready requests from incomplete ones" is a better starting point than "improve transparency". Then write a short brief:
| Element | Question | A good answer |
|---|---|---|
| Audience | Who makes the decision? | Name the role, not "everyone" |
| Location | Where will they see it while working? | At the point of work, not in a report |
| Timing | How fresh must the information be? | Hourly, per shift or daily |
| Signal | What condition needs attention? | A rule, not a judgment call |
| Response | What should follow, and who owns it? | A named role and a next step |
| Evidence | What would show the new method helps? | A measure taken before and after |
Audience
Who makes the decision?
A good answer: Name the role, not "everyone"
Location
Where will they see it while working?
A good answer: At the point of work, not in a report
Timing
How fresh must the information be?
A good answer: Hourly, per shift or daily
Signal
What condition needs attention?
A good answer: A rule, not a judgment call
Response
What should follow, and who owns it?
A good answer: A named role and a next step
Evidence
What would show the new method helps?
A good answer: A measure taken before and after
Keep the brief narrow enough to test, and involve the people who submit, review and receive the work so one team's fix does not create another team's problem.
Matching the visual to the need
| Need | Visual | Setup note |
|---|---|---|
| A confusing process | A flowchart or swimlane map | Show decisions, returns and changes of owner |
| Active work to coordinate | A workflow board | Define states, movement rules and blockers |
| Performance to review | A dashboard | Show trends, context and exceptions |
| A repeated task | A visual work guide | Put the help where the task is done |
| Unusual conditions | A status signal or alert | Say who responds and what comes next |
| Physical order | Labels and location marks | Show the set place and amount |
A confusing process
A flowchart or swimlane map
Setup note: Show decisions, returns and changes of owner
Active work to coordinate
A workflow board
Setup note: Define states, movement rules and blockers
Performance to review
A dashboard
Setup note: Show trends, context and exceptions
A repeated task
A visual work guide
Setup note: Put the help where the task is done
Unusual conditions
A status signal or alert
Setup note: Say who responds and what comes next
Physical order
Labels and location marks
Setup note: Show the set place and amount
On a workflow board, write the rule for entering and leaving each column next to it, and add WIP limits where the team needs to control how much is active. In an office, a blocked request can carry a text label, the reason and the person fixing it. Do not add alerts until someone has agreed to receive and act on them. If you run a wall board and a screen, name one main record and show how current the other is.
Dashboards built around decisions
A dashboard should give a focused view, not repeat every report. Start from the decisions made in team reviews, and give different users different views if one shared screen would be hard to use. For each visual, define:
- Meaning: What the measure actually shows.
- Scope: Which work, team, place or period is included.
- Context: The comparison that makes the number readable, such as target or last month.
- Currency: When the data was last updated.
- Action: Who checks an exception and where that action is recorded.
Use charts that fit the comparison, keep scales consistent and never use color alone for status: pair it with text or symbols, keep strong contrast and check screen reader access on digital reports. Test the draft on the real screens. If a participant cannot spot the most important exception and name the next step unaided, treat that as design feedback.
Setting up a digital visual board
- 1
Define the pilot. One workflow with a clear start and finish, a stated problem and the behavior you want to change. Record a baseline, including how much effort current tracking takes.
- 2
Agree states and rules. Turn the current process into a small set of columns. Define ready and done, and show waiting, blocked, canceled and reopened work where it matters. Decide who can change priority and how urgent requests enter.
- 3
Choose the tool against requirements. List must-haves before demos: access for everyone who needs it, workflow fit, change history, imports and exports, accessibility, who administers it and how you get your data back out. Test with real items, including awkward ones.
- 4
Keep the card template small. A short description, owner, state, due date, blocker, next action and a link to the source record. Remove fields nobody uses, and make sure no item sits between teams without an owner.
- 5
Name data owners. Who updates items, who maintains the flow definitions, who owns dashboard calculations and who administers the board. Check that any automatic state change matches the real work.
- 6
Pilot and revise. Use the board in real coordination, ask which fields people ignore and which states confuse them, and test cancellations, duplicates, absent owners and urgent work before scaling.
A review routine that turns visibility into action
A board helps only when people review it and act. Keep the review short and do not read out every item already visible:
- 1
Check the information is current enough to use.
- 2
Find blocked, aging or unusual work.
- 3
Decide on priorities or promises that need a call.
- 4
Assign a next action, owner and follow-up point.
- 5
Split urgent coordination from deeper study, and schedule the study outside the huddle.
Leaders set the tone: ask what is blocking progress and what help is needed before asking why a number is bad. Tiered meetings connect this review to the levels above.
Visual management failure modes
Watch for signs the system is becoming extra reporting work:
- 1
Stale information. Show how current the data is and agree who updates it. If it is too old for the decision, say so.
- 2
Color without meaning. Set written status rules and pair color with labels, so green is not a personal judgment.
- 3
Too many fields or measures. Ask which decision each one supports and remove the rest.
- 4
Signals without responses. Name who receives each exception and what happens if the first response does not fix it.
- 5
Conflicting records. Pick the main source and reconcile the others.
- 6
Exposure without need. Keep personal or sensitive details off shared displays unless they have been reviewed.
Train with practice, not slides: give users sample cases and ask them to update the board, spot an exception and find the next action. Fix confusing rules before reading uneven use as resistance.
Before scaling a visual pilot
Review the pilot against the original decision problem, noting changes in demand, staffing or work mix, and include the effort needed to keep the board current. Then confirm:
- Flow states: The columns and the done rule are clear to everyone.
- Update duties: Everyone knows who updates what, and when.
- Exceptions: Each has a workable response path.
- Measures: Each has a written definition and source.
- Access: Permissions and accessibility have been tested.
- Duplicate reporting: Removed, or kept for a stated reason.
- Ownership: A named owner keeps the system running after the pilot.
Expand only the parts that earned their place, and keep reviewing the system as the work changes.
Guides on this topic
- Gemba walk checklist: questions, form and routinesA gemba walk checklist with before, during and after steps, question sets for flow, safety and quality, and a free printable gemba walk form and question cards.Read the guide
- Lean construction: principles, techniques and how to startLean construction applies lean thinking to building projects. Learn the principles, the eight wastes on site, the Last Planner System and how to start.Read the guide
- 5S audit checklist: questions, scoring and a templateA 5S audit checklist with five questions per S for manufacturing, office and warehouse versions, scoring guidance, and free printable forms and an Excel sheet.Read the guide
- Kaizen 5S: how 5S and kaizen work together in leanKaizen 5S explained: what 5S and kaizen each do, how they support each other in lean management and how to run them as one daily habit.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Hiroyuki Hirano, 5 Pillars of the Visual Workplace: The Sourcebook for 5S Implementation (Productivity Press, 1995)
- 2.Gwendolyn D. Galsworth, Visual Workplace, Visual Thinking: Creating Enterprise Excellence through the Technologies of the Visual Workplace (Visual-Lean Enterprise Press, 2005)
- 3.David Mann, Creating a Lean Culture: Tools to Sustain Lean Conversions (Productivity Press, 2005)