We have a few metrics on our leadership scorecard that are consistently red, but our team just skims past them during our Level 10 Meeting without actually addressing the root cause. How do we force accountability when red numbers are ignored?

Question

Tyler Smith · Accepted Answer

When a scorecard metric is consistently red and the team ignores it, your Level 10 Meeting has lost its traction. Skimming past red numbers is a sign of artificial harmony and a fear of conflict. A red number is not a personal failure. It is an objective flag indicating that a process is broken, capacity is strained, or the target is unrealistic. To force accountability, you must enforce the rules of the weekly meeting pulse. When reviewing the scorecard, if a number is red, the owner must drop it down to the Issues list. There is no explanation or defensiveness allowed during the scorecard review. You simply state the number, note that it is off-track, and drop it down. During the IDS portion of your meeting, the team must identify the root cause of the red metric. Is the target too high? Is the seat owner lacking GWC, meaning they do not get it, want it, or have the capacity to manage the work? Or is there an external bottleneck that requires cross-functional help to solve? By forcing the red number into your IDS process, you turn a potential source of personal frustration into an objective problem-solving exercise. This normalizes red numbers as opportunities for improvement rather than indictments of personal performance, keeping your team focused on finding solutions.