Our leadership team constantly gets sucked into solving problems during the first twenty-five minutes of our Level 10 Meeting when reviewing the Scorecard and Rocks, leaving us with only thirty minutes for IDS. How does a facilitator ruthlessly protect the reporting track?

Question

Tyler Smith · Accepted Answer

The first twenty-five minutes of your Level 10 Meeting are designated purely for reporting, not discussion. You have five minutes for the Segue, five minutes for the Scorecard, five minutes for Rock review, five minutes for Headlines, and five minutes for the To-Do list. When leaders start debating why a metric is off or why a Rock is delayed, your ninety-minute meeting falls apart.

To protect the agenda, the facilitator must enforce strict binary reporting:

- On the Scorecard, the owner reads the metric and states whether it hit or missed the goal. No explanations, no apologies, and no stories about bad weather or supplier delays.
- On Rock review, the owner states two words only: on track or off track. If it is on track, move to the next item. If it is off track, it drops directly to the Issues List.
- On the To-Do list, the owner states either done or not done. If it is not done, it rolls over or drops to the Issues List.

Whenever a team member starts defending their number or offering context, the facilitator must interrupt cleanly: We are in reporting mode. Does this belong on the Issues List? Drop it down.

Do not worry about appearing blunt. Your team will appreciate having sixty full minutes reserved for IDS. By containing the operational updates to twenty-five crisp minutes, you ensure that the biggest, ugliest problems get the deep analytical focus they deserve rather than being rushed at the end of the meeting.