Our team does not argue about the red numbers anymore, but the actual administrative mechanics of updating and reading the scorecard still eat up ten minutes of our Level 10 Meeting. How do we streamline the actual reading and logging process to hit that five-minute mark?

Question

Tyler Smith · Accepted Answer

To keep your scorecard review under five minutes, you must treat it like a silent, rapid-fire status report rather than a discussion. The problem often arises because people read every single number out loud, or they wait until the meeting starts to type in their data.

Streamlining the Scorecard Process

Follow these steps to streamline your scorecard review:

1. Establish a hard rule: All data must be entered by the designated owner at least one hour before the Level 10 Meeting™ starts.
2. Accountability for missing data: If the data is not in by the deadline, the number is red by default, and this becomes a separate accountability issue. For more on accountability, see [how to assess if an internal candidate is ready for the Integrator seat](/qa/promoting-internal-operations-manager-integrator).
3. Focus on red numbers: During the meeting, you only read the red numbers. Do not read the green ones. This helps you [trim the Scorecard down to the numbers that actually matter](/qa/trimming-your-eos-weekly-scorecard).
4. Concise reporting for red numbers: The person who owns the red metric states:
• The name of the measurable.
• The actual number.
• One of two phrases: "drop it" or "I have got it."

• If they say "drop it," the Integrator moves it to the [Issues List](/qa/using-accountability-chart-to-stop-blame-in-ids) to be solved during the IDS® portion of the meeting.
• If they say "I have got it," it means they have a clear plan to correct the trajectory this week and do not need team help.

5. No discussion or explanation: No context is given, no explanations are made, and no questions are asked by other team members. This prevents the meeting from becoming [boring progress updates](/qa/fixing-boring-eos-quarterly-sessions).

By moving directly from a red number to the decision to "drop it" or "I have got it," you can easily scan fifteen numbers in under two minutes. This leaves your valuable meeting time for actually solving the root issues later in the agenda, which is crucial for [reviewing your weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes).

Related questions

• [How do we handle a key department head who refuses to participate in offsite vulnerability or team-building exercises, claiming it is a waste of time?](/qa/handling-leader-resisting-offsite-vulnerability)
• [How do we shift our focus from lagging results to weekly leading indicators?](/qa/leading-vs-lagging-scorecard-metrics)
• [How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-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)
• [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)