One of our key managers gets defensive and starts explaining away the context every time their scorecard metric drops into the red. How do we handle this in the Level 10 Meeting?

Question

Tyler Smith · Accepted Answer

Defensiveness around a red scorecard metric often comes from a misunderstanding of its purpose. If a manager perceives a red number as a personal failure or a threat to their job, they'll naturally make excuses. You need to reframe your team's perspective on these [scorecard metrics](/qa/how-to-choose-five-fifteen-scorecard-metrics).

The Purpose of a Red Number

In an EOS® (Entrepreneurial Operating System) culture, a red number isn't a failure. It's an early warning light on your business's dashboard, signaling that attention is needed. Red numbers are opportunities to proactively [solve problems](/qa/using-accountability-chart-to-stop-blame-in-ids) before they escalate into crises.

Handling Defensiveness in the Level 10 Meeting

During the Level 10 Meeting™, implement a strict rule: no explanations during the scorecard review. This keeps the meeting focused and efficient. [Reviewing your scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes) is crucial.

• If a manager starts explaining a red number, gently interrupt them.
• State clearly, "Let's drop it to the Issues List and IDS it later." This immediately signals that while the issue is important, the discussion has a designated time and place.

IDS: Focusing on the System, Not the Person

When you reach the Identify, Discuss, Solve (IDS) portion of your meeting, shift the focus entirely to the system, not the individual manager. This approach naturally reduces defensiveness over time.

Ask questions that redirect the conversation towards systemic analysis:

• "Is the target still realistic?"
• "Do we have the right resource allocation?"
• "Is there a bottleneck in the process?"

This line of questioning encourages problem-solving and reinforces that the red number indicates a system-level challenge, not personal incompetence. For complex or [long-term projects](/qa/weekly-leading-indicators-for-long-term-projects), this systemic view is even more critical.

The Role of AI

While AI can prepare data before the [Level 10 Meeting](/qa/using-ai-tools-in-level-10-meetings) and track decisions afterward, the 90 minutes of the meeting itself remain a human-centric interaction. Your leadership team, the scorecard, the Issues List, and the IDS conversation are all designed to foster human connection and collaborative problem-solving.

Related questions

• [How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers at other departments rather than taking ownership. How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [How do we choose five to fifteen scorecard metrics?](/qa/how-to-choose-five-five-scorecard-metrics)
• [Our scorecard is packed with metrics like closed sales and completed projects, but we still feel reactive. How do we shift our focus from lagging results to weekly leading indicators?](/qa/leading-vs-lagging-scorecard-metrics)
• [For businesses that run complex, long-term engineering or construction projects, how do we break down massive lagging deliverables into weekly leading indicators that actually tell us if a project is on track?](/qa/weekly-leading-indicators-for-long-term-projects)