tyler-smith.com · Questions & Answers

When our weekly Scorecard numbers miss target by a tiny margin, our team argues that the metric should be marked green because it was close enough. How do we eliminate the debate around near-miss numbers?

Eliminate the gray area completely. The Scorecard is strictly binary. A number is either at or above target, which is green, or it is below target, which is red. There is no yellow, no partial credit, and no negotiation.

When you allow team members to argue that a metric was close enough to count as green, you destroy the objective honesty of the Data Component. Close enough is an emotional rationalization that conceals underlying operational friction. A target of ten client demos means ten. Nine is red.

Leaders resist binary scoring because they treat red as a personal failure or an indictment of their work ethic. The Integrator must reframe what red actually means. Red is not a reprimand. Red is simply an objective signal that says: something in our operational process broke, stalled, or faced friction this week, and we need to look at it.

If nine demos out of ten represents acceptable performance, then your target was set incorrectly in the first place. Change the baseline target to nine if that truly satisfies your business model. But as long as the target is ten, missing by one requires dropping the metric to the Issues List. When your team realizes that red numbers trigger problem-solving rather than punishment, the defensiveness disappears and the data remains pure.

Category: Scorecards & Data

← All questions