Our leadership team constantly tries to skip the reporting sections of our Level 10 Meeting to jump straight into IDS, arguing that we already know the numbers. How do I stop this agenda drift?

Question

Tyler Smith · Accepted Answer

Skipping the reporting sections of your Level 10 Meeting is a critical mistake that weakens team alignment and prevents effective problem-solving. When leaders argue they already know the numbers, they are missing the entire point of the meeting pulse.

The Purpose of Reporting

The reporting portion of the Level 10 Meeting is not merely a status update; it serves as a shared diagnostic check for the entire team. The first twenty minutes of the agenda, which includes the Scorecard, Rock Review, and Customer/Employee Headlines, is specifically designed to:

• Build a collective picture of the company's current state.
• Force everyone to look at the business holistically.
• Provide a common understanding of objective data.

If you skip these critical steps, you are relying on siloed information and individual assumptions, which can lead to solving the wrong problems later in the meeting. For example, if your [weekly scorecard](/qa/how-to-review-scorecard-under-five-minutes) isn't reviewed efficiently, you miss vital collective insights.

Stopping Agenda Drift

To effectively stop agenda drift and ensure the reporting sections serve their intended purpose, the facilitator must strictly enforce the meeting rules:

• Rapid, High-Level Review: Each section must be a quick overview.
• No Discussion Allowed: This is crucial. Prevent any attempts to explain, defend, or analyze.
• Clear Status Updates: For Scorecard numbers, state "on track" or "off track." For Rocks, indicate "on track" or "off track." For headlines, provide a brief, one-sentence summary.
• Drop it to IDS: If a number is red, a Rock is off track, or a headline reveals a problem, the facilitator must immediately instruct the team to drop it to the Issues List. This ensures that valuable discussion time is saved for the IDS section.

By keeping the reporting clean, fast, and disciplined, you can complete the entire review in twenty minutes. This leaves a full fifty-five minutes for high-value problem solving during IDS, ensuring you tackle the most important issues based on collective data, not assumptions. Failing to look at the objective data first often results in [blame games](/qa/using-accountability-chart-to-stop-blame-in-ids) and addressing symptoms rather than root causes.

Remember, the goal is to quickly surface issues, not solve them during the reporting phase. An efficient [review of scorecard metrics](/qa/trimming-your-eos-weekly-scorecard) sets the stage for productive problem-solving.

AI's Role

While the Level 10 Meeting itself remains a human-centric process, AI can play a supportive role outside of the meeting. AI never sits in the room during the ninety minutes. Instead, it works before the Level 10 Meeting to prep data and after the meeting to capture and track what was decided. This allows the leadership team to focus on the Scorecard, the Issues List, and the IDS conversation.

Related questions

• [We spend half of our Level 10 Meeting arguing over why numbers were missed instead of just reading the scorecard. How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [My leadership team is struggling to agree on what actually deserves a spot on our high level scorecard. How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-scorecard-metrics)
• [One of our key managers gets defensive and starts explaining away the context every time their scorecard metric drops into the red. How do we handle this in the Level 10 Meeting?](/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)