Our Level 10 Meeting™ consistently starts late or runs over because during the first twenty five minutes of reporting, our team constantly drops issues into the conversation instead of just calling out things that are dropped or off track. How do we maintain absolute discipline during the reporting phase?

Question

Tyler Smith · Accepted Answer

The first twenty-five minutes of your Level 10 Meeting™ are designed for reporting, not discussion. When team members try to solve problems during the Scorecard, Rock Review, Headlines, or To-Do list review, they are stealing time from your eighty-minute block of pure problem-solving. This agenda drift kills the energy of the meeting before you even reach the Issues List.

To stop this, the facilitator must be absolutely ruthless. The moment a leader begins to explain why a metric is off track or why a Rock is behind, the facilitator must cut them off. The correct response is a simple phrase: drop it to the list.

The reporting phase must be binary. For the Scorecard, read the number and state if it is on or off track. For Rocks, say on track or off track. For To-Dos, say done or not done. No context is allowed. If a metric is red or a Rock is off track, it immediately goes to the bottom of the weekly Issues List.

By enforcing this strict boundary, you preserve the momentum of the meeting. The team learns that their problems will indeed be solved, but only during the designated IDS® section, where issues are prioritized and addressed in order of impact. Protecting this structure ensures you do not waste thirty minutes on minor operational updates before getting to the real root-cause issues.