Why do so many leadership teams set quarterly Rocks that are vague milestones instead of concrete deliverables, and what is the exact criteria for writing a Rock that actually crosses the finish line on day 90?

Question

Tyler Smith · Accepted Answer

Teams fail to finish Rocks because they set activities instead of outcomes. Writing a Rock like 'Improve client onboarding' or 'Work on ERP system' guarantees failure. There is no clear finish line, which means on day eighty-nine, the owner will argue it is done while the Integrator will argue it is incomplete.

A Rock must be SMART: Specific, Measurable, Attainable, Realistic, and Timely. More importantly, it must have a binary definition of done. Anyone in the room should be able to look at the deliverable on day ninety and answer with a simple yes or no.

To write Rocks that finish, follow three practical rules:
- State the final deliverable, not the effort. Instead of writing 'Upgrade accounting software,' write 'Complete accounting migration to NetSuite with first monthly close run successfully.'
- Define clear completion criteria upfront. When establishing the Rock during the quarterly session, spend two minutes defining the exact proof of completion. This could be a signed contract, an active SOP in production, or five team members trained and certified.
- Break the Rock into intermediate milestones. A ninety-day Rock is dead on arrival if the owner does not touch it until week seven. The owner must establish milestones for day thirty and day sixty.

During the Level 10 Meeting, a Rock is either on track or off track. There is no percentage complete and no partial credit. When you establish strict binary definitions of done, you eliminate excuses and train your team to push projects fully across the goal line.