Our team panics when a Scorecard measurable turns red for a single week and immediately wastes thirty minutes in IDS trying to solve temporary noise. When should a red Scorecard number drop to the Issues List versus being monitored for a multi-week trend?

Question

Tyler Smith · Accepted Answer

The fundamental rule of an EOS Level 10 Meeting is simple: if a Scorecard measurable is off track, it drops down to the Issues List. Period. However, dropping a number down does not mean the team must automatically burn thirty minutes trying to fix a one-week anomaly during IDS.

Leadership teams must separate identifying an issue from prioritizing it. The Scorecard review exists to flag variances without emotional debate. Dropping every red cell down creates absolute transparency and eliminates subjective hiding. But once those numbers reach the Issues List, the leadership team must use discipline when selecting the top three issues to solve.

A single red number caused by a known, short-term disruption, such as a holiday week, a planned system migration, or an unexpected team illness, does not warrant immediate emergency surgery. The measurable owner simply identifies the variance and notes that it is expected to recover next week. If the issue is not selected in the top three during IDS, it sits or clears naturally.

The real trigger for deep operational triage is a multi-week pattern. If a measurable misses target two or three weeks in a row, or if the variance reveals an underlying process breakdown, the team must prioritize it in IDS. That is no longer operational noise; it is a systemic crack.

By sticking to the rule of always dropping red numbers down while staying selective about what you prioritize in IDS, you maintain total visibility without chasing weekly shadows.