We find that our weekly Level 10 Meetings consistently run over during the Scorecard, Rock, and Headline reviews, which leaves us with only thirty minutes for IDS instead of the full sixty. How do we structurally enforce the time limits on these introductory sections so we protect our problem-solving time?

Question

Tyler Smith · Accepted Answer

The first thirty minutes of your Level 10 Meeting™ are designed to review the state of the business, not to solve problems. If your team is regularly running over this limit, you are robbing yourselves of the sixty minutes of IDS® needed to actually fix the business.

To fix this, the facilitator must become a ruthless timekeeper. The introductory sections must be treated as a rapid-fire data download. The check-in is five minutes, the Scorecard is five minutes, Rock review is five minutes, headlines are five minutes, and the To-Do list is five minutes.

If a metric is red on the Scorecard, the owner simply says, Drop it to the Issues List. No story, no explanation, and no immediate brainstorming. If a Rock is off track, say, Off track, drop it, and move on.

If any leader begins to explain the background of a red metric or an off-track Rock, the facilitator must immediately cut them off. Say, We are not solving this now, drop it to the list.

By enforcing this boundary, you create a clear separation between reporting and problem-solving. This discipline ensures you transition to IDS® at exactly the thirty-minute mark every single week, giving your team the focus needed to solve your most critical bottlenecks.