Our weekly Level 10 Meeting regularly runs over ninety minutes because our reporting sections drag on, leaving us with less than fifteen minutes for IDS. How do we trim the administrative fat from our meeting agenda to protect our problem-solving window?

Question

Tyler Smith · Accepted Answer

When your Level 10 Meeting consistently runs long and leaves no time for IDS, you are treating the meeting as a status update rather than a problem-solving engine. The reporting sections of the agenda must be fast, disciplined, and strictly limited to twenty-five minutes.

To trim the fat, establish a hard rule: reporting is for identifying issues, not solving them. During the Scorecard, Rock review, and customer or employee headlines, your team members must only state whether a metric is on track or off track. There is no room for stories, explanations, or context.

If a Scorecard number is red, or if a Rock is off track, the leader does not explain why. They simply say, off track, and the Integrator or meeting leader immediately drops that item to the Issues List. The same rule applies to headlines. If a customer has a major issue, it goes straight to the Issues List.

By stopping all discussion during the reporting phase, you can easily breeze through the first five sections in twenty-five minutes. This preserves a full sixty minutes for IDS, where you can systematically prioritize and solve the issues you just identified. If your team starts telling stories during reporting, the meeting leader must immediately intervene and drop the item to the bottom of the board.