Our weekly Level 10 Meeting constantly runs over ninety minutes because the reporting section drags out to forty-five minutes before we even touch the Issues List. How do we ruthlessly hold the first twenty-five minutes so we protect our issue-solving time?
Reporting is strictly status updates, not discussion. The first twenty-five minutes of your Level 10 Meeting have a strict minute-by-minute budget:
- Good News: 5 minutes
- Scorecard: 5 minutes
- Rock Review: 5 minutes
- Customer and Employee Headlines: 5 minutes
- To-Do List: 5 minutes
Total: 25 minutes. When teams run over, it is almost always because leaders start explaining their numbers, offering context, or proposing solutions. The Integrator must step in and shut down narrative reporting immediately.
For the Scorecard, the metric owner states only the target and the actual number. There is no commentary allowed. If a number is missed, the owner says off track, and the Integrator asks whether it needs to drop to the Issues List. If yes, write it down; if no, move to the next metric.
For the Rock Review, each leader states only on track or off track. If a Rock is off track, it drops directly down to the Issues List without explanation. It is not litigated in the moment.
Headlines are one-sentence announcements. To-Dos are binary: done or not done. If a To-Do is not done, you decide whether it stays on the list for one more week or drops down to the Issues List.
Protecting the 60-minute IDS block requires an Integrator willing to cut people off mid-sentence with five simple words: Drop it to the list.
Category: EOS Implementation