Our weekly Level 10 Meeting™ is scheduled for ninety minutes, but the introductory reporting sections take up nearly fifty minutes because leaders constantly feel the need to defend their performance or tell stories. How do we strictly enforce the timebox on these early agenda items?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting™ is designed to spend the vast majority of its ninety minutes on problem-solving. If your reporting sections are taking fifty minutes, you are running an expensive update meeting, not an execution pulse. You must protect your sixty-minute IDS® block at all costs.

The root cause of this time bloat is defensive behavior. When a scorecard metric is red or a Rock is off-track, leaders naturally want to explain why. They start telling stories, sharing context, or defending their actions.

The facilitator must stop this narrative immediately. The rule for the first fifteen minutes of the meeting is simple: report only, do not solve.

When reviewing the scorecard, Rocks, and To-Dos, leaders may only state whether an item is on-track or off-track, or complete or not complete. If a metric is red, it is dropped to the bottom of the Issues List. There is absolutely no discussion allowed during the review.

To enforce this, the facilitator must use the drop-it rule. If a leader starts explaining a number, the facilitator must cut them off and say, drop it to the Issues List.

Keep the pace fast by using these techniques:

- Keep the segue to one minute per person.
- Review the scorecard in under five minutes.
- Review Rocks in under five minutes.
- Review employee and customer headlines in five minutes.
- Review To-Dos in five minutes.

By enforcing these hard boundaries, you will preserve your entire sixty-minute block for actual problem-solving, which is where real operational progress happens.