Our leadership team sets ambitious quarterly Rocks, but individual owners repeatedly report roadblocks only in the final two weeks of the quarter when it is too late to recover. What weekly protocol ensures team accountability before Rocks go off track?

Question

Tyler Smith · Accepted Answer

Rocks fail in week eleven because leaders treat Rock ownership as a private project rather than a public weekly commitment. When an executive waits until the final stretch to admit a Rock is behind, the entire leadership team has failed its weekly oversight duty.

The weekly Level 10 Meeting is your primary defense mechanism. During the Rock Review, the owner must state only on track or off track. If an owner anticipates missing the final completion date by even twenty-four hours, that Rock is off track today. If a dependent department has not delivered a prerequisite, that Rock is off track today.

To prevent late surprises, implement three operational disciplines:

- Milestone breakdown: Within the first two weeks of the quarter, every Rock owner must outline three to four thirty-day milestones. If month one milestones are unmet, the Rock is officially marked off track.
- Zero tolerance for optimistic reporting: The Integrator must challenge optimistic on track assertions. If an executive claims a complex project is on track but has not completed foundational deliverables by week six, the Integrator pushes it to the Issues List for IDS.
- Immediate IDS intervention: When a Rock goes off track, the room does not shame the owner. The team attacks the roadblock during IDS to clear the path, reassign sub-tasks, or reallocate resources before the quarter is compromised.

A completed Rock is binary. By making weekly reporting objective and using the full power of the room to eliminate friction early, your completion rates will consistently cross the eighty percent pure EOS standard.