tyler-smith.com · Questions & Answers

When a metric on our weekly Scorecard goes red, should we drop it down to the Issues List immediately on week one, or wait for a two-week trend before problem-solving it in the Level 10 Meeting?

Drop it down immediately on week one.

The five-minute Scorecard review in your Level 10 Meeting is built for rapid detection, not debate. When an owner reads their number and it is below the weekly target, they simply say, Off track, drop it to the list. You do not explain it, you do not defend it, and you do not wait to see if it fixes itself next week.

Dropping a red metric to the Issues List does not mean you are obligated to solve it that morning. It simply captures the variance on paper. When you get to the IDS portion of the meeting, the leadership team prioritizes the top three issues for the company.

If the missed metric was caused by a known one-time anomaly, such as a holiday closure or a software migration, the team might decide not to prioritize it for discussion. That is fine. But the discipline of putting every red number on the list keeps the team honest and eliminates the temptation to sweep bad data under the rug.

Waiting two or three weeks to flag a red number guarantees you will lag reality by a month. By the time a metric is red for three weeks in a row, a minor operational hiccup has hardened into a systemic failure that threatens quarterly Rocks and revenue targets.

Keep the barrier to logging an issue at zero. Flag it on week one, prioritize ruthlessly in IDS, and treat red numbers as data rather than personal failure.

Category: Scorecards & Data

← All questions