Our Level 10 Meeting is routinely running over two hours because we get bogged down in the updates before we even reach the IDS section. How do we hard stop the context building and protect our issue solving time?

Question

Tyler Smith · Accepted Answer

Your Level 10 Meeting is running over because your team is treating the reporting section like a discussion. It is a discipline problem, plain and simple. The first half of the meeting exists to flag issues, not to solve them or tell stories.

To fix this, you must enforce a strict, zero-discussion rule during the first thirty minutes. When the Scorecard, Rock review, and customer or employee headlines are read, the only acceptable comments are on track, off track, or drop it to IDS.

If anyone starts explaining why a number is off or starts telling a story about a client, the Integrator or meeting leader must immediately interrupt. Use the phrase: Drop it to the Issues List. Do not let them finish the story.

This feels rude at first, but it is the only way to protect your sixty minutes of IDS. The reporting phase should take exactly twenty minutes. If you spend the first forty-five minutes explaining and justifying, you have already lost the meeting.

Once you transition to IDS, prioritize the list ruthlessly. You will never solve all fifteen issues on your list, so pick the top three and solve them completely. When your team realizes that off-track items are dealt with systematically in the final hour, they will stop trying to defend themselves during the reporting segment. Keep the timer visible on the screen or wall, and hold the line on the agenda.