Operations Operating practice

Visual Management

Makes work status, standards, and abnormalities visible so teams can respond and learn promptly.

Visual management makes work status, standards, and abnormalities visible so teams can respond and learn promptly. Signals connect observation with support and adjustment.

Core question

Which abnormal condition must the team see, and what response should the signal trigger?

Prepare plan Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 1-20
Time: Ongoing

Phases may be revisited; their order supports the work but does not replace domain judgment.

Visual Management workspace showing the question, observations, and next decision.

Purpose
Clarify purpose and users
Determine who needs to see which abnormality, when, and how to respond.
Signal
Design a simple signal
Show only relevant states, standards, and thresholds; agree their meaning.
Response
Use in the work cadence
Review the board/display regularly and respond to abnormalities with support.
Review
Review usefulness
Ask people which signals help; remove stale displays and adjust standards.

Review the result and open assumptions at the next suitable checkpoint. Record changes, ownership, and new evidence.

A good fit when

Use when: A team workflow with shared cadence, clear states, and a response people can take.

Ideal for

Ops Teams
Service Desks
Shared Workspaces

Not good for

Hidden reporting
One-off presentations

Outputs

Working picture
Determine who needs to see which abnormality, when, and how to respond.
Testable evidence
The evidence review records regular board or display reviews and supportive responses to abnormalities.
Next step
The review records useful signals, updated displays, and resulting adjustments to standards.

Signal, response, and team workflow

Fictional worked example

Make work status, standards, and abnormalities visible so teams can respond and learn promptly.

Work states

Record team goal, users, and decision-relevant abnormality.

Queued → active (WIP max. 3) → done; blocked shown separately.

Signal

Define work states, measure, threshold, and source.

Red: SLA at risk when fewer than 4 hours remain and case is open.

Response

Add signal owner, response, and review cadence.

Team huddle asks about blockers and possible support; no blame.

Review

Record stale displays and agreed changes.

After two weeks, review with the team whether the signal is timely and useful without false alarms.

Fictional service-team board: cards show queued, active, and blocked customer cases. A WIP limit of 3 active cases reveals overload; red marks SLA risk and triggers a brief support check. The board tracks work, not individual performance.

Andon · Lean Enterprise Institute

First step

Start with a bounded question, clarify access and participants, and collect available evidence. Make work status, standards, and abnormalities visible so teams can respond and learn promptly.

Open the method guide

Where to go next?

Operations

Standard Work Analysis

Checks whether the surfaced deviation points to an outdated standard.

Delivery

Value Stream Mapping

Embeds the individual signals into a view of the whole value stream.

Deep dive

Purpose

With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.

How it works

Information is condensed so the normal case and the exception become instantly distinguishable. Clear signals show where intervention is needed and where observation alone suffices. When conditions change, the display is updated along with them and stays useful as a steering surface.

In detail

Visual Management designs information so the normal state and the exception can be told apart without explanation. Signals that trigger decisions or reactions are decisive, rather than just filling nice-looking overviews. As a daily steering surface, the display only stays useful if it is maintained as conditions change.

Facilitation

First clarify which deviations must catch the eye immediately and which information must never end up as mere decoration. The method becomes strong at the point where teams can immediately infer the need for action from the picture. Close with clear maintenance responsibilities and the question of which decisions the board should actually trigger going forward.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Signals Operations Visual management

Sources

Andon · Lean Enterprise Institutelean.orgMethod reference reviewed to support the scope and workflow of Visual Management. Examples and editorial guidance are original and explicitly fictional.

Artifact templates

Visual Management: WorksheetPrepare Visual Management with a clear question, roles, and sources.

markdown

visual-management-working-template.md

Prepare Visual Management with a clear question, roles, and sources.

Visual Management: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Plan the full method Time: Set according to scope and available evidence

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Shared workspace, accessible sources, and a decision log.
Roles: Team · process owner · facilitator
Advance information: Clarify the question, timeframe, data access, roles, and known uncertainties in advance.
Overall time needed: Set up with the team; then use and review in the daily or weekly work cadence.
Setup: Create a shared version. Label facts, assumptions, and decisions separately.