We set Rocks each quarter, but around week six or seven our progress stalls out as daily operational fires surge. How do we maintain execution momentum during the mid-quarter lull?

Question

Tyler Smith · Accepted Answer

Mid-quarter stalls happen when Rocks are treated as ninety-day deadlines rather than weekly execution tracks. When an owner defines a Rock on session day, the deadline feels distant. Daily operational fires inevitably crop up, the team deprioritizes the project, and by week seven everyone realizes they have made zero tangible progress.

To prevent the mid-quarter lull, every Rock must be broken down into mandatory milestones during the first seven days of the quarter. A healthy Rock should have distinct completion checkpoints at day 30, day 60, and day 75. If a Rock owner does not cross their 30-day milestone, that Rock is off track immediately, not at week ten when it is too late to rescue it.

The weekly Level 10 Meeting is your early warning system. If an owner marks their Rock as off track at week six, do not allow them to say they will make it up next week. Drop that Rock straight to the Issues List. Use IDS to diagnose why execution stalled. Is it an unexpected capacity bottleneck? Is the owner waiting on another department head? Does the scope need to be adjusted right now? By confronting the delay in real time during the weekly meeting, you protect the quarterly outcome instead of conducting an autopsy at the next quarterly session.