Our weekly Level 10 Meetings are dragging on past two hours and turning into status updates. How do we keep them strictly under 90 minutes without cutting off important discussions?

Question

Tyler Smith · Accepted Answer

The discipline of the Level 10 Meeting™ requires keeping it to a hard 90 minutes. When meetings consistently run long, it is almost always due to the team solving issues during the reporting phase. To fix this, you must enforce a strict boundary between reporting and problem-solving.

Structure Your Level 10 Meeting for Efficiency

Reporting Phase: 15 Minutes

Dedicate the first 15 minutes of the meeting strictly to reporting. This phase should cover:

• Reviewing the Scorecard. For tips on speeding this up, see [how to review our weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes).
• Progress on Rocks.
• Customer and employee headlines.
• The previous week's To-Do list.

During this time, if anyone begins to explain, defend, or debate a number or headline, the meeting leader must immediately stop the discussion and state clearly: "Let's drop that to the IDS section." This ensures a rapid-fire, "yes or no" reporting style. This phase should not delve into why a number was missed, only what the number is. If you're struggling with team defensiveness, consider [handling defensiveness around red scorecard metrics](/qa/handling-defensiveness-around-red-scorecard-metrics).

IDS® Phase: 60 Minutes

By keeping the first 15 minutes disciplined, you preserve a full 60 minutes for your IDS® (Identify, Discuss, Solve) section. This is where the team actively solves issues that were identified during reporting or added to the issues list.

• Focus on resolution: The primary goal is to work through the identified issues effectively.
• Time-bound: If you do not finish your issues list within this hour, you do not extend the meeting.
• Carry over issues: Any remaining issues are carried over to the next week's meeting. This approach maintains the team's energy and respect for the meeting schedule, reinforcing the importance of being concise and effective during the allotted time. When issues are dropped to IDS, it's crucial to [use the Accountability Chart to stop the blame game](/qa/using-accountability-chart-to-stop-blame-in-ids).

Related questions

• [How to review our weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes)
• [Handling defensiveness around red scorecard metrics](/qa/handling-defensiveness-around-red-scorecard-metrics)
• [Our Integrator acts as the Level 10 Meeting facilitator but struggles to participate objectively because they are busy managing the timer and the agenda. Should we rotate the facilitator role or hire an outside moderator?](/qa/should-integrator-facilitate-level-10-meetings)
• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers at other departments rather than taking ownership. How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [Our weekly segue during the Level 10 Meeting consistently runs fifteen minutes late because my leadership team uses it to share long-winded personal life updates. How do I rein in the segue without killing team culture?](/qa/rein-in-level-10-meeting-segue)