Our leadership team members consistently hit week 10 of the quarter with their Rocks marked on track, only for three of them to fail by week 13 because critical dependencies were missed. How do we structure Rock milestones and verify true completion well before the quarter closes?
A Rock that fails in week 13 did not break in week 13. It broke in week three when the owner failed to break a 90-day goal into measurable milestones with clear cross-departmental dependencies. Reporting on track during the Level 10 Meeting™ is often just optimism masking a lack of progress.
To guarantee your Rocks actually cross the finish line, change how you write and track them.
First, enforce a strict definition of done before leaving your quarterly session. A Rock cannot be a vague ambition like improve onboarding. It must have binary completion criteria, such as: new client onboarding automated in the CRM with 100 percent of active accounts migrated and three test cohorts completing the flow without manual intervention.
Second, mandate that every Rock owner build a milestone schedule within the first two weeks of the quarter. A healthy Rock requires three to four verifiable checkpoints due at weeks 4, 8, and 11. If a milestone is missed at week 4, the Rock is immediately flagged as off track on the weekly Scorecard. Do not let leaders mark a Rock on track because they plan to work on it next weekend. If the week 4 deliverable is not done, the status is red.
Third, identify external dependencies at the moment of creation. If your marketing Rock requires three weeks of development work from engineering, the engineering seat must co-sign the milestone timeline in the session room.
When you force binary milestones and call out false green statuses early, your team stops treating week 13 as a panic deadline and starts closing Rocks out cleanly by week 11.
Category: EOS Implementation