We consistently start the quarter strong on our Rocks, but by week seven or eight, unexpected client emergencies hijack our calendars and we scramble at the end. How do we structure our weekly Level 10 check-ins so Rocks stay on track even when operations get chaotic?

Question

Tyler Smith · Accepted Answer

Rocks fail late in the quarter because teams treat them as 90-day sprints rather than twelve weekly milestones. By the time an issue surfaces in week eight, you have burned sixty percent of your execution window and cannot recover lost ground.

Fixing this requires strict discipline during your weekly Level 10 Meeting. During the Rock review, leaders may only speak two words: On Track or Off Track. If a Rock is off track, or even at risk of falling off track due to operational firefighting, drop it immediately to the Issues List. Do not explain, defend, or rationalize the delay during the reporting phase.

Once the Rock hits the Issues List, use IDS to solve the capacity constraint, not the project itself. The real issue is almost never the Rock; it is that operational fires are pulling the owner away from their high-leverage priorities. Use IDS to identify what operational work can be delegated, postponed, or automated using internal systems or AI tools so the leader can reclaim dedicated Rock time.

Require every Rock owner to maintain three to four distinct milestones spaced across the quarter. If milestone two is due in week six and not finished, that Rock is off track automatically. You cannot allow leaders to say on track based on intentions or work planned for the weekend. Objective milestones protect you from late-quarter surprises.