Our Level 10 Meeting™ constantly runs over ninety minutes because our leadership team treats the first three sections as a place to tell long-winded stories rather than a quick check-in. How do we enforce the time limit without shutting down valuable context?
If your Level 10 Meeting™ is routinely exceeding ninety minutes, your team is violating the fundamental rule of the check-in sections: they are discussing issues rather than reporting them. The first twenty-five minutes of the meeting are designed for rapid-fire data sharing, not strategic debate.
To fix this, you must enforce a strict zero-discussion rule during the Scorecard, Rock review, and customer/employee headlines. If a number is red, the owner simply says off track. No explanations, no excuses, and no storytelling. If a Rock is off track, say off track. If another team member has a question or wants to help, that item is immediately added to the Issues list for later.
The Integrator must act as an aggressive gatekeeper. When a leader starts explaining why a metric was missed, the Integrator must cut them off and say, drop it to the Issues list. This keeps the meeting moving and preserves your time for the actual IDS® portion.
Remember, the value of the Level 10 Meeting™ is concentrated in the sixty minutes of solving problems, not the thirty minutes of administrative updates. By enforcing strict reporting discipline in the first third of the meeting, you protect your time to actually solve the systemic issues holding your operations back.
Category: EOS Implementation