Our Level 10 Meeting frequently runs over ninety minutes because we spend forty-five minutes just reviewing the Scorecard and To-Do list before we even start IDS. How do we tighten our reporting hygiene to protect our problem-solving time?

Question

Tyler Smith · Accepted Answer

The ninety-minute timeline for a Level 10 Meeting is non-negotiable. When meetings run long, it is almost always because the team is discussing issues during the reporting section instead of dropping them down to the issues list. You need to enforce a hard boundary between reporting and solving.

During the first twenty-five minutes, your only job is to state whether a metric is on track, a Rock is on track, or a To-Do is done. The correct response is a simple yes or no. If a metric is off-track, do not let anyone explain why. Do not allow a five-minute story about why a vendor was late. Simply say drop it and write it on the issues list.

By keeping the reporting clean, you preserve a full fifty minutes for the IDS portion of the meeting. If you finish your reporting in twenty-five minutes, you protect the integrity of the agenda. The meeting scribe must actively police this boundary. If someone starts explaining a metric, the scribe or the Integrator must cut them off immediately and add the item to the issues list.

Consistency is what makes this work. When the team realizes that every off-track item will be handled during IDS, they will stop trying to defend themselves during the reporting phase. This keeps the meeting tight, professional, and under ninety minutes.