Our Level 10 Meeting™ always runs long because our reporting segments, especially the Scorecard and Rock review, turn into discussions before we even get to the IDS® portion. How do we strictly quarantine the reporting section to keep the meeting under ninety minutes?

Question

Tyler Smith · Accepted Answer

The key to keeping your Level 10 Meeting™ under ninety minutes is absolute discipline during the first twenty-five minutes. The reporting portion of the agenda is designed for data transmission, not discussion. When you review the Scorecard, Rock progress, and customer headlines, you are identifying issues, not solving them.

To enforce this discipline, you must use a strict rule: if an item requires more than a simple on track, off track, or a brief update, it must be dropped to the Issues List. For example, when reviewing the Scorecard, if a metric is red, the owner simply says off track. No explanations, no excuses, and no context are allowed at that moment. The meeting leader must immediately drop that metric to the bottom section of the agenda for IDS® later.

The same rule applies to the Rock review. Each leader states whether their Rock is on track or off track. If it is off track, it goes straight to the Issues List. If anyone starts to explain why a Rock is slipping, the Integrator must politely interrupt and say, let us drop that to IDS.

By quarantining discussion, you protect your sixty-minute problem-solving block. This structure prevents meeting fatigue and ensures your team spends their energy solving the root causes of major problems rather than wasting time on minor operational updates. Master this division, and your ninety-minute limit will become your team's favorite constraint.