Our Level 10 Meeting™ regularly drags on past the ninety minute mark and turns into a frustrating, circular debate. How do we keep it tight, punchy, and strictly on time?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting™ that consistently runs over ninety minutes typically indicates a failure in one key area: reporting instead of solving, or solving the wrong problems. To bring your meetings back into control, you must enforce strict discipline on the agenda.

The First 25 Minutes: Rapid-Fire Reporting

The initial twenty-five minutes of your meeting must be a swift review of key metrics and updates. This section is strictly for reporting; no discussion is allowed.

• Scorecard review: Quickly go through your [weekly scorecard](/qa/how-to-review-scorecard-under-five-minutes) numbers. If a metric is off track, simply state it and move on.
• Rock progress: Report on the status of your Rocks. If a Rock is behind, acknowledge it and move forward.
• Customer/Employee Headlines: Share brief, impactful news items.
• To-do list: Review completion of previous to-dos.

If an item is off track or requires discussion, it should be immediately added to the Issues List for later. This dedicated reporting phase ensures that the team is informed without getting sidetracked.

The Core 60 Minutes: IDS® (Identify, Discuss, Solve)

After the rapid-fire reporting, you'll have a solid sixty minutes dedicated to IDS®, where the real work happens. The most common pitfall here is spending too much time discussing low-priority issues.

To maximize this crucial time:

1. Prioritize Issues: Before diving in, collectively prioritize the issues on your list. Focus on the top three most critical issues facing the business first. This prevents getting bogged down on less urgent matters, a common challenge many teams face with [trimming your EOS weekly Scorecard](/qa/trimming-your-eos-weekly-scorecard).
2. State the Issue Concisely: When processing an issue, demand conciseness. Team members should state the issue in one sentence, avoiding long, rambling stories.
3. Identify the Root Cause: Once the issue is clearly stated, guide the discussion to identify its root cause. This is where the team needs to dig deep and understand why the problem exists, not just what the problem is.
4. Solve and Create Action Items: As soon as the root cause is identified, pivot immediately to solving the issue and creating clear, actionable to-dos. These actions should be assigned to specific individuals with due dates. For teams struggling with blame, leveraging the [Accountability Chart to stop blame](/qa/using-accountability-chart-to-stop-blame-in-ids) can be highly effective.

The Hard Stop

Always maintain a hard stop at ninety minutes. If issues remain unresolved when time runs out, they stay on the Issues List for the next meeting. This discipline trains your team to be concise, focused, and efficient, ensuring that the meeting delivers value without overrunning its scheduled time. It also forces the team to differentiate between a temporary predicament and a [strategic problem](/qa/competitor-ai-threats-thinking-time) that truly requires extensive debate.

Related questions

• [How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [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)
• [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)
• [How do we trim the Scorecard down to the numbers that actually matter?](/qa/trimming-your-eos-weekly-scorecard)