Our weekly Level 10 Meeting™ is supposed to be ninety minutes, but we consistently find ourselves dragging it out to two hours because the reporting segments crawl and we never have enough time left for IDS®. How do we tighten our reporting segments to protect our problem-solving block?

Question

Tyler Smith · Accepted Answer

A weekly Level 10 Meeting™ that consistently runs over ninety minutes is a structural failure, not a sign of hard work. When meetings drag on, it is almost always because the team is allowing discussion and problem-solving to bleed into the reporting segments.

To protect your ninety-minute limit, you must treat the first thirty minutes as sacred and strictly informational. The Segue, Scorecard, Rock Review, Customer/Employee Headlines, and To-Do List must be completed in exactly thirty minutes. There is absolutely no discussion allowed during this time.

If a scorecard metric is red, the owner says off track, and it immediately gets dropped to the Issues List. If a Rock is off track, it goes to the Issues List. If a headline needs further context, it goes to the Issues List. Do not let team members start explaining, justifying, or brainstorming solutions during the reporting phase.

This discipline leaves you with a full, uninterrupted sixty minutes for IDS®. By keeping the reporting fast and binary, you preserve the energy and focus of the team for actual problem-solving. If your Integrator is not actively cutting off cross-talk during the first thirty minutes, the meeting will fail. Establish a hard rule: if it requires more than a ten-second update, it goes to the bottom of the list for IDS®. This simple boundary keeps your meetings productive, focused, and strictly under the ninety-minute mark.