Why do our quarterly Rocks routinely fail to finish within the 90-day window, and how do we write Rock definitions so tight that completion is binary on session day?

Question

Tyler Smith · Accepted Answer

Rocks fail to cross the finish line for two predictable reasons: they are scoped as ongoing job functions instead of defined deliverables, or they lack a clear definition of done. When a Rock is titled improve customer onboarding or overhaul marketing strategy, the owner can work 80 hours a week and still fail to complete it by day 90.

A Rock must be specific, measurable, and binary. At the end of the quarter, it is either 100 percent complete or incomplete. There is no partial credit, no 90 percent done, and no credit for good effort.

To ensure Rocks finish, enforce a strict definition protocol during your quarterly session:

- Define the exact deliverable. If the Rock is about onboarding, the deliverable is not better onboarding. It is document and roll out the five-step onboarding checklist, train all four account managers, and run three new clients through the workflow.
- Break the Rock into four milestones. Milestone one must finish by week three, milestone two by week six, milestone three by week nine, and milestone four by week eleven.
- Assign one single owner. If two people own a Rock, nobody owns it.

When a Rock is defined with an unmistakable end state and measurable midway checkpoints, the owner cannot hide behind vague progress updates during the weekly Level 10 Meeting. They either hit the milestones or raise an issue during IDS long before week twelve.