One of the measurables on our leadership Scorecard has missed its goal for six consecutive weeks, but the seat owner just shrugs and drops it to the Issues List without changing anything. How do we break the pattern of chronic red numbers?

Question

Tyler Smith · Accepted Answer

A measurable that stays red for six consecutive weeks is no longer a Scorecard issue; it is an accountability failure. When a leadership team tolerates chronic misses, red numbers become normalized and the Scorecard loses its power as an early warning system.

The rule of the EOS Scorecard is straightforward: whenever an activity metric misses its weekly goal, it drops down to the Issues List. However, dropping an item to the list is not an absolution of responsibility. It is a demand for corrective action.

To break this pattern, handle the chronically missed number in your next IDS session with strict accountability:

- Challenge the target itself. Ask the seat owner whether the goal is realistic. If the target was set incorrectly, recalculate it based on actual capacity and reset the standard. But do not lower the bar simply to make someone feel comfortable.

- Require root-cause analysis, not explanations. If the goal is realistic, the seat owner must identify the exact breakdown in activity. Are they failing to execute the required inputs, or is the underlying process broken?

- Assign binary, short-term corrective To-Dos. The seat owner must walk away from the Level 10 Meeting with specific, seven-day action items designed to alter the outcome, not just a vague commitment to try harder.

If the measurable misses for another two weeks after running root-cause IDS, stop treating it as a technical problem. You are dealing with an execution breakdown in that seat. Use GWC to evaluate whether the leader genuinely has the capacity and willingness to own that measurable.