Our weekly Level 10 Meeting constantly runs past ninety minutes because our team starts debating issues during the reporting segments. How do we regain time discipline and protect the IDS portion?
A Level 10 Meeting runs long for one primary reason: your leadership team is talking and solving problems during the reporting phase instead of reporting data.
The agenda has a rigid time allocation for a reason. The first twenty-five minutes are strictly for reporting:
- Good News (five minutes)
- Scorecard (five minutes)
- Rock Review (five minutes)
- Customer and Employee Headlines (five minutes)
- To-Do List review (five minutes)
During these segments, there is zero room for discussion, context, or debate. When reviewing the Scorecard, the number is either above or below the goal. If it is below, the owner simply says "drop it." The Integrator adds it to the Issues List without anyone explaining why it was missed. The exact same rule applies to Rocks. The answer is "on track" or "off track." If off track, drop it to the list. No explanations.
The Integrator must act as a ruthless timekeeper. When a leader starts saying "well, the reason the metric is down is because our vendor delayed delivery," the Integrator must immediately cut them off and say: "Drop it to the list. We will discuss it during IDS."
This structure protects sixty full minutes for Identify, Discuss, and Solve (IDS). When you protect that sixty-minute block, you tackle the most important issues first and finish the meeting in exactly ninety minutes every single week.
Category: EOS Implementation