tyler-smith.com · Questions & Answers

Our weekly numbers fluctuate slightly from week to week, causing our Scorecard to oscillate between red and green on normal operational variance. Should our weekly Scorecard targets be a strict single number, or should we use acceptable operating ranges to keep our team focused only on meaningful breakdowns?

Every business experiences a baseline level of operational noise. When a target is set as a rigid single number, such as exactly 20 sales conversations per week, a team that hits 19 registers a red number, triggering unnecessary anxiety and wasting valuable Level 10 Meeting time on standard statistical variance.

The solution is establishing clear threshold bands or minimum acceptable floors for each measurable on your Scorecard.

Define the goal as a clear operational standard, but establish the red trigger based on a functional breakdown rather than minor noise. For instance, if your optimal target is 20 completed calls, your acceptable operational band might be 18 to 22. Any result within that window is considered green. Only when the number drops below 18 does it register as off-track and drop to the Issues List.

There are two essential rules when applying target bands:

First, do not widen the band to hide poor performance. The minimum floor must represent the true breaking point below which your quarterly Rocks or revenue targets are placed at genuine risk. If hitting the lower boundary consistently causes downstream operational failures, your band is too forgiving.

Second, track multi-week trends. A metric that hovers at the absolute bottom edge of an acceptable range for three consecutive weeks is sending a warning sign. Even if the number technically registers green each week, the Integrator should drop the multi-week trend down to the Issues List for IDS before the breakdown turns completely red.

Category: Scorecards & Data

← All questions