The board meeting (Daily Management)
Daily Huddle / Tier Meeting
The board meeting is the daily pulse of operations: 10-15 minutes standing in front of the board, where yesterday’s deviations become visible, get an owner and a deadline — so problems are handled while they are small.
Use the method when
- →Deviations are discovered days or weeks after they arose
- →Firefighting dominates because small problems are allowed to grow
- →The team lacks a fixed forum where “what’s bugging us” is said out loud and owned
Don’t use it when
- →As a replacement for actual problem solving — the board meeting FINDS problems and assigns ownership; it does not SOLVE them (A3/5 Whys does that afterwards)
- →If management won’t take part in the cadence itself — a board meeting the manager skips dies in three weeks
Before you start
The board shows max. 4-6 metrics the team can influence, updated daily
Fixed time, fixed place, fixed duration — same time every day, no exceptions
An escalation channel exists: what the team can’t solve must be passable onward the same day
How to do it — step by step
Safety first
1-2 minAlways the first item: incidents, near-misses and observations since yesterday. Not as a ritual, but because the order shows the priority, and because near-misses are free learning.
Review the board’s numbers — only the deviations
3-4 minEach metric is turned over: green is passed without comment, red gets 30 seconds: what happened? Not why (that is analysis, not a board meeting) — only what, so the deviation is recorded and visible.
Each red gets an action with a name and a date
3-4 minThe mechanical rule that separates management meetings from information meetings: red number → action → one name (not “we”) → a date. Actions are written on the board’s action list, visible to all.
Follow up on yesterday’s actions — first
2-3 minYesterday’s actions are reviewed: closed, in progress or blocked? Blocked actions are escalated immediately. This item is the meeting’s backbone — skip it, and the team learns that the action list is a parking lot.
Escalate what the team can’t solve itself
1-2 minDeviations outside the team’s mandate are sent to the next level (tier 2) the same morning — with a concrete formulation: what is the problem, what have we tried, what do we need. And the answer must come back: an escalation without feedback is the last escalation.
Today’s plan and allocation
2-3 minBriefly: today’s expected load, special orders, absence and reallocation. Finish on time — every time. A meeting that overruns loses its authority as a routine.
The classic mistakes
How it goes wrong in practice, and this is where most implementations part ways.
The meeting grows
15 minutes becomes 30, discussions break out in front of the board. The rule: problems are identified at the meeting, solved after the meeting — by the two or three relevant people, not the whole team.
The board reports upward instead of managing the team
When the board’s numbers are chosen to impress management rather than manage operations, the team stops using it. The board is the team’s tool — management’s insight is a side effect.
Red without reaction
The same number is red three weeks running, and everyone has stopped seeing it. Persistent red is not a board deviation — it is a problem that needs an A3 and an owner outside the meeting.
The meeting is owned by one person
When the leader is ill, the meeting is cancelled — then it isn’t a system but one person’s habit. Rotating facilitation to a simple standard makes the meeting robust.
Related standards
The standard is free. The anchoring is the craft.
The method only works when it becomes daily routines and leadership behaviour. The operations check shows in 4 minutes where your operations stand, and what should come first.