Our team routinely allows the first 25 minutes of the Level 10 Meeting to drag out into 40 minutes, which robs our IDS block of crucial problem-solving time. How do we strictly police the 25-minute reporting portion without rushing past critical updates?

Question

Tyler Smith · Accepted Answer

The reporting portion of the Level 10 Meeting agenda is purely transactional. Its entire purpose is to provide situational awareness across the business in exactly twenty-five minutes: five minutes for segue, five minutes for the Scorecard, five minutes for Rock Review, five minutes for headlines, and five minutes for the to-do list. When this block bleeds into forty minutes, it is almost always because leaders start discussing, explaining, or defending numbers instead of reporting data.

To fix agenda drift, the Integrator must enforce one foundational rule: zero discussion during reporting. When reviewing the Scorecard or Rocks, the only acceptable responses from the owner are "on track" or "off track." If a metric is off track, nobody asks why. Nobody explains the market conditions or outlines the recovery plan. The facilitator immediately asks, "Do you want to drop that to the Issues List?" If yes, it gets logged under IDS in three words or fewer. If no, move straight to the next line.

The same rule applies to the To-Do List review. It is a binary check. The item is either done or not done. If it is not done, it either stays on the list for one more week or moves to IDS if it is stuck. There is no status update monologue allowed.

Set a visual countdown timer on the shared screen for each section. When the five-minute timer for the Scorecard dings, the facilitator transitions immediately to the Rock Review, regardless of where you are on the list. Teams quickly learn that if they want their updates heard, they must be concise. By protecting the first twenty-five minutes, you guarantee a full sixty minutes for high-value IDS.