The first twenty-five minutes of our Level 10 Meeting consistently drags out to forty-five minutes or more because our department leaders use their Scorecard and Rock updates to justify numbers and give status reports. How do we stop the reporting bloat and protect our sixty minutes for IDS?

Question

Tyler Smith · Accepted Answer

The first twenty-five minutes of your Level 10 Meeting are strictly designed for reporting, not for problem-solving or status defense. When leaders give long-winded explanations about why a metric missed or why a Rock is yellow, they are stealing time from IDS and hiding from accountability.

Enforce binary reporting across the entire check-in sequence:
- On the Scorecard, a number is either on track or off track. There is no third option.
- On Rocks, a priority is either on track or off track.
- On To-Dos, an action item is either done or not done.

If a Scorecard metric misses its target, the seat owner says two words: "Off track." The facilitator asks one question: "Do you want to drop that to the Issues List?" The owner says yes or no. That entire interaction must take less than five seconds. No background stories, no market excuses, no defensive narratives.

The exact same discipline applies to Rock review. Leaders must never explain what they did this week. They simply state "On track" or "Off track." If it is off track, drop it to the Issues List.

Moving every explanation to the Issues List forces the team to decide whether the problem is significant enough to prioritize during IDS. This stops individual leaders from monopolizing the meeting with status reports.