During the Rock review section of our Level 10 Meeting, leaders whose Rocks are falling behind spend several minutes explaining why and pitching recovery plans instead of just stating the status. How do we enforce pure binary reporting?

Question

Tyler Smith · Accepted Answer

The Rock review portion of the Level 10 Meeting agenda is allocated exactly five minutes for a reason. Its purpose is purely diagnostic: to establish whether quarterly milestones are progressing on schedule or falling behind. It is not the time to explain failure, apologize for delays, or pitch operational recovery plans.

When a leader responds to their Rock with a narrative beginning with, Well, we were delayed because our developer left, they are introducing waste into the pulse. That narrative steals time from the rest of the agenda and tempts the entire leadership team into an unscheduled, premature problem-solving session.

The rule during Rock review is strictly binary. The Rock owner can only utter two phrases: On Track or Off Track. Nothing else is acceptable.

If a Rock is on track, the Integrator moves immediately to the next item. If a Rock is off track, the Integrator cuts off any incoming explanation instantly. The Integrator simply responds: Understood. Drop it to the Issues List.

Dropping an off-track Rock to the Issues List is not a punishment or a public shaming. It is the operational mechanism that allows the leadership team to support that leader during IDS. By parking the off-track Rock on the list, the team can prioritize it against all other operational issues. If it is a top priority, the room will dedicate fifteen or twenty minutes during IDS to identify root causes and assign corrective To-Dos. Enforce binary reporting and keep your pulse on schedule.