Our leadership team gets defensive whenever their weekly Scorecard numbers are red, leading to long explanations instead of solving the issue. How do we run a clean IDS session in our Level 10 Meeting to address a chronically red metric without making the seat holder feel personally attacked?

Question

Tyler Smith · Accepted Answer

Defensiveness kills accountability. When a metric is chronically red, your leadership team must understand that the number is not a judgment on their character or their GWC™. The red number is simply a data point indicating that a process is broken or capacity is stretched.

To run a clean IDS® session on a red metric, you must separate the person from the number. Start by identifying the root cause of the miss. The owner of the metric must lead this discussion by stating the facts, not excuses. The question is never, "Why did you fail?" The question must be, "What is preventing this process from hitting its target?"

Often, a red metric is a symptom of a larger bottleneck. For example, if the marketing seat is missing their weekly leads target, IDS® might reveal that the outsourced ad agency is underperforming, or that the website traffic has dropped due to a technical error. By focusing on the system rather than the person, the team can collaborate to find a solution.

The Integrator must keep the conversation objective and solution-oriented. If the discussion devolves into personal blame or defensiveness, pause and bring the team back to the data. Remember, you are building a business that runs on data, not politics. Once the root cause is identified, assign a clear action item to resolve it, or create a new Rock if it requires a major quarterly initiative. This disciplined approach removes the drama and keeps your team focused on execution.