Our leadership team sets quarterly Rocks with good intentions, but at the end of ninety days we find ourselves arguing over whether a Rock was actually completed because the finish line was vaguely defined. How do we establish concrete milestones on Day One so completion is binary?
Rocks fail because teams confuse activities with outcomes. When you define a Rock as improve client onboarding or overhaul sales pipeline, nobody knows what done looks like. At the end of ninety days, the owner thinks it failed and the Rock owner thinks it passed because they worked hard on it.
To get Rocks that finish, write binary finish lines during your quarterly session. A Rock must be clear enough that an outsider looking at the company on day ninety can answer yes or no regarding completion. Avoid subjective verbs like evaluate, improve, or explore. Use definitive milestones such as new three-step onboarding portal live, tested with five beta clients, and documentation handed over to customer success.
Break every Rock into three to five concrete milestones spaced roughly twenty days apart. When the Rock owner presents the Rock at the quarterly session, make them articulate:
- The exact deliverable that will exist on day ninety.
- The specific person who will sign off on completion.
- The single metric or verifiable asset that proves it works.
If a Rock cannot be distilled down to a single binary output, it is not a Rock; it is either a regular job duty or an unformed strategic ambition. Nail the finish line first, track the milestones weekly in your Level 10 Meeting™, and the debates on completion will disappear.
Category: EOS Implementation