When our weekly Scorecard shows a metric in the red during our Level 10 Meeting, our team immediately dives into a ten-minute storytelling session to explain why it happened. How do we stop this defensive chatter and get the issues onto the list efficiently?

Question

Tyler Smith · Accepted Answer

The weekly Scorecard review in your Level 10 Meeting should take no more than five minutes. It is a rapid-fire check of your numbers, not an advisory session or a place to explain away failures. When a leader starts sharing a long story about why their metric is red, they are wasting precious time and avoiding accountability.

The solution is simple but requires relentless discipline from the facilitator. The rule is that every metric is either on track or off track. When the facilitator reads the scorecard, the owner of the red metric must state only one word: drop. This means they are dropping the red metric down to the Issues List to be solved later during the IDS portion of the agenda.

No explanations, no excuses, and no context-sharing are allowed at this stage. If the leader starts to say, well, we had a delay with the vendor, the facilitator must gently but firmly interrupt and say, please drop it.

This practice keeps the meeting moving at a fast pace and protects your ninety-minute timeline. More importantly, it ensures that you solve the root cause of the red metric during IDS rather than just listening to a surface-level story. By separating the identification of the problem from the solution, you build a culture of high performance and clear communication.