Our weekly Level 10 Meeting always runs past ninety minutes because our leadership team turns the Scorecard and Rock reviews into long discussions before we even get to IDS. How do we keep the first thirty minutes tight so we finish on time?

Question

Tyler Smith · Accepted Answer

The first twenty-five minutes of a Level 10 Meeting are designed for reporting, not discussion. When leaders start debating why a Scorecard metric was missed or explaining the story behind an off-track Rock, the agenda collapses and you run out of time to solve root causes.

Your Integrator must act as an unsentimental timekeeper. Run the clock strictly:
- Good news segue: five minutes. Each person shares one personal and one professional win, with zero commentary from the room.
- Scorecard review: five minutes. The leader reads the numbers. Owners say only whether their measurable is on track or off track.
- Rock review: five minutes. Each owner reads their Rock and says either on track or off track.
- Customer and employee headlines: five minutes. Brief updates only.
- To-Do list: five minutes. Owners report done or not done. If a task is not done, it stays on the list for one more week or becomes an issue.

Whenever a team member starts explaining why a number is red or why a project is delayed, the Integrator must cut them off immediately. Say: Drop it down. That item goes straight to the Issues List.

Reporting highlights what needs attention; IDS is where you solve it. By keeping the reporting tracks to twenty-five minutes, you protect a full sixty minutes for IDS and five minutes to conclude. That is how the meeting stays under ninety minutes every single week.