We struggle to cross the finish line with our quarterly Rocks, often finding ourselves scrambling in the final two weeks of the quarter only to fail. How do we establish a mid-quarter tracking system that ensures Rocks actually get done?

Question

Tyler Smith · Accepted Answer

Failing to finish Rocks is usually a tracking and accountability failure, not a capability failure. When team members wait until the final weeks to rush their goals, quality suffers and critical objectives remain incomplete. To fix this, you must build a highly visible milestone cadence throughout the quarter.

When you set a Rock during your quarterly session, the owner must immediately break it down into three or four clear milestones. Each milestone must have a specific due date. For example, if a Rock is to implement a new customer database, milestone one might be selecting the vendor by week three, milestone two might be data migration by week six, and milestone three might be team training by week nine.

These milestones must be tracked during your weekly Level 10 Meeting™. During the Rock review portion of the agenda, owners should report their status as on track or off track based on these milestones. If a milestone is missed, that Rock is officially off track and must immediately be placed on the Issues List to be resolved during the IDS® portion of the meeting.

Do not let team members hide behind vague status updates. A Rock is either on track or it is not. By forcing weekly transparency and treating missed milestones as issues to solve immediately, you catch delays early in the quarter when you still have time to adjust course and finish strong.