Our weekly Level 10 Meeting™ routinely runs over ninety minutes because we get bogged down in status updates before we even reach the IDS® portion. How do we force the team to keep the meeting under ninety minutes without cutting off important conversations?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting™ that runs over ninety minutes is a broken meeting. It usually happens because your team is treating the first thirty minutes as a status update and discussion forum. The agenda of a Level 10 Meeting™ is designed to be highly structured and fast-paced to save your time, not waste it.

To fix this, you must enforce a strict rule of no discussion during the reporting phase. When you review the Scorecard, Rock review, and To-Do list, team members should only state whether a metric is on track or off track, or done or not done. If someone starts explaining why a number was missed or why a Rock is delayed, the Integrator must immediately cut them off and drop that item to the Issues List.

The reporting section should take no more than twenty-five minutes. This leaves you with a full hour for IDS®. This is where your discussions belong. By pushing all conversations to the IDS® portion of the agenda, you prioritize your issues and solve the most critical ones first.

If you run out of time during IDS®, the meeting still ends exactly at ninety minutes. The remaining issues stay on the list for next week. Keeping the meeting strictly under ninety minutes teaches your team to be concise, respect the clock, and focus on solving rather than talking.