Our weekly Level 10 Meeting™ regularly runs over ninety minutes because our leadership team spends too much time sharing status updates and debating minor points during the reporting section. How do we keep our meetings strictly within the time limit without cutting off critical business discussions?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting™ that consistently runs over ninety minutes is failing because the team is violating the agenda rules. The first thirty minutes of the meeting must be a fast, high-level review of your Scorecard, Rock progress, and To-Do list. There is absolutely no problem-solving allowed during this phase. If a metric is off-track, or a Rock is behind, the only acceptable response is to say drop it down to the Issues List.

The root of your time problem is usually a lack of discipline from the meeting leader, typically the Integrator. When a metric is missed, team members instinctively start explaining why it happened or how they plan to fix it. This is where your meeting lead must step in immediately. They must cut off the explanation and direct the team to drop the issue to the bottom of the agenda. The reporting section is for identifying problems, not solving them.

By protecting the first thirty minutes, you preserve a full hour for the IDS® portion. This is where your actual discussions belong. Once you transition to IDS®, you prioritize the issues so you tackle the most important ones first. If you run out of time at the ninety-minute mark, the remaining issues simply roll over to next week. This structure ensures that your team stays focused on the root causes of major bottlenecks instead of getting exhausted by endless operational chatter before you even reach the Issues List.