Our department heads keep asking for a yellow status on our weekly Scorecard for metrics that are within five percent of their goal, arguing that binary red or green is too harsh. Why does EOS reject yellow metrics, and how do we handle near misses?

Question

Tyler Smith · Accepted Answer

Yellow metrics are an escape hatch for accountability. The moment you introduce yellow into an EOS Scorecard, your leadership team stops discussing the hard realities of the business and begins debating whether a 6 percent miss qualifies as yellow or red.

A weekly Scorecard must be ruthlessly binary. It is either on track or off track. Red does not mean an employee is a failure, nor does it require punishment. Red simply means the measurable did not hit the agreed-upon target and requires five seconds of attention to determine whether it needs to drop to the Issues List.

When leaders argue that binary scoring is too harsh, they are usually confusing the Scorecard with an employee performance review. The Scorecard is an objective pulse of company health. If your airplane needs 1,000 feet of runway to clear an obstacle and has 980 feet, you do not call it yellow. You hit the obstacle.

Set realistic weekly targets. If a number consistently misses by one percent but the business operates smoothly, your target is likely calibrated incorrectly. Adjust the goal to reflect the true operational threshold. Once the target is set, enforce black-and-white scoring: green if the goal was met or exceeded, red if it was missed by any margin. Treat red as data, not drama.