Our weekly Level 10 Meetings regularly drag on past two hours because the team wanders off on tangents during the reporting sections before we even get to the Issues List. How do we enforce the strict 90-minute timebox without cutting off necessary dialogue?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting drags because the leadership team treats the first thirty minutes as an open discussion forum instead of a rapid reporting cadence. The first five sections exist solely to uncover problems, not solve them.

The time allocations are non-negotiable:
- Good News: 5 minutes
- Scorecard: 5 minutes
- Rock Review: 5 minutes
- Customer and Employee Headlines: 5 minutes
- To-Do List: 5 minutes
- IDS: 60 minutes
- Conclude: 5 minutes

To protect the clock, the Integrator must police reporting ruthlessly. During the Scorecard review, owners only state whether their number is at or below target. No explanations, no backstories, no excuses. If a number is off, the owner simply says drop it, and the Integrator logs it on the Issues List.

The same rule applies to Rocks. The owner says on track or off track. If it is off track, it goes straight to the Issues List. Do not allow anyone to explain why a Rock is delayed during the review phase.

When leaders attempt to justify numbers or debate headlines, the facilitator must cut them off immediately and add the topic to the board. All dialogue belongs inside the 60-minute IDS block. By protecting the first twenty-five minutes, you guarantee a full hour of uninterrupted time to solve root issues without ever running over.