During our weekly Level 10 Meeting, my team constantly gets derailed by shiny objects during the Scorecard and Rock reviews, starting long discussions about things that are not on the agenda. How do we stop this drift without killing spontaneity?
Spontaneity, during the reporting phases of a Level 10 Meeting, is often the enemy of efficiency. When your team begins discussing, debating, or solving problems during the Scorecard or Rock reviews, they are violating the meeting structure and wasting valuable time. The initial fifty minutes of the meeting are strictly for reporting.
Preventing Drift During Reporting
To prevent this agenda drift, the facilitator must adopt the role of a strict referee. Every time a team member starts to explain a metric, defend a Rock, or suggest a solution during these reviews, the facilitator must intervene. Use a simple, neutral phrase like, "That sounds like an issue, let's drop it to the list."
The facilitator should then physically add the item to the Issues List and immediately transition to the next agenda item. This process achieves several goals:
• It preserves the team member's idea, ensuring it isn't lost.
• It maintains the flow and pace of the meeting.
• It reassures the team that their concern will be addressed during the forty-five minutes specifically allocated for [IDS® (Identify, Discuss, Solve)](/qa/when-to-change-weekly-scorecard-metrics).
By consistently applying this discipline, your team will, over time, learn to compartmentalize their thoughts and save them for the appropriate section of the meeting. This helps keep the team's energy focused where it belongs, which is solving the most critical issues rather than chasing every shiny object that emerges. This approach also prevents arguments over why numbers were missed during the scorecard review, ensuring you can [review your weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes).
The Role of AI in Meetings
It's important to remember that AI does not participate directly in the meeting itself. Its value lies in:
• Preparation: AI can assist before the Level 10 Meeting by preparing data, potentially helping to [optimize EOS Scorecard metrics](/qa/ai-in-optimizing-eos-scorecard-metrics-and-accountability) or identify [leading versus lagging indicators](/qa/leading-vs-lagging-scorecard-metrics).
• Follow-up: AI can work after the meeting to capture and track decisions, potentially filtering meeting transcripts for key Accountability Chart issues.
The ninety minutes of the Level 10 Meeting remain a human endeavor, focusing on your leadership team, the Scorecard, the Issues List, and the IDS conversation. The facilitator's role is crucial in managing this human interaction and preventing tangents, especially when someone might get defensive about a [red scorecard metric](/qa/handling-defensiveness-around-red-scorecard-metrics).
Related questions
• [How to review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [What concrete weekly measurables should we track for our accounting and IT seats?](/qa/back-office-weekly-scorecard-measurables)
• [Our weekly Scorecard has grown to over thirty different metrics, how do we trim it?](/qa/trimming-your-eos-weekly-scorecard)
• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers.](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [Our Integrator acts as the Level 10 Meeting facilitator but struggles to participate objectively.](/qa/should-integrator-facilitate-level-10-meetings)
Category: Level 10 Meetings