Our weekly Scorecard has several metrics that have been red for consecutive weeks, but the seat owners always have a plausible excuse and we fail to drop these numbers down to IDS®. How do we enforce consequences for repeating red metrics?

Question

Tyler Smith · Accepted Answer

When weekly scorecard metrics remain red for weeks without resolution, it is a sign that your team is treating the scorecard as a passive dashboard rather than an active accountability mechanism. A red metric that does not get dropped to IDS® is an accepted failure.

To fix this, the Integrator must enforce a strict rule: if a scorecard number is red for two consecutive weeks, it must automatically be placed on the issues list for the weekly Level 10 Meeting™. No exceptions, and no excuses allowed during the reporting section.

Once the red metric is in IDS®, the discussion must focus on the root cause of the miss, not just the weekly narrative. Ask whether the target is still realistic, whether the seat owner has the capacity to hit it, or if the process itself is broken.

If the seat owner keeps offering plausible excuses, you must address the underlying accountability. A metric owner is not just responsible for reporting the number; they are responsible for doing whatever it takes to hit the target.

If external factors or operational fires got in the way, that is the issue that needs to be solved. If the owner has hit a limit in their capability, then you must evaluate their GWC™ for that specific metric.

Never let a red number slide by with a promise that it will be better next week. If a number is red, the team must align on a concrete to-do for the coming week to actively course-correct.