tyler-smith.com · Questions & Answers

In our first two months running the weekly Scorecard, several numbers miss their goals every week. How do we keep the team from constantly changing measurables instead of letting the data mature?

High-performing leaders despise seeing red on a dashboard. When an initial Scorecard measurable misses its target week after week, the team's natural instinct is to renegotiate the metric, lower the goal, or invent a new calculation that looks greener. You must resist this urge.

Changing Scorecard measurables every three weeks prevents you from establishing an accurate historical baseline. A red number does not automatically mean the metric is incorrect; it usually means your activity is insufficient, your process is broken, or your capacity is bottlenecked. The red box is simply doing its job by exposing an operational vulnerability before it shows up on your monthly income statement.

Commit to leaving your Scorecard metrics untouched for a minimum of eight to twelve weeks, unless a measurable is mathematically flawed or completely impossible to track. If a number is off-track, drop it to the Issues List during the Level 10 Meeting and use IDS to examine root causes:

- Is the activity volume simply too low?
- Is the seat owner lacking proper tools or training?
- Is the target unrealistic based on current team capacity?

Solve the operational breakdown behind the number instead of moving the goalposts. Once you have three full months of continuous, unvarnished weekly data, you can intelligently adjust goals based on true operating realities rather than emotional discomfort.

Category: EOS Implementation

← All questions