In our Level 10 Meeting™, when a scorecard metric goes red, the person accountable for that seat gets highly defensive and starts pointing fingers at other departments. How do we handle scorecard defensiveness to keep the focus on solving the issue?

Question

Tyler Smith · Accepted Answer

When a scorecard metric is red, it is an early warning sign that a process or system is failing, not a personal attack on the leader in that seat. Yet, many leaders react with immediate defensiveness and finger-pointing during the Level 10 Meeting. This defensive posture completely stalls problem-solving and violates the core trust of your team.

To eliminate this defensiveness, you must establish a clear distinction between being accountable for a number and being blamed for it. Under your company Charter, the leader owning the seat is accountable for reporting the metric and identifying if it is off-track, but they do not have to solve it alone.

When a number is red, the only acceptable response from the seat owner is: It is off-track, and I need to drop it to the Issues List. Or: It is off-track, but I have a plan to resolve it this week.

If they start explaining or blaming other departments, the facilitator must cut them off and drop the number to the Issues List for a proper IDS. During IDS, the team must focus entirely on the process, not the person. Ask: What in our system is broken that caused this number to drop? By keeping the focus on the system rather than personal failure, you remove the fear of being red. This builds a healthy, data-driven environment where numbers are used to solve problems, not to assign blame.