Our leadership team starts each quarter with high enthusiasm for their Rocks, but we consistently hit day ninety with only half of them actually completed. What structural gap in our weekly execution is causing our quarterly Rocks to stall?

Question

Tyler Smith · Accepted Answer

Failing to complete Rocks is rarely a resource issue. It is almost always a lack of weekly milestones and accountability. Many leadership teams treat Rocks as large, ninety-day projects that they can start working on in week six or seven. By the time they realize they are behind, the quarter is over and the Rock is incomplete.

To fix this structural gap, you must change how Rocks are tracked during your weekly Level 10 Meeting™. A Rock should never be reported as on track simply because a leader feels good about it. On track must mean that the specific milestones for this week have been completed.

When a Rock is assigned during your quarterly planning session, the owner must immediately break it down into three or four clear milestones with specific due dates throughout the quarter. During your weekly meeting, when the Integrator reviews the Rocks list, the owner must report on track or off track based solely on those milestones.

If a Rock is off track for two consecutive weeks, it must immediately be dropped down to the Issues List to be resolved using the IDS® process. This prevents team members from hiding their lack of progress until it is too late to recover. Completing Rocks is about establishing a predictable rhythm of execution. By building weekly milestone accountability directly into your operating system, you ensure that your team stops scrambling at the end of the quarter and starts hitting their ninety-day goals consistently.