When a weekly Scorecard measurable stays red for four to six consecutive weeks despite weekly IDS processing in the Level 10 Meeting, at what point does it graduate from a weekly operational issue into a quarterly Rock or a people issue?

Question

Tyler Smith · Accepted Answer

If a Scorecard measurable is red for two weeks, it is a normal operational variance. If it is red for three weeks, you IDS it to identify root causes. But if a measurable stays red for four to six consecutive weeks, your Level 10 Meeting process is breaking down. You are treating a systemic breakdown as a minor weekly glitch.

A metric stuck in red for over a month always falls into one of three distinct categories:
- The target is disconnected from reality: Your capacity or market conditions changed, but leadership refused to adjust the goal. Re-examine the math against current resources.
- The issue requires dedicated execution capacity: The root cause cannot be solved during a weekly meeting because it demands 20 to 50 hours of process redesign, software implementation, or training. At the next Quarterly Planning session, turn this fix into a company or departmental Rock with a dedicated owner.
- It is a people issue: The person in the seat does not Get it, Want it, or have the Capacity to do it (GWC). They are either hiding the truth, lacking the skill to execute the work, or overwhelmed by poor seat design on your Accountability Chart.

Do not allow a red metric to become background wallpaper on your Scorecard. If a metric hits week four in the red, the Integrator must force a definitive diagnosis. Either create a Rock to rebuild the process, evaluate the seat holder against GWC, or admit the target is wrong. Leaving it red without resolution destroys accountability across the team.