We keep going over our ninety-minute limit for our weekly Level 10 Meeting™ because our leadership team gets stuck debating operational updates during the reporting section. How do we draw a hard line between reporting and solving?

Question

Tyler Smith · Accepted Answer

Keeping your Level 10 Meeting™ under ninety minutes requires strict behavioral discipline during the first thirty minutes. The reporting section, which includes the Scorecard, Rock review, and people headlines, is designed purely for reporting. It is not the time to explain, defend, or solve problems. When a number is off track or a Rock is behind, the only acceptable response is not on track. The metric or Rock is immediately dropped down to the Issues List.

The trap most leadership teams fall into is allowing a department head to explain why a number is off track. Once the explanation starts, other team members chime in with suggestions, and you have entered premature solving. This eats up your valuable eighty percent of the meeting, which should be reserved entirely for IDS® at the end.

To break this habit, the meeting leader must act as a hard coordinator. When someone starts explaining a red metric, the leader must interrupt and say, Drop it to the Issues List. Do not let them finish the story. Once the team realizes that dropping an item to the list is not a punishment but rather the correct path to resolving it during the dedicated IDS® portion, the reporting section will naturally compress to twenty-five minutes. This leaves a full sixty minutes to prioritize and solve your most critical issues systematically.