Our leadership team regularly burns through 45 minutes on the reporting phase alone, leaving barely 40 minutes for IDS. How do we physically cut off the Scorecard, Rock review, and Headlines to protect the 60-minute problem-solving block?

Question

Tyler Smith · Accepted Answer

The first thirty minutes of the Level 10 Meeting™ exist solely for reporting, not for problem-solving. When your Scorecard, Rock review, Headlines, and To-Do list creep past the thirty-minute mark, you starve the team of the 60 minutes required to solve root issues in IDS®.

This agenda drift happens because leaders cannot resist the urge to explain why a number is red or why a Rock is off track. The Integrator must police the verbal boundary ruthlessly. During the Scorecard review, the metric owner reads the metric and says "On track" or "Off track." Nothing else. If a number is off track, the Integrator asks a single question: "Do we need to drop it to the Issues List?" The answer is yes or no. No explanations, no excuses, no context.

Apply the exact same standard to the Rock review. The owner states "On track" or "Off track." If it is off track, drop it down. Do not explain what went wrong or how you plan to fix it. That conversation belongs in IDS®.

For Headlines and To-Dos, keep the tempo rapid-fire. If the timer hits twenty-five minutes and you have not finished the reporting track, stop the conversation and immediately drop any unreviewed items to the Issues List. When you consistently protect the 60-minute IDS block, the team learns to report in bullets rather than paragraphs.