Why do our leadership team members get defensive during the weekly Level 10 Meeting when reviewing Rocks, and how do we keep the reporting to a simple on-track or off-track status so projects actually finish?

Question

Tyler Smith · Accepted Answer

The weekly Rock review in a Level 10 Meeting should take less than five minutes. It is a status check, not an explanation. When leaders start explaining why a Rock is delayed, defending their progress, or detailing their weekly activities, they are masking execution risk with narrative. That behavior directly causes Rocks to fail at day ninety.

To fix this, the Integrator must strictly enforce a binary response. When your name is called for a Rock, you say only two words: on track or off track. There is no middle ground, no almost on track, and no story about a vendor delay.

If a Rock is on track, the meeting immediately moves to the next item. If a Rock is off track, it drops straight to the Issues List. It does not get discussed right then. Dropping an off-track Rock to the bottom of the list is not a disciplinary action. It simply alerts the team that the owner needs help clearing a barrier during IDS.

When you eliminate storytelling during the Rock review, you remove the psychological need for defensiveness. The owner knows that being off track simply means the team will swarm the problem later in the meeting. This weekly visibility prevents a struggling Rock from quietly dying in week six and guarantees that friction is resolved before the quarter ends.