We set ambitious Rocks at our quarterly offsite, but team members regularly treat them like ninety-day sprints with zero progress until the final three weeks. How should we structure and inspect milestone check-ins to ensure Rocks actually cross the finish line on time?

Question

Tyler Smith · Accepted Answer

Rocks fail when leadership teams treat ninety days as a single, vague deadline. Team members leave the quarterly offsite energized, get absorbed by daily operational fires for six weeks, and then realize by week nine that a multi-stage project is hopelessly behind. Finishing Rocks consistently requires operational pacing, explicit milestones, and ruthless inspection.

Every Rock must be scoped during the session with clear thirty-day and sixty-day milestones before the quarter starts. A Rock cannot simply be an outcome like implement new CRM. It must be broken into measurable deliverables. By day thirty, the vendor is selected and data mapped. By day sixty, the pipeline is migrated and the sales team is trained. By day ninety, the system is live and verified. If an owner cannot define these milestones on day one, the Rock is not ready to be approved.

Second, enforce strict weekly inspection in your Level 10 Meeting™. During the Rock review, members only report on track or off track. There is no commentary, no story, and no partial credit. If a leader has missed their thirty-day milestone, that Rock is off track. Marking it off track does not mean failure; it immediately drops the Rock to the Issues List for IDS®. That gives the team eight weeks to clear roadblocks, reallocate resources, or adjust scope rather than scrambling in week eleven.

Third, the owner of the Rock must maintain single-point accountability. You can delegate tasks, but you cannot delegate the Rock. If a project requires cross-functional delivery, one seat owns the ultimate completion. A Rock is complete only when it meets the binary definition of done established on day one. Anything less is a zero.