Our quarterly Rocks consistently stall out around week seven because team members get swallowed by daily fires and then scramble at the end. What pacing mechanism ensures Rocks actually get completed across the full quarter?

Question

Tyler Smith · Accepted Answer

Rocks stall out when teams treat them as 90-day projects rather than breaking them into sequential milestones during the first two weeks of the quarter. When week seven arrives and an owner has not touched their Rock, panic sets in and quality evaporates.

To ensure Rocks finish predictably, require every Rock owner to define three to four critical milestones during the first Level 10 Meeting of the quarter. These milestones should map to day 30, day 60, and day 75. A milestone is not a vague intention; it is a concrete deliverable with a strict deadline.

During your weekly Level 10 Meeting Rock review, keep reporting strictly binary: on track or off track. If a milestone is missed, the Rock is immediately marked off track and dropped to the Issues List for IDS. Never allow a leader to say they are off track but will catch up next week.

Dig into the root cause during IDS. Is the stall caused by a cross-departmental bottleneck, unrealistic initial scoping, or daily fire-fighting? By diagnosing off-track milestones in week four or five, the leadership team clears hurdles while there is still ample time to finish by day 90.