When a metric on our weekly Scorecard drops to red, our Level 10 Meeting devolves into a defensive justification session instead of productive problem solving. How do we change how we address underperforming numbers?

Question

Tyler Smith · Accepted Answer

If your team is defending red numbers during the Scorecard review, you are violating the core rules of the Level 10 Meeting. The Scorecard review is a diagnostic check, not a trial.

To stop this behavior, you must enforce a strict response protocol. When a metric is read and it is below the target, the owner has only two options. They can say, On track, or they can say, Off track, drop it to IDS.

No explanations, no context, and no excuses are permitted during the first portion of the meeting. If a leader starts explaining why the number is red, the Integrator must immediately cut them off and say, Let us drop it to IDS.

During the IDS portion of the meeting, the mindset must shift from blame to problem-solving. The team must work together to identify the structural cause of the miss. Is the target unrealistic? Is there a training bottleneck? Or did an external event disrupt the workflow?

By treating the red metric as an objective business issue rather than a personal failure, you remove the fear that drives defensiveness. Your Scorecard is a tool for early warning, not a weapon for micromanagement. When your team trusts that the Level 10 Meeting is a safe space to solve operational issues, they will stop hiding from their numbers.