Complete firstClear scope
A team workflow with shared cadence, clear states, and a response people can take.
Without a boundary, data, perspectives, or flows become mixed.
Method guideOperations
Visual Management
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityLow
TimeOngoing
Participants1-20
FormatWorkshop + async
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstAccess to evidence
Relevant people and sources can be included.
Gaps remain visible; missing evidence must not be invented.
02
Preparation
What needs to be ready before start
Materials
Shared workspace, accessible sources, and a decision log.
People / roles
Team · process owner · facilitator
Pre-read
Clarify the question, timeframe, data access, roles, and known uncertainties in advance.
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.
03
Core question
The one question this method answers
Which abnormal condition must the team see, and what response should the signal trigger?
04
Flow
Phases with goal, actions, output and pitfall
Visual management makes work status, standards, and abnormalities visible so teams can respond and learn promptly. Signals connect observation with support and adjustment.
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.
- 1
Purpose
Clarify purpose and users
Goal
Does visibility improve work at the point of use?
Inputs for this step
- Team goal and meaningful abnormality
Actions
- Determine who needs to see which abnormality, when, and how to respond.
- Does visibility improve work at the point of use?
Output
Work goal and meaningful signals
Work goal and meaningful signals
Quality check
Does visibility improve work at the point of use?
Pitfall
Display has no agreed response Agree an owner, response time, and action for each signal.
Timing: Part of the agreed work block; research may be separate.
- 2
Signal
Design a simple signal
Goal
Does everyone interpret the signal the same way?
Inputs for this step
- States, standards, and thresholds
Actions
- Show only relevant states, standards, and thresholds; agree their meaning.
- Does everyone interpret the signal the same way?
Output
Shared, interpretable display
Shared, interpretable display
Quality check
Does everyone interpret the signal the same way?
Pitfall
Stale data gives false status Show source, update cadence, and expiry clearly.
Timing: Part of the agreed work block; research may be separate.
- 3
Response
Use in the work cadence
Goal
Is there an accountable response rather than display alone?
Inputs for this step
- Agreed response and cadence
Actions
- Review the board/display regularly and respond to abnormalities with support.
- Is there an accountable response rather than display alone?
Output
Agreed response cadence
Agreed response cadence
Quality check
Is there an accountable response rather than display alone?
Pitfall
Board becomes an individual leaderboard Show team flow and blockers; avoid individual performance surveillance.
Timing: Part of the agreed work block; research may be separate.
- 4
Review
Review usefulness
Goal
Does visibility support learning rather than surveillance?
Inputs for this step
- User feedback and stale signals
Actions
- Ask people which signals help; remove stale displays and adjust standards.
- Does visibility support learning rather than surveillance?
Output
Feedback-based signal adjustment
Feedback-based signal adjustment
Quality check
Does visibility support learning rather than surveillance?
Pitfall
Too many signals hide abnormalities Show only abnormalities that trigger support or a decision.
Timing: Part of the agreed work block; research may be separate.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned result with question, evidence, open issues, next action, ownership, and review date.
Versioning / ownership
Record date, scope, sources, and changes. Preserve earlier observations.
Tool alternatives
- Whiteboard or paper
- Shared spreadsheet
- Versioned project space
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.
Prepare for the work steps
Purpose: Clarify purpose and users
- Team goal and meaningful abnormality
Signal: Design a simple signal
- States, standards, and thresholds
Response: Use in the work cadence
- Agreed response and cadence
Review: Review usefulness
- User feedback and stale signals
Signal, response, and team workflow
Work states
Record team goal, users, and decision-relevant abnormality.
...
Signal
Define work states, measure, threshold, and source.
...
Response
Add signal owner, response, and review cadence.
...
Review
Record stale displays and agreed changes.
...
Blank worksheet: start with a bounded question. Enter observed facts only, mark assumptions, and record open questions and sources.
Andon · Lean Enterprise Institute
Purpose: Clarify purpose and users
Expected artifact: Work goal and meaningful signals
Work goal and meaningful signals
Entry:
...
- Does visibility improve work at the point of use?
Signal: Design a simple signal
Expected artifact: Shared, interpretable display
Shared, interpretable display
Entry:
...
- Does everyone interpret the signal the same way?
Response: Use in the work cadence
Expected artifact: Agreed response cadence
Agreed response cadence
Entry:
...
- Is there an accountable response rather than display alone?
Review: Review usefulness
Expected artifact: Feedback-based signal adjustment
Feedback-based signal adjustment
Entry:
...
- Does visibility support learning rather than surveillance?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/visual-management/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
visual-management-beispiel.md
Concrete filled scenario, fictional example
Fictional worked example
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.
All names and values are invented for illustration. Unresolved explanations remain questions.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Clarify purpose and usersDisplay has no agreed responseView in phase
- Design a simple signalStale data gives false statusView in phase
- Use in the work cadenceBoard becomes an individual leaderboardView in phase
- Review usefulnessToo many signals hide abnormalitiesView in phase
Trap
Clarify purpose and users
Symptom
Display has no agreed response
What to do
Agree an owner, response time, and action for each signal.
Trap
Design a simple signal
Symptom
Stale data gives false status
What to do
Show source, update cadence, and expiry clearly.
Trap
Use in the work cadence
Symptom
Board becomes an individual leaderboard
What to do
Show team flow and blockers; avoid individual performance surveillance.
Trap
Review usefulness
Symptom
Too many signals hide abnormalities
What to do
Show only abnormalities that trigger support or a decision.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
The question or boundary remains ambiguous: narrow it first.
Key data or participants are missing: label the gap and arrange access.
The group mixes observation and explanation: revisit the evidence.
An immediate safety or operational risk appears: stop and use the responsible procedures.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.