Our company regularly misses the 80 percent completion threshold on quarterly Rocks because work expands mid-quarter. How do we structure Rock milestones so they actually cross the finish line by day 90?
The failure to complete quarterly Rocks almost never stems from a lack of effort. It stems from poor scope discipline on session day and an absence of intermediate mileposts. If a Rock is defined loosely, team members will subconsciously expand the scope whenever operational fires crop up.
To ensure Rocks finish cleanly at the 80 percent or higher target, enforce three non-negotiables:
- Set binary success criteria. A Rock cannot be described as research a new CRM or improve client onboarding. It must have a verifiable deliverable: CRM contract executed with five users migrated, or new client onboarding checklist built and tested on three accounts. On session day, the answer to whether it is complete must be a simple yes or no.
- Require three milestone dates at week four, week eight, and week eleven. Rocks stall because owners wait until week nine to begin heavy lifting. Setting binary checkpoints forces the owner to confront bottlenecks early. If the week four milestone is missed, it drops immediately to the Level 10 Issues List as an off-track Rock.
- Limit each leader to one to three Rocks maximum. High achievers naturally overestimate what they can accomplish in 90 days alongside running the day-to-day business. Achieving three Rocks at 100 percent completion creates vastly more operational momentum than staggering across the quarter with six Rocks at 60 percent completion.
Category: EOS Implementation