We set Rocks every quarter but always end up with a mad rush in week twelve where things are either half-baked or pushed to next quarter. How do we build a systematic mid-quarter checkpoint to guarantee Rocks actually cross the finish line?

Question

Tyler Smith · Accepted Answer

The root cause of the last-minute scramble is a lack of clear milestones and visibility between weeks three and nine. To fix this, you need to treat Rocks as projects with explicit, non-negotiable milestones that are tracked weekly in your Level 10 Meeting™.

During your weekly meetings, a Rock is either on track or off track. If a Rock is off track for more than two consecutive weeks, it must be dropped to the Issues List and resolved using IDS® immediately. Do not wait for week twelve to realize a project is in trouble.

First, require every Rock owner to break their ninety-day goal into three clear milestones: thirty-day, sixty-day, and ninety-day deliverables. These are not mental notes; they must be documented.

Second, during the weekly Rock review, the owner must state "on track" or "off track" based on these milestones, not on their emotional state or how busy they feel.

Third, implement a strict mid-quarter review during week six. This is not a formal session, but a targeted check on your scorecard. If a milestone is missed, the team must identify the root bottleneck. Either you resource it, adjust the scope, or accept that it is off track and solve the resource gap. By forcing this operational checkpoint, you eliminate the magical thinking that causes week twelve failures.