Our weekly Level 10 Meeting™ is consistently running over the ninety-minute mark because our scorecard review and headlines turn into debates before we even build our IDS® list. How do we strictly enforce the timebox without cutting off critical business updates?

Question

Tyler Smith · Accepted Answer

Running over ninety minutes is a failure of discipline, not a lack of time. When your scorecard review, customer headlines, or Rock updates turn into debates, you are letting the meeting hijack itself.

The rule is absolute: the first twenty-five minutes of the Level 10 Meeting™ are for reporting only. There is zero discussion allowed during the Scorecard, Rock review, customer and employee headlines, and To-Do list.

If a number is off track, a Rock is off, or a headline reveals a problem, the meeting leader must immediately say: drop it to IDS®. Do not let anyone explain why the number is red. Do not let anyone defend their progress. The only acceptable response is: drop it to the list.

You must assign a designated timekeeper, usually the Integrator, to enforce this transition. If your reporting takes twenty-six minutes, you have failed the discipline test.

By aggressively pushing all discussions to the final sixty minutes of the meeting, you protect your time to actually solve issues. Once you reach the IDS® portion of the agenda, the team prioritizes the top three issues. You do not start at the top of the list and work down. You pick the absolute most critical issue first.

This structural discipline ensures that your ninety minutes are spent solving the root causes of your biggest problems, rather than getting exhausted by minor updates during the first half-hour.