Our Level 10 Meeting™ frequently runs past ninety minutes because our leadership team turns the first twenty minutes of Scorecard and Rock review into an open debate on why numbers are off. How do we enforce the five-minute reporting rules without shutting down necessary discussion?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting breaks down when the leadership team treats the first twenty minutes as a problem-solving session instead of a reporting dashboard. The opening check-ins, Scorecard, Rock review, customer headlines, and To-Do list must be executed in exactly twenty-five minutes. That leaves a full sixty minutes for IDS.

The most common breakdown occurs during the Scorecard and Rock reviews. A leader sees a metric in the red or a Rock marked off-track and immediately asks why. That triggers twenty minutes of defensive storytelling, excuses, and impromptu brainstorming. Your 90-minute structure is dead before you ever reach the Issues List.

To protect the ninety-minute boundary:
- Enforce reporting-only language. When reviewing the Scorecard, the metric owner simply states on track or off track. No context, no explanation.
- If a number or Rock is off track, the Integrator asks a single question: Drop it down? If yes, it becomes an issue on the Issues List. You move on immediately.
- Limit individual check-in highlights to one minute per person during the Segue.
- Appoint a dedicated timekeeper to call out minute markers. If the reporting takes twenty-seven minutes, stop and analyze where the team leaked time.

The purpose of the first twenty-five minutes is visibility, not resolution. When the team trusts that their off-track items will be addressed thoroughly during the designated sixty minutes of IDS, they stop defending their numbers during the review.