Summary
Board meetings are the most widespread Lean practice in Western companies — and the one that most often dies quietly. The meetings start with energy, drift into status readings, and are eventually skipped when everyday pressure mounts.
This analysis reviews what the literature points to as the difference between board meetings that die and Daily Management systems that carry operations year after year: a cascade with escalation, leader standard work, and a meeting discipline that treats deviations as information. The analysis draws on recognised literature — not on surveys or our own client data.
Introduction: the board is not the system
David Mann, whose Creating a Lean Culture(2010) is the standard work on the subject, put the core plainly: Lean implementations rarely fail on the technical tools — they fail on what he calls “the missing link”: a management system that keeps the new way of working alive. The board is only the visible part. The system is the routines that surround it.
Mann’s estimate has been cited widely since: that successful Lean is roughly 20% technique and 80% management behaviour. Whether or not you take the number literally, the proportion captures something every practitioner recognises: two companies can have identical boards — and wildly different results.
The question is therefore not whether to hold board meetings. It is what separates the systems that last from the ones that die. The literature points to four elements.
Part 1: The four elements that carry a Daily Management system
Based on Mann (2010), Rother (2010), Shook (2008) and Liker & Convis (2011).
The cascade: three tiers with escalation
A standalone board meeting is an island. A Daily Management system is a chain: Tier 1 at the line (10-15 minutes), Tier 2 at department level, Tier 3 with the leadership — each with its own time slot, so a problem that arises in the morning can reach the leadership’s table the same morning if it requires a mandate.
The cascade’s function is not reporting upwards — it is filtering and escalation. The team solves what the team can. The rest is escalated explicitly, with a name and a deadline. Without that mechanism the board meeting becomes a place where problems are mentioned but not owned. Mann describes it as the difference between “information boards” and “improvement boards”: the first shows numbers; the second drives actions.
“The lean management system sustains the gains from lean production conversions. Without it, the gains erode — usually quickly.”
— David Mann, Creating a Lean Culture (2010)
Leader standard work
Mann’s most overlooked point: standard work doesn’t apply only to operators. Leaders at every level need their own — a short, recurring routine of board rounds, gemba visits and follow-up points, taking up a growing share of the day the closer you are to the floor (up to half of a team leader’s day; a smaller but fixed share for the plant manager).
The logic is the same as for all other standard work: what isn’t standardised varies with how busy things are. And management follow-up that varies with busyness is precisely what Repenning and Sterman (2001) identified as the mechanism behind improvements that slip: under pressure, prevention gets deprioritised — and then the pressure grows.
Deviations as information — not accusation
A board meeting lives on problems becoming visible. It dies when showing them is dangerous. John Shook describes from NUMMI (2010) how the culture change began with a visible problem being treated as a gift — something the system could now learn from — rather than an accusation against the person who reported it.
In practice this is decided in the first weeks: does the leader respond to a red number with curiosity (“what blocked us?”) or with blame (“why didn’t you make it?”). Choose the latter, and the organisation learns to colour the numbers green — and the board loses its function as a source of truth. Deming said it most briefly: drive out fear, or you will never get honest data.
The coaching routine: questions rather than answers
Mike Rother’s Toyota Kata(2010) documents the pattern that turns Daily Management into a learning system rather than a control system: the leader doesn’t deliver solutions at the board, but asks a fixed set of questions — what is the target, what is the actual condition, what is blocking us, what is the next experiment, what did we learn from the last one?
The effect is twofold: problem-solving capability is built in the people who face the problems — and the system stops depending on one strong leader. That is exactly what makes the difference between a system that survives a change of leadership and one that dies with it.
Part 2: The five causes of death
Patterns that recur in the literature and in the field when board meetings lose their function.
1. The meeting becomes a status reading
The numbers are read aloud, but no deviation gets an owner and a deadline. Mann: a board without an action trail is a notice-board ritual, not a management system. The test is simple — can you point to what yesterday's meeting changed?
2. The leader stays away — or takes over
Two opposite mistakes with the same result. If the leader stays away, it signals the meeting doesn't matter. If the leader takes over and dictates solutions, the learning stops (Rother). Both hollow out ownership.
3. Escalation without a return loop
The team escalates a problem — and never hears what happened. After three times, they stop escalating. An escalation path is only credible if answers and status flow visibly back.
4. Stale or hand-picked numbers
Data that is three days old, or KPIs chosen to look good, make the meeting meaningless. The board must show the unfiltered, current condition — otherwise the decisions get made elsewhere anyway.
5. No link to direction
When the board KPIs don't connect to the company's goals (the Hoshin link), the meeting feels like administration. The cascade must run both ways: goals down, deviations and learning up.
Part 3: How to build a system that lasts
Five recommendations in sequence — based on the literature and field experience.
Start with one Tier 1 meeting — and make it excellent
One team, one board, the same time every day, max 15 minutes, four fixed questions: What happened yesterday? What deviated? What is the plan today? What needs escalating? Only expand once the meeting has run stably for 4-6 weeks.
Write down leader standard work before you scale
When does the team leader walk their round? What questions does the department manager ask at the board? What does the plant manager check weekly? Unwritten management routines disappear under pressure — written ones can be held onto and handed over.
Build the escalation path with a return loop
Every escalated problem has an owner, a deadline and a visible answer back to the team. The metric is not the number of escalations, but the response time — it tells the team whether the system can be trusted.
Train the reaction to red numbers
Agree explicitly in the leadership team how to respond to a deviation: curiosity before explanation, process before person. One wrong reaction in week two costs more credibility than ten good meetings can rebuild.
Measure the system's health — not only the operation's
Track the completion rate (are the meetings held?), action closure (are agreed actions closed on time?) and escalation response time. If they fall, the system is dying — long before the KPIs show it.
Sources
- Mann, D. (2010). Creating a Lean Culture: Tools to Sustain Lean Conversions (2nd ed.). Productivity Press.
- Rother, M. (2010). Toyota Kata. McGraw-Hill.
- Shook, J. (2008). Managing to Learn. Lean Enterprise Institute.
- Shook, J. (2010). How to Change a Culture: Lessons from NUMMI. MIT Sloan Management Review, 51(2).
- Liker, J. & Convis, G. (2011). The Toyota Way to Lean Leadership. McGraw-Hill.
- Repenning, N. & Sterman, J. (2001). Nobody ever gets credit for fixing problems that never happened. California Management Review, 43(4).
- Deming, W.E. (1986). Out of the Crisis. MIT Press.
This analysis was prepared by Prozanta and is based on publicly available academic material. It does not constitute legal or financial advice.