Our Level 10 Meeting consistently bleeds past 90 minutes because the first twenty minutes turn into storytelling and status updates during the Scorecard and Rock review. What specific reporting disciplines stop the reporting phase from eating our IDS time?

Question

Tyler Smith · Accepted Answer

The first twenty minutes of a Level 10 Meeting exist purely for reporting, not discussion. When leaders begin explaining the backstory behind a missed metric or detailing why a Rock is delayed, your ninety-minute discipline collapses. This storytelling robs the team of the sixty minutes required to identify, discuss, and solve the real issues holding the business back.

To fix this dynamic, enforce ruthless binary reporting. The Scorecard review must take no more than five minutes. Each leader reads their measurable, reports the current number, and states whether it hit the goal. If the number missed, the leader says one word: drop. The Integrator writes the measurable on the Issues List without allowing a single sentence of explanation.

The same rule applies to the Rock review, which must also finish in five minutes. Each owner reads their Rock title and states either on track or off track. There is no middle ground. An Integrator must cut off any owner who begins giving context with a simple prompt: is it on track or off track? If it is off track, drop it to the Issues List.

By keeping the Good News, Scorecard, Rock Review, Customer/Employee Headlines, and To-Do list within the first twenty-five minutes, your team preserves a full sixty minutes for IDS. If an issue is truly important, it gets prioritized and solved in the back half of the meeting where root cause problem solving belongs.