When a critical Scorecard measurable stays red for four or five consecutive weeks, our team drops it to the Issues List every single Level 10 Meeting, yet we rehash the same talking points without solving it. How do we break this cycle?

Question

Tyler Smith · Accepted Answer

A metric that stays red for more than three weeks is no longer a weekly operational glitch. It is a structural failure or an unrealistic goal. Dropping the exact same number to the Issues List every week to repeat the same complaints is meeting waste at its worst.

When a Scorecard measurable remains chronically off track, your IDS® must focus on the system, not the weekly number. During Identify, ask two questions: Is the goal realistic given our current capacity, and is the process behind this number broken?

Often, teams discover that the goal was set without accounting for market changes or resource constraints. If the goal is genuinely unachievable under current conditions, reset the measurable so it reflects reality.

If the goal is valid, then your previous solutions were superficial band-aids. Stop assigning seven-day To-Dos to fix a systemic problem. Instead, create a dedicated quarterly Rock to overhaul the underlying workflow, hire needed capacity, or rebuild the technology stack.

Finally, evaluate whether the seat owner truly has GWC™ for the role. If the process is sound and the goal is realistic, chronic underperformance points to an execution issue. Address the root cause once, create a definitive structural fix, and stop letting stale metrics clutter your weekly Issues List.