Every time a Scorecard number turns red in our Level 10 Meeting, the owner of that metric reflexively starts defending why they missed or the team begins debating solutions, stretching our five-minute review to twenty. What exact meeting discipline cuts off debate instantly without shutting down healthy accountability?

Question

Tyler Smith · Accepted Answer

The purpose of the Scorecard agenda item in the Level 10 Meeting is reporting, not problem solving. When leaders start explaining, contextualizing, or defending a red number, they derail the meeting and destroy the five-minute cadence.

In EOS, you do not debate red numbers during the Scorecard review. The protocol is binary and clinical. The owner of the seat states one of two phrases: At Target, or Drop it Down. If the number is below the weekly goal, it drops directly to the Issues List.

To enforce this discipline, your Integrator must ruthlessly police three operational rules:
- Zero Narrative: No explanations, excuses, or background context are permitted during the first five minutes. The only acceptable response is the number itself and whether it is at target or needs to be dropped to the Issues List.
- Immediate Redirection: If an owner begins telling a story, the Integrator must cut in immediately and say: Drop it down. We will IDS it on the Issues List.
- Solve in Priority Order: Just because a Scorecard metric dropped to the list does not mean you discuss it first. During IDS, the leadership team ranks the top three issues for the company. If the missed metric is priority number one, you spend thirty minutes solving it at the root cause. If it is priority seven, you do not touch it until the bigger obstacles are cleared.

Separating reporting from solving protects the team from thirty minutes of superficial talking. Keep the review under five minutes by enforcing binary numbers, logging issues silently, and saving all debate for IDS.