Our Level 10 Meeting consistently bleeds from 90 minutes to two hours because leaders debate context during the Scorecard and Rock reviews rather than waiting for IDS. How do we stop this reporting drift and protect our problem-solving time?

Question

Tyler Smith · Accepted Answer

The first 25 minutes of the Level 10 Meeting are strictly for reporting, not discussion. When leaders begin explaining the backstory behind an off-track metric or a delayed Rock, the Integrator must cut them off immediately. The only acceptable response when reviewing the Scorecard is on track or off track. For Rocks, it is on track or off track. There are no asterisks, no qualifications, and no short narratives allowed during reporting.

If a number is off track or a Rock is struggling, the Integrator directs the scribe to drop it straight to the Issues List. Do not ask for context. Do not ask why it happened. Do not allow the seat holder to defend their performance. Moving an item to the Issues List is not a disciplinary action; it is simply logging an operational fact so the team can tackle it during IDS.

To break the habit of reporting drift, the Integrator must actively police the language in the room. When an owner or department head begins a sentence with, "Well, the reason this is yellow is because vendor shipping was delayed," the Integrator must say: "Drop it to the list."

Keep the reporting sections tightly bound to their standard time allocations: five minutes for Scorecard, five minutes for Rock review, five minutes for customer and employee Headlines, and five minutes for To-Dos. When you honor these limits, you preserve the full 60 minutes required for IDS. If you let debate creep into the first twenty minutes, you steal time from solving root causes, force the meeting past 90 minutes, and exhaust the leadership team.