A gemba board is a visual team board at the workplace that runs the daily huddle. It organizes the team's key metrics, typically Safety, Quality, Delivery, and Cost, alongside problems and actions, so anyone can see at a glance whether today is normal or abnormal.

The word gemba means "the real place," the spot where the work actually happens, and the board lives there, on the floor, next to the line, not in a manager's office. Its whole purpose is to bring the numbers to where the team stands so a short daily conversation can catch problems while they are still small. This guide covers what belongs on the board, how to lay it out, how the daily huddle uses it, and the design mistakes that turn a living board into wallpaper.

What is a gemba board?

A gemba board, also called a team board, tier board, or day-by-hour board, is the visual centerpiece of daily management. It is a physical or digital display, owned by one team, that shows how the team is performing against its targets right now and what it is doing about the gaps. The board is not a report for management; it is a tool for the team, positioned where the team works, updated by the team, and used every day to run the shift.

The defining feature is that it makes the abnormal jump out. A good board is designed so that a red mark against a target is visible from across the aisle, and so that anyone, an operator, a supervisor, a plant manager on a walk, can read the team's status in seconds without asking a question. That is the difference between a gemba board and a wall of printed charts nobody looks at: the board is built to trigger a conversation and an action, not just to inform.

Anatomy of a gemba boardAnatomy of a gemba boardSAFETYdays since incidentQUALITYdefects vs targetDELIVERYon-time vs planCOSTscrap / downtimePROBLEMS & IDEAS• Line 3 jam at changeover• Label misreads on scanner• Idea: stage totes night beforethe parking lot, raise it here, don't solve it hereACTIONSWHATWHOBYFix scanner angleRosaWedTrial night stagingDevFrievery problem that gets worked becomes an owned action with a date
A gemba board reads top to bottom: metrics across the top show whether the day is normal, the parking lot captures problems and ideas, and the action list turns the ones you work into owned commitments with dates.

What is SQDC, and what goes on the board?

SQDC, Safety, Quality, Delivery, Cost, is the standard set of metric categories on a gemba board, arranged in that order on purpose: safety first, then quality, then delivery, then cost. The order encodes a priority. You never trade safety for delivery, and you never ship bad quality to hit a number. Some plants extend it to SQDCP or SQDCM, adding People or Morale, but the core four are near-universal.

Each category carries one or two simple measures the team actually controls, shown against a target with a clear red/green status per day. Below the metrics sit two working sections: a problems and ideas parking lot where anyone can post an issue or suggestion without solving it on the spot, and an action list where the problems the team decides to work become tasks with a named owner and a due date. Metrics tell you something is wrong; the action list is where it gets fixed.

CategoryQuestion it answersTypical measures
SafetyIs everyone going home safe?Days since incident, near-misses reported
QualityAre we building it right?Defects or scrap vs target, first-pass yield
DeliveryAre we on schedule?On-time to plan, units vs plan by hour
CostAre we running efficiently?Scrap cost, downtime, overtime
The four SQDC categories, in priority order. Keep one or two measures per category that the team genuinely controls, a board with twenty metrics gets read as zero.

How do you design a gemba board?

Design the board backward from the daily huddle it has to run. The board is a tool for a ten-minute conversation, so every element should earn its place in that conversation. Here is the sequence:

  1. Define the team and the cadence. One board serves one team with one owner and one daily meeting time. Decide who stands at it and when, start of shift is typical.
  2. Pick a few metrics the team controls. Choose one or two measures per SQDC category that the team can actually influence today. Vanity metrics and plant-wide numbers the team can't move belong somewhere else.
  3. Set a target and a clear normal/abnormal rule for each. A metric without a target can't be red or green. Define exactly what counts as an off day so the status is objective, not a judgment call.
  4. Make status readable from across the aisle. Big marks, red for off-target and green for on. Someone should read the board's overall state in five seconds without leaning in.
  5. Add the parking lot and action list. Give problems and ideas a place to land, and give worked problems an owned action with a date. This is the engine that turns a status board into an improvement board.
  6. Put it at the gemba and keep it updated by the team. Mount it where the work happens, and have the team, not a coordinator, mark it. A board updated by an outsider stops being the team's.
  7. Run it, then improve it. Use it daily for a few weeks, then prune what nobody looks at and add what the huddle keeps needing. The board evolves.

