Should our weekly Scorecard targets be single hard numbers or bounded ranges with minimum and maximum control limits to prevent overreacting to normal operational noise?

Question

Tyler Smith · Accepted Answer

Standard EOS practice requires a single goal for every Scorecard measurable, typically formatted as greater than or less than a specific target number. This binary rule keeps reporting brutally simple during the five-minute review: the number is either green or red. There is no negotiating in the meeting.

However, for high-volume operational metrics like inventory levels, daily bank balances, or billable hours, single numbers can cause leadership teams to chase statistical noise. In those operational seats, establishing control bands is practical, but the Scorecard itself must still present a binary target.

Format your target as a defined tolerance corridor. For example, rather than setting billable utilization at exactly eighty percent, define the target as between seventy-five and eighty-five percent. If the team hits seventy-six percent, the cell is green. If it drops to seventy-four percent or spikes to eighty-nine percent, the cell turns red.

Spiking above your upper limit is just as dangerous as falling below. Sustained utilization above eighty-five percent indicates impending team burnout, delayed client deliverables, and zero capacity for unplanned growth.

Do not allow ranges to soften accountability. The corridor must be tight, mathematically justified, and agreed upon by the leadership team. When a metric breaches either boundary, drop it immediately to the Issues List for IDS. Running on data means eliminating guesswork, not debating whether a three percent deviation matters.