Our weekly Level 10 Meeting consistently bleeds past 90 minutes because the first five reporting agenda items take forty-five minutes instead of twenty-five. How do we enforce reporting discipline so we actually protect sixty minutes for IDS?

Question

Tyler Smith · Accepted Answer

When the front half of your Level 10 Meeting™ creeps past twenty-five minutes, your team is using reporting time to justify numbers and debate solutions instead of simply reporting facts. That dynamic robs you of the sixty minutes required for true problem solving.

The first twenty-five minutes must follow a rigid cadence:

- Good News: exactly five minutes to transition from the whirlwind into the room.
- Scorecard: five minutes maximum. Leaders read only their metric, the target, and whether it is on track. Zero editorializing.
- Rock Review: five minutes maximum. The owner states the Rock name and says on track or off track. No progress reports.
- Customer and Employee Headlines: five minutes. One-sentence updates.
- To-Do List: five minutes. The owner states whether their seven-day commitment is done or not done.

If any metric is red, any Rock is struggling, or any headline requires discussion, nobody explains why. The Integrator interrupts the speaker immediately and says: Drop it down. The topic is placed on the Issues List in four words or less.

Your Integrator must act as a ruthless timekeeper. If someone begins a narrative with, 'Well, the reason the lead count dropped this week is because...', cut them off. Put it on the list. Protecting sixty minutes for IDS® ensures you fix the root causes behind broken numbers instead of burning your meeting listening to defensive commentary.