By the numbers. The gemba concept was popularized for Western management by Masaaki Imai in Gemba Kaizen (1997), which defines gemba as the "real place" where value is created and argues that improvement and management belong there rather than in the office. The Lean Enterprise Institute's lexicon defines gemba the same way, the actual place where work is done, and treats visual, at-the-workplace management as core lean practice (Lean Enterprise Institute, Gemba lexicon). The board is that principle made concrete: the numbers live where the work lives.

How does the daily huddle use the board?

The daily huddle is a short stand-up meeting, usually 10 to 15 minutes, held at the board, at the same time every day, standing up so it stays brief. The team walks the board left to right: check safety, then quality, then delivery, then cost, marking each day's status. Where a metric is red, the team names the problem, decides whether to work it now or park it, and assigns an action with an owner and a date. Where it is green, they move on. The huddle is not a status report to a boss; it is the team running its own day.

Boards also connect upward through tiered daily management. A red on a team board that the team can't resolve on its own escalates to the next tier, a value-stream or plant board, at a slightly later meeting, so problems find the level that can actually fix them without burying every issue in a leadership meeting. This is the same escalation logic as an andon system run on a daily rhythm instead of a real-time one.

Tiered daily management: how problems escalate from the gemba boardThe board feeds a tiered daily rhythmTIER 1team gemba boardshift start, 10 minfix what the team owns;escalate what it can'tTIER 2value-stream boardmid-morningcross-team problemsTIER 3plant boardresources, prioritiesescalate up →← support and decisions flow back down
The gemba board is tier one of a daily rhythm. Problems the team can't solve escalate to the level that can, and support flows back down, so issues find the right altitude fast instead of stalling or clogging a leadership meeting.

What makes a gemba board fail?

The most common failure is too many metrics. A board with twenty numbers gets read as zero, because nothing stands out and the huddle turns into a slow recital. Pick the few the team controls and cut the rest. The second failure is a board with no action list, metrics with nowhere for problems to go, so the team stares at red every day and nothing changes. The board becomes a status display instead of an improvement engine.

Other reliable killers: the board is owned and updated by a coordinator instead of the team, so it stops being theirs; it lives in an office or hallway instead of at the gemba; the targets are missing, so "red" is a matter of opinion; or leadership uses the huddle to interrogate the team instead of to remove obstacles, which teaches everyone to make the board look green rather than tell the truth. A gemba board only works if it is safe to show a problem on it.

Should a gemba board be paper or digital?

Start with paper. A whiteboard and markers cost nothing, change instantly, and force the team to own the board with their own hands, and the discipline of the daily huddle matters far more than the medium. Many excellent boards never become anything but a whiteboard, and that is fine.

The limit of paper shows up in two places: the metrics are only as fresh as the last manual update, and the history erases every morning. If yesterday's board is a photo on someone's phone, you can't see a trend, and a slow slide over two weeks stays invisible until it's a crisis. This is where a digital board earns its place, when the SQDC numbers populate themselves from data captured at the line, the board is live instead of a day behind, the trend is always there, and the same status the team sees at the huddle is visible to the next tier without anyone re-keying it. That is the picture Harmony builds: production and quality data captured at the point of work, feeding a visual management view the team runs its huddle from. CLS made exactly that shift, from paper logs found the next morning to production status visible during the shift, which is what lets a gemba board show today's reality instead of yesterday's. Whichever medium you choose, confirm it against the floor with a regular gemba walk keep it inside the daily discipline of lean manufacturing and pair it with tidy 5S so the board reflects a workplace that is already in order. Done right, the board is where gemba kaizen starts every morning.