A daily management board is a visual scoreboard, usually organized as SQDC (Safety, Quality, Delivery, Cost), where a team marks each category green or red for the day and runs a short stand-up in front of it. A red square is not a report; it is the trigger for an action with an owner and a due date.

The board is the cheapest management system a plant owns and the easiest to get wrong. Done well, it turns yesterday’s results into today’s actions in five minutes at the start of a shift. Done badly, it is wallpaper: a grid of stale numbers nobody looks at. This guide covers what belongs on an SQDC board, how to run the five-minute stand-up that converts a red square into a countermeasure, and how the boards tier upward so problems the floor cannot fix reach someone who can. It is the operating rhythm behind visual management.

What is a daily management board?

A daily management board is a physical or digital board that shows a team’s performance against a small set of measures, one column per day, colored to a target. The dominant layout is SQDC, Safety, Quality, Delivery, Cost, often extended with People (SQDCP). Each row is a category; each cell is a day; the color answers one question: did we hit the standard? Green means yes, red means no, and red is the whole point. A board that is all green is either a flawless operation or, far more often, a board with targets set too soft to tell anyone anything.

The discipline is that every red generates a written action, a short problem statement, an owner, and a date, tracked on the board until it closes. Without that loop, coloring squares is just decoration. With it, the board becomes the front end of the plant’s problem-solving system, feeding root-cause work on the reds that keep coming back.

Anatomy of an SQDC daily management boardAn SQDC board and its actionsCat.MonTueWedThuFriActions (owner / due)SQDCQ Tue: seal defectJ.Lee / FriD Thu: late line 3M.Ortiz / MonEvery red cell owns a row in the actions list. No orphan reds.
The SQDC grid colors each category by day. The right-hand actions list is what separates a management board from wallpaper, every red maps to an owner and a due date.

What belongs on an SQDC board?

Keep it to a handful of measures the team can actually influence by the end of the shift. A board that tries to show everything shows nothing. A workable set:

LetterCategoryTypical daily measure
SSafetyDays without a recordable; near-misses reported; open safety actions
QQualityFirst-pass yield scrap, top defect, holds
DDeliverySchedule attainment, units vs plan, late orders
CCostDowntime hours, overtime, cost per unit vs standard
PPeople (optional)Attendance, cross-training gaps, open improvement ideas

Two rules keep the board honest. First, each measure needs a target so the color means something, “green” without a standard is an opinion. Second, the measures should be things the team owns; putting a plant-wide number the crew cannot move on a floor board just teaches everyone to ignore red. For which measures to pick, the discipline of choosing plant KPIs applies directly: few, owned, and tied to a target.

How do you run the five-minute stand-up?

Run it at the board, standing, at the same time every shift, in five minutes or less. The cadence matters more than eloquence. Here is the sequence:

  1. Color yesterday. Before people arrive, the day’s cells are already marked green or red against target from the shift’s actual numbers, not filled in live from memory.
  2. Walk the reds, skip the greens. Spend no time celebrating green. Go straight to each red: what happened, in one sentence, from the person closest to it.
  3. Assign or update an action. Every red gets a countermeasure with a named owner and a due date, written on the board. If a red is repeating, it is escalated to root-cause analysis not re-explained daily.
  4. Check open actions. Fast pass down the actions list: on track, blocked, or done. Blocked items are the ones that escalate to the next tier.
  5. Escalate what the team cannot fix. Anything outside the team’s control, a maintenance backlog, a supplier issue, a resource conflict, is handed up to the tier-two board with a clear ask.
  6. Close and go. Confirm the plan for the shift and break. Five minutes. The board did its job when the crew leaves knowing the one or two things that need to change today.
From a red square to a closed actionWhat a red square is supposed to triggerRED1-line problemstatementowner + duedateclosed on boardescalate totier-two boardA red with no action attached is the failure mode to watch for.
The red-to-action loop. If the team cannot close an action within its control, it escalates, the board is a router, not a dead end.

How do the boards tier upward?

Boards tier so that a problem lands with the person who can actually solve it. Tier one is the crew at the line, first thing each shift. Tier two is the value-stream or department, an hour later, reviewing the escalations from tier one plus its own measures. Tier three is the plant leadership, reviewing what tier two could not resolve. The escalations flow up; support and decisions flow back down. This is tiered accountability and it is what keeps a floor problem from dying in a notebook or a plant problem from never reaching the floor.

The timing is deliberate: each tier meets after the one below it, so a red raised at the 6:30 line huddle can be on the department board by 7:30 and in front of the plant manager by 8:15 the same morning. Contrast that with a monthly review, where the same problem surfaces four weeks after anyone could have acted on it. Fast tiers are the difference between lean daily management and a status meeting.

How daily management boards tier upwardThree tiers, same morningTier 3: plant ~8:15Tier 2: department ~7:30Tier 1: line crew, shift start ~6:30escalatesupportEscalations rise; decisions and support come back down, within hours, not weeks.
Each tier meets shortly after the one below it, so a floor problem reaches the person who can solve it the same morning. Escalations flow up; support flows down.

How do you start a daily management board?

Start small and let the loop earn trust before you add measures. Pick one line or cell, choose one measure per SQDC letter, and set an honest target for each, honest meaning the line will genuinely go red on a bad day. Put the board where the crew already gathers, and hold the first stand-up yourself so the format is set: color the reds, assign an action, check yesterday’s actions, escalate what you cannot fix, done in five minutes. Resist the urge to launch a twelve-metric board across the whole plant on day one; that is how boards die before anyone believes in them.

For the first two weeks, expect the reds to feel uncomfortable and the actions list to run behind. That is the system working, not failing, the board is surfacing problems that were always there and previously invisible. Protect two things above all: that every red gets an action, and that the stand-up stays short. Once the crew sees a red they raised turn into a fix within days, the board stops being a chore and becomes theirs. Only then add the tier-two connection and, if useful, the People row. A board that grows from a working loop outlasts one installed all at once, the same way a gemba walk habit beats a one-time audit.

Why do daily management boards fail?

They fail in a few predictable ways, and all of them are fixable:

The through-line is that a board is only as good as the loop behind it. Wiring the numbers to the same machine and quality data that feed OEE removes the memory problem and frees the five minutes for actions instead of arithmetic (see the platform). See how one plant made the daily rhythm stick in the CLS case study.

Data & sources

Visual daily management is a documented lean practice, not a proprietary framework.