During the Scorecard section of our Level 10 Meeting™, our leaders waste fifteen minutes defending their red numbers and explaining why the metric missed, rather than just stating the number and dropping it to the Issues List. How do we stop this defensive storytelling and keep the reporting block under five minutes?

Question

Tyler Smith · Accepted Answer

When your leaders spend fifteen minutes explaining and defending their red metrics during the Scorecard review, your Level 10 Meeting is losing its pulse. The reporting section of your agenda is designed for rapid-fire data delivery, not defensive storytelling or immediate troubleshooting.

To stop this waste of time, enforce a strict rule of stating only the numbers. When reviewing the Scorecard, the owner of each metric must only say two things: the actual number and whether it is red or green. For example, a leader should say: Leads were forty-two, which is red.

There should be absolutely no explanation of why the leads were low, no excuses about marketing campaigns, and no reassurance that next week will be better. If a metric is red, the facilitator must immediately ask: Drop it to the Issues List? If the team agrees, the metric is added to the bottom of the list with a single click, and the meeting immediately moves to the next number.

By keeping the reporting phase entirely transactional and reserving all discussion for IDS, you protect the momentum of your weekly pulse and ensure that red metrics are solved systematically rather than debated defensively.