Our Level 10 Meeting is exactly ninety minutes, but we spend almost the entire time in administrative updates and have only ten minutes left for IDS. How do we hard-stop the reporting phase so we actually solve issues?

Question

Tyler Smith · Accepted Answer

To protect your sixty minutes of problem solving, you must treat the first twenty five minutes of your Level 10 Meeting as a strict, non-negotiable reporting zone. The reporting sections (the Segue, Scorecard, Rock Review, People Headlines, and To-Do List) are designed for share-and-go updates, not for discussion.

To make this stick, implement three rules immediately:

First, the meeting leader must call out any discussion during the first twenty minutes. If a metric is red or a Rock is off track, do not allow the owner to explain why or start solving it. The only acceptable response is to drop it down to the Issues List.

Second, keep metrics and Rocks binary. They are either on track or off track, and the update should take no more than three seconds per item.

Third, prep your data before you walk in. If leadership team members are still updating the Scorecard or thinking about their headlines during the meeting, you have already lost.

By enforcing these boundaries, you transform your weekly meeting from a boring status update into an active execution engine. You will find that ninety percent of the value of the meeting happens in the final sixty minutes of uninterrupted problem solving.