Our leaders consistently argue during week ten that unexpected customer crises prevented them from finishing their quarterly Rocks. How do we structure Rock milestones during the 90-day cycle so they get across the finish line regardless of day-to-day firefighting?

Question

Tyler Smith · Accepted Answer

Rocks fail to finish because leaders treat them as a single monolithic project to tackle in the final three weeks of the quarter. When customer emergencies hit, the unfinished Rock gets pushed aside, and week thirteen arrives with zero results.

To ensure Rocks finish, every Rock owner must break their ninety-day priority into four distinct, measurable milestones during the quarterly planning session. These milestones must be scheduled for weeks three, six, nine, and twelve. If a Rock requires input or deliverables from another department, those dependencies must be agreed upon and written down as milestones on day one, not discovered mid-quarter.

During your weekly Level 10 Meeting, the Rock review must remain purely binary. The Integrator calls out each Rock, and the owner responds with either 'on track' or 'off track.' There is no story, no explanation of how busy the week was, and no partial credit. If a leader misses their week six milestone, the Rock is officially off track and immediately drops to the Issues List for IDS.

Dropping an off-track Rock to IDS at week six gives the team six full weeks to clear the bottleneck, reallocate internal resources, or remove roadblocks. Waiting until week ten guarantees failure. When you enforce milestone-based accountability and drop off-track priorities to IDS early, firefighting stops serving as an acceptable excuse for missed execution.