On our weekly Scorecard, we have several metrics that have been red for a month, and the team member responsible always has a plausible explanation for why. How do we transition from accepting excuses to holding them accountable for changing the trend line?

Question

Tyler Smith · Accepted Answer

Accepting plausible explanations for red metrics week after week is a slow death for operational accountability. A weekly Scorecard is not a tool for defense; it is an early warning system designed to trigger action. If a number is consistently red, the explanation does not solve the problem.

To break this pattern, you must separate the person from the metric during your Level 10 Meeting™. When a number is red, it is an operational issue, not a personal trial. Drop the metric to the Issues List and use IDS® to analyze why the system is failing to produce the desired result.

Ask whether the target is realistic, whether the process is being followed, or if the seat holder has the necessary resources and GWC™ capacity to hit the number. If the system is sound but the performance is lacking, the owner of the metric must bring a concrete action plan to the next meeting to get the trend line moving in the right direction.

Shift the conversation from why it happened to what we are doing to fix it. This changes the dynamic from a weekly defensive explanation to proactive problem-solving. True accountability means the owner of the metric owns the solution, not just the excuse.