During the Scorecard and Rock review, our leaders constantly offer long-winded defenses and start problem-solving off-track items before we finish reporting. How do we enforce pure reporting discipline during the first twenty minutes?

Question

Tyler Smith · Accepted Answer

Jumping into problem-solving during reporting is the single most common reason Level 10 Meetings run out of time for IDS. A leader sees a red metric or an off-track Rock, feels defensive, and immediately launches into a five-minute narrative explaining external market headwinds, vendor delays, or client excuses. Other leaders jump in, and suddenly twenty minutes of IDS time has been burned during what should have been a sixty-second status check.

Reporting must remain ruthlessly transactional. The purpose of the Scorecard and Rock review is strictly to identify what is off track, not to explain why it is off track or how to fix it.

The Integrator must establish absolute verbal boundaries. When reviewing the Scorecard, the metric owner is allowed to state two words only: on track or off track. If a number is off track, the facilitator asks one question: Drop it down? If the owner or any peer says yes, the scribe adds the metric name directly to the Issues List. There is zero room for backstory.

The same rule applies to Rocks. The owner says on track or off track. No narratives about how close they are to finishing or why an internal dependency slowed them down. If it is off track, it drops straight to the Issues List.

If an executive starts to explain, the facilitator must immediately interrupt: John, stop. Drop it to the list. We will solve it in IDS. It feels abrupt at first, but it quickly trains the room that issues are not personal indictments. By keeping the reporting block under twenty-five minutes, you protect a full sixty minutes to dissect root causes and build permanent solutions during IDS.