Our leadership team wastes twenty minutes in our Level 10 Meeting debating whether a number that is two percent below target should be marked red. How do we set clear upper and lower thresholds for our Scorecard?

Question

Tyler Smith · Accepted Answer

Debating whether a missed measurable is close enough to count as green destroys the pace of your Level 10 Meeting and rationalizes operational underperformance. In EOS, the Scorecard must provide an absolute, binary pulse. A number is either on track or it is off track. There is no such thing as light red or mostly green.

To end subjective arguments, the seat owner and the Integrator must establish strict numerical goal rules during your quarterly planning session. You have two clear ways to structure this:

- Exact Floor Targets: Set a hard minimum number. If the goal is twenty qualified appointments per week and the team delivers nineteen, the box is red. Period. No debate, no justification.
- Defined Tolerance Bands: If a metric naturally fluctuates week to week, agree on a pre-determined operating band, such as eighteen to twenty-two. Anything inside that band is marked green. The moment the number hits seventeen, it turns red automatically.

The critical operational discipline is understanding why a number turns red. Red does not mean a team member is in trouble; it simply means the system requires attention. A red number simply signals that an Issue should be dropped down to the Issues List so the team can IDS the root cause.

When you remove the emotional stigma of red numbers, your leadership team will stop fighting over two percent variances and start focusing their energy on solving operational roadblocks.