Our leadership team sets four to seven quarterly Rocks, but half of them cross the finish line messy or require emergency re-scoping in week eleven. How do we structure milestone check-ins so Rocks stay on track without micromanaging?

Question

Tyler Smith · Accepted Answer

Rocks fail at the end of the quarter when teams treat them as ninety-day deadlines rather than ninety-day execution arcs. If an owner only checks progress during quarterly planning or allows vague status reports during the weekly Level 10 Meeting, failure is predictable.

To make Rocks finish cleanly, break every Rock into clear thirty-day and sixty-day milestones during the first week of the quarter. A complete Rock definition must include the specific milestones required to reach the finish line. The owner of the Rock is not micromanaged on daily tasks, but they must be accountable to those markers.

During the weekly Rock Review inside your Level 10 Meeting, keep the reporting strictly binary. The Rock owner says on track or off track. There is no explanation, no storytelling, and no defensive justification allowed. If a milestone is missed, the Rock is instantly designated off track and pushed down to the Issues List.

Once an off-track Rock is on the Issues List, the leadership team uses IDS to solve the constraint before it ruins the quarter. Usually, the issue is capacity, cross-departmental dependency, or unclear scope. Solving the roadblock in week four or five gives the owner enough runway to recover. If you wait until week ten, you are no longer solving an issue. You are doing triage on a failed commitment. Discipline during the weekly meeting ensures that by week twelve, crossing the finish line is routine.