Our weekly Scorecard consistently shows red targets in certain departments, but the responsible department heads always have logical excuses for why they missed their numbers. How do we use our weekly Scorecard to cut through the stories and drive true accountability without damaging team morale?

Question

Tyler Smith · Accepted Answer

When your Level 10 Meeting becomes a weekly storytelling session about why numbers are red, your Scorecard has lost its teeth. Department heads will always have logical explanations for missed targets. Your job as a leader is to cut through the stories and focus on root causes.

First, establish that a red number is not a moral failure. It is simply a signal that a process is broken or capacity is stretched. Eliminate the blame game.

Second, enforce a strict rule. During the Scorecard review, no one is allowed to explain why their number is red. The only acceptable response is to say drop it down to the Issues list. This keeps the review phase fast and objective.

Third, when you reach the IDS portion of the meeting, solve the issue systematically. Do not accept excuses like we were too busy. Instead, dig into the actual workflow. Is the target unrealistic? Is the seat owner struggling to GWC their seat? Is there a bottleneck in their documented process?

By separating the identification of red numbers from the solving of the issues, you remove the defensive posture. This builds a culture where your team respects the data, owns their results, and collaborates to fix the problems.