When a leadership team member reports a Rock as off track in a weekly Level 10 Meeting, how should the team address it without turning the meeting into a lengthy status update?

Question

Tyler Smith · Accepted Answer

The quarterly Rock review inside a Level 10 Meeting is an operational integrity check, not a project debrief. You have roughly five minutes to review the entire list of Rocks. The moment a leader begins explaining why their Rock is off track, meeting momentum dies and the agenda is hijacked.

Enforce strict meeting hygiene by following a precise protocol:

- Binary reporting only. When a leader's name is called, they are permitted to say exactly two words: on track or off track. No background story, no timeline defense, no context.
- Immediate routing to the Issues List. If the Rock is off track, the Integrator immediately asks: do we need to drop this to the Issues List? If yes, it is logged with a clean three-word issue title, and the meeting moves instantly to the next Rock.
- Solve it during IDS, never during the review. When the meeting transitions to the IDS portion, the team prioritizes the top three issues. If the stalled Rock is critical to the business, it gets selected, identified at its root cause, and solved systematically.

Allowing leaders to defend their performance during the reporting phase creates an environment of excuse-making. Keep reporting binary, protect the pacing of the Level 10 Meeting, and do the heavy lifting inside IDS.