Our leadership team consistently logs red numbers on the Scorecard week after week, but we brush past them without dropping them to the Issues List. How do we break the habit of normalizing red metrics in our Level 10 Meeting?

Question

Tyler Smith · Accepted Answer

When a leadership team looks at a red number on their Scorecard and simply moves on to the next row, they destroy the accountability culture of the business. Normalizing misses teaches the organization that targets are theoretical suggestions rather than hard operational commitments.

In a true EOS Level 10 Meeting, there are only two acceptable verbal responses when a leader reads their Scorecard number:

- On track.
- Off track, drop it down.

The Scorecard review must take no more than five minutes. No explanations, no storytelling, and no defensive justifications are allowed during the review. If the metric missed its weekly target, the owner must say two words: off track. The Integrator or meeting scribe immediately writes the issue on the Issues List.

The only exception is if the owner has a concrete, immediate fix already executing that will return the number to green next week without leadership involvement. In that case, the owner states the plan in ten seconds. If the number misses a second consecutive week, it drops down automatically.

The purpose of dropping a red metric to the Issues List is not to punish the seat owner. It is to give the leadership team the opportunity to IDS (Identify, Discuss, and Solve) the underlying operational breakdown. When your team realizes that dropping an issue leads to collaborative problem solving rather than an interrogation, the fear evaporates and data discipline returns.