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?

Question

Tyler Smith · Accepted Answer

The purpose of the Scorecard review in your weekly Level 10 Meeting is to identify issues, not to solve them on the spot. If you find your team spending fifteen minutes debating why a number is off track, your meeting is going off course. To correct this, implement a strict, binary rule during this portion of the agenda.

Streamlining Your Scorecard Review

When reviewing each metric:

• The owner simply reads the name of the measurable, the target, and the actual number.
• If the number is on track, move immediately to the next metric.
• If the number is off track (in the red), the owner states "drop it." This means the issue is immediately added to the [Issues List](/qa/enforcing-scorecard-hygiene-level-10-meeting) for later discussion.

Enforcing Discipline

Crucially, no explanations are allowed during the Scorecard review. No one should be permitted to explain away a missed target with reasons like "we missed it because the server went down on Tuesday." The entire leadership team must agree to self-regulate and gently call out anyone who starts to tell a story or offer justifications. This discipline is essential for keeping the review focused and swift.

By dropping the red numbers to the bottom of the agenda, you efficiently preserve your review time. You will then systematically tackle these problems during the IDS (Identify, Discuss, Solve) portion of the meeting, where you have dedicated time to [identify, discuss, and solve the root cause](/qa/improving-departmental-level-10-meetings-ids). This disciplined approach keeps your Scorecard review under five minutes and ensures your team spends its valuable time solving problems rather than just talking about them.

This strict process helps maintain focus, preventing the discussions from derailing the meeting. It's also critical for situations where a [manager gets defensive](/qa/handling-defensiveness-around-red-scorecard-metrics) about a missed metric.

Related questions

• [How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-scorecard-metrics)
• [How do we shift our focus from lagging results to weekly leading indicators?](/qa/leading-vs-lagging-scorecard-metrics)
• [When is it appropriate to change a scorecard number, and how do we do it without losing historical consistency?](/qa/when-to-change-weekly-scorecard-metrics)
• [How do we break down massive lagging deliverables into weekly leading indicators that actually tell us if a project is on track?](/qa/weekly-leading-indicators-for-long-term-projects)
• [How do we enforce better Scorecard hygiene?](/qa/enforcing-scorecard-hygiene-level-10-meeting)