Our Level 10 Meeting routinely blows past 90 minutes because people turn the five-minute Scorecard and Rock reviews into lengthy storytelling sessions. How do we tighten the front half of the meeting to protect IDS time?

Question

Tyler Smith · Accepted Answer

The first 25 minutes of a Level 10 Meeting exist purely for reporting, not for problem-solving. When a meeting runs past 90 minutes, it is almost always because the team spent half an hour debating a missed metric or narrating a customer headline instead of saving that discussion for IDS.

Enforce strict speaking discipline during the front half of the agenda. For the Scorecard review, each seat owner simply reads their metric and states whether it is above or below target. No excuses, no background stories, and no editorial commentary. If a number is off track, the Integrator asks one simple question: drop it down? If yes, it gets logged on the Issues List.

Apply the identical standard to the Rock review. The owner states only on track or off track. Any commentary lasting longer than two seconds must be cut off by the Integrator and redirected to the Issues List. For customer and employee headlines, mandate a single factual sentence.

By eliminating narrative updates, your team will complete the Segue, Scorecard, Rock review, Headlines, and To-Do list review in exactly 25 minutes. That leaves a full 60 minutes for IDS and five minutes to conclude, keeping the meeting strictly within 90 minutes.