Our leadership team constantly debates what actually constitutes a red number on our weekly Scorecard, arguing that being five percent below target is basically green. How do we establish rigid Scorecard goals and tolerances so the team stops rationalizing missed targets during our Level 10 Meeting?

Question

Tyler Smith · Accepted Answer

The EOS Scorecard is binary. You either hit the weekly target or you missed it. There is no such thing as almost green, acceptable yellow, or passing with an asterisk. When you tolerate rationalizations for small misses, you introduce subjectivity into your culture and dilute accountability.

Teams debate targets when the purpose of the Scorecard is misunderstood. A red cell is not a personal failure, a punitive mark, or a reason to fire an employee. It is an objective flag indicating that an operational system is wavering. When a number is red, it simply means the leadership team needs to take notice. If it stays red for more than one or two consecutive weeks, the seat owner drops it down to the Issues List to IDS the root cause.

To establish clean boundaries, follow these rules:
- Set single-point weekly thresholds: If the target is twenty completed implementations, nineteen is red. Period.
- Ban mid-meeting target revisions: Never allow a leader to negotiate a target down during the Scorecard review because the week was hard.
- Re-evaluate targets only during Quarterly Planning: If a target is consistently unrealistic or uncalibrated, adjust it during your quarterly offsite, not during a weekly Level 10 Meeting.

When your team accepts that red simply means an issue needs attention rather than an attack on their capability, the debates stop and the problem-solving begins.