We have a beautiful weekly Scorecard with twelve key metrics, but when a number goes red, our team just moves on to the next line without actually addressing it. How do we force our leadership team to use our weekly Scorecard as the primary engine for our Level 10 Meeting IDS sessions?

Question

Tyler Smith · Accepted Answer

A common pitfall for leadership teams running on EOS is treating the weekly Scorecard as a passive report rather than an active diagnostic tool. If your team is letting red numbers slide by without discussion, you are missing the entire point of the weekly review.

The rule of the Level 10 Meeting is simple. Any Scorecard number that misses its target is dropped down to the Issues List automatically. No explanations, excuses, or stories are allowed during the initial Scorecard review.

To break the habit of ignoring red numbers, your Integrator must enforce this discipline ruthlessly. When a metric is red, the owner simply states that the number is red and the Integrator instructs the scribe to add it to the Issues List.

During the IDS portion of the meeting, your team will prioritize these issues. Here, you will dive deep to identify the root cause of the red metric, discuss potential solutions, and create a concrete To-Do to get the number back on track for the following week.

By forcing every red number through the IDS process, you create a culture of accountability where numbers are respected, and issues are actually solved rather than swept under the rug.