When a scorecard metric is red in our Level 10 Meeting™, the seat owner insists they have a plan and don't need to drop it down to the Issues List. How do we handle leaders who are defensive about red numbers and refuse to let the team IDS® them?

Question

Tyler Smith · Accepted Answer

Defensiveness around red scorecard metrics is a major obstacle to building a healthy leadership team. When a leader resists dropping a red number to the Issues List, they are usually treating the red mark as a personal failure rather than a business problem. In an EOS® environment, a red metric is not an accusation. It is simply an early warning indicator that a process or system needs attention.

The facilitator and the Integrator must address this defensiveness by reframing the purpose of the Issues List. Every red metric must be dropped to the list, no exceptions. The phrase, I have a plan, is not an acceptable reason to bypass the system. If the seat owner has a plan, that is excellent, but the rest of the leadership team needs to hear it, validate it, and support it.

By dropping the red metric to the Issues List, the team can IDS® it together. This gives the other leaders a chance to offer help, identify cross-departmental impacts, and ensure the plan is robust. Over time, this practice builds trust and normalizes healthy vulnerability. If a leader continues to resist this process, it indicates they are prioritizing their ego over the health of the company, which requires a direct, offline conversation about core values and their alignment with the Accountability Chart.