During our weekly Level 10 Meeting, our Scorecard review repeatedly exceeds five minutes because leaders start explaining red numbers or debating target calculations. What strict operational protocol stops premature problem-solving during this agenda item?

Question

Tyler Smith · Accepted Answer

The five-minute Scorecard review fails the moment your Integrator allows storytelling. A Level 10 Meeting is engineered for strict discipline: report the numbers, identify off-track items, and push all discussion down to the Issues Solving Track.

When a leader begins explaining why their metric is off-track, the Integrator must immediately cut them off. The phrase to use is: Drop it down to IDS. The Scorecard agenda item is strictly for reporting data, not diagnosing performance.

Implement these three rules to keep your Scorecard review under five minutes:

- Absolute silence except for the owner: Each leader reads their measurable name, their weekly target, and their actual number. If a leader owns four metrics, they speak four sentences.
- Binary evaluation: A number is either on track or off track. There is no almost or context allowed. If the target is twenty and the actual is nineteen, it is off track.
- Direct drop to the Issues List: If a number is off track, the Integrator asks the metric owner one question: Do you want to drop this to the Issues List, or do you have it under control? If dropped, it becomes an issue for IDS later in the meeting. Zero debate occurs in the moment.

Treating the Scorecard review as a data dashboard rather than a conversation preserves your meeting energy for root-cause problem solving during the sixty minutes reserved for IDS.