Should our weekly Scorecard targets represent baseline minimum standards or aspirational stretch goals, and how do we prevent the team from treating red numbers as a personal failure?

Question

Tyler Smith · Accepted Answer

Scorecard targets must always represent the baseline operational standard required to achieve your annual budget and quarterly plan. They are never aspirational stretch targets. A stretch goal belongs in your strategic planning discussions or your quarterly Rocks, where the team takes on innovative projects with variable outcomes. The Scorecard is your operational baseline. It is the minimum pulse required to keep the enterprise solvent, orderly, and growing.

If your Scorecard targets are set as aspirational goals, half your board will be red every single week. When numbers are perpetually red through no operational negligence, two destructive behaviors emerge. First, the leadership team develops scorecard numbness, where red no longer triggers urgency because missing targets is normal. Second, team members become defensive, spending meeting time crafting excuses rather than reporting facts.

To remove personal shame around red numbers, teach the team that a red cell is simply an operational signal. In EOS, a red measurable is an early warning system designed to protect the seat owner, not punish them. It indicates that friction has entered the process. Dropping a red number to the Issues List to IDS is not an admission of incompetence. It is an objective request for the leadership team to help clear an obstacle before a small weekly variance turns into a catastrophic quarter.