A lean visual management board should help people understand the current work and the response it requires. A display is not useful merely because it contains metrics, red boxes and a list of overdue actions. The team needs to know what each measure means, which conditions need attention and who can respond.
The Lean Enterprise Institute’s discussion of visual management asks whether boards serve the people using them. The template below is our illustrative application of that principle, not an official LEI template or a validated management assessment.
Choose one purpose for the first board
Start with a specific coordination need: seeing whether a team’s current work is proceeding as intended and exposing obstacles that need help. Do not combine every corporate measure on the first version. Ask the people using the board what information would change their next decision.
A hypothetical administrative team might track requests due today, requests completed and requests blocked by missing information. A production team must use its own approved operating, safety and quality standards. This general management guide does not prescribe production control limits or technical procedures.
Define the measure before choosing the color
Record the measure’s unit, period, source, update owner and meaning. Clarify what is included and excluded. “Completed” could mean drafted, reviewed, accepted by the next team or delivered to the customer; those states are not interchangeable.
Agree the expected condition with the responsible team. Do not invent a target to make the display look complete. If information is missing or out of date, show that plainly rather than treating a blank as zero or a green status.
Use these five sections
Purpose and period: What work and time window does this board describe?
Expected and actual condition: What was agreed, what happened and what source supports the comparison?
Obstacle: What specific condition interrupted the work?
Response: Who owns the next action, what authority is needed and when will the team review it?
Closure evidence: What happened, what remains open and what should change next?
Keep personal performance, medical, customer and other sensitive information out of public displays. Share only what participants are authorized to see. An accessible description of a process issue is more useful than exposing an individual’s details.
Copyable blank record (AI-assisted editorial): Purpose and period: [work being coordinated; review date or time window]. Expected and actual condition: [approved expectation; observed result; unit and source; update owner]. Obstacle: [specific condition preventing the work; unknown information clearly marked]. Response: [next action; responsible owner; required approval or escalation route; review point]. Closure evidence: [receiving owner’s confirmation or other agreed evidence; what remains unresolved; next decision]. Copy one record for each issue that needs a response, using only information the participants may see. Keep the approved expectation visible if the work is late; leave unavailable evidence marked unknown rather than entering zero or clearing the issue.
A completed board example
Editorial example (AI-assisted): This fictional administrative team uses its board to decide which already-approved requests need attention; it is not a production, safety or customer-service standard. Purpose and period: review the current day’s approved requests. Expected and actual condition: the team’s agreed plan is three completed requests; its approved record shows two completed and one still waiting. Obstacle: the remaining request lacks information from another team. Response: the designated coordinator asks the authorized contact for that information and records when the team will review the answer. Closure evidence: the receiving team confirms that the missing information is usable and the approved record shows whether the request is complete.
If the information is still unavailable at review, keep the request visibly unresolved and use the established escalation path. Do not mark it complete because someone sent a message, or change the target to make the board look green. The example shows how the fields connect a condition to a response; replace its fictional quantities and roles with your team’s approved arrangements.
Connect the board with a response routine
Use the daily huddle agenda to examine changed conditions briefly. Move complex investigation to an appropriate follow-up rather than solving every problem in front of the board. When an issue needs authority beyond the team, name the responsible route and what response is expected.
The leader standard work guide helps managers protect the observation and follow-through the board depends on. Information collection without response is an extra reporting burden, not a complete management routine.
Test whether the board changes a decision
After an appropriate trial period, ask which issues became visible, what actions followed and whether users found the definitions clear. Remove fields that do not serve the agreed purpose. Keep an unresolved issue visible until the owner can explain its disposition, rather than clearing it merely because the meeting ended.
If boards are full but obstacles remain unanswered, discuss the leadership response pattern with Shannon. The next improvement may concern ownership and support, not another dashboard. Before choosing outside support, use the lean consulting scope guide to separate leadership support from technical process implementation.
About this resource: Prepared with AI-assisted drafting. Examples and templates are illustrative, not reported client outcomes, a validated assessment or a substitute for required policies and qualified supervision.