Our leadership team sets clear binary Rocks, but people leave eighty percent of the work until the final three weeks of the quarter and scramble, resulting in sloppy work or late finishes. How do we structure Rock tracking across the thirteen-week quarter to ensure steady execution and on-time completion?

Question

Tyler Smith · Accepted Answer

Leaving Rock execution to the final month is a structural failure in project pacing. A ninety-day window feels long enough that leaders procrastinate until week nine, when operational gravity suddenly overwhelms them. To fix this, you must demand milestone discipline during the quarterly planning session.

When a leader drafts a Rock, the deliverable must be binary, but the execution path cannot remain an unstructured ninety-day blank slate. Require the Rock owner to define three intermediate milestones: one for day thirty, one for day sixty, and one for day ninety. A Rock is not finalized in your quarterly session until these thirty-day checkpoints are clearly documented.

During the weekly Level 10 Meeting, you only report whether a Rock is on track or off track. You do not discuss the details unless it is off track. However, the Integrator must hold Rock owners accountable to their intermediate milestones. If an owner reaches week six and has not hit their thirty-day milestone, that Rock is off track by definition, even if the owner swears they can catch up.

Dropping a Rock to the Issues List at week six gives the team seven weeks to solve the bottleneck through IDS. Waiting until week eleven guarantees failure.

Hold a hard line on the definition of on track. On track means the milestones scheduled for this exact week are finished. If leaders know they cannot hide behind vague optimism mid-quarter, they will pace their execution evenly and finish their Rocks clean.