Our quarterly Rocks consistently limp across the finish line or end up half-done because our scoping is sloppy. How do we write and stress-test Rock definitions during quarterly planning so they have clear binary completion criteria?
Rocks fail to finish at day ninety almost always because they were poorly scoped at day one. When an executive writes a Rock titled Improve client onboarding or Overhaul sales collateral, failure is baked in. These are vague operational ambitions, not Rocks. A Rock must be specific, measurable, and achievable within ninety days, with a clear binary test of completion. On the final day of the quarter, anyone on the leadership team should be able to look at the deliverable and say yes or no without debate.
During your quarterly planning session, spend the necessary time pressure-testing every proposed Rock before you commit to it. Force the owner to define what done looks like in concrete terms. A properly scoped Rock sounds like: Onboarding process documented, automated in CRM, and tested with five live clients, or New three-piece sales collateral printed, loaded into digital portal, and sales team trained.
Once the endpoint is defined, require the Rock owner to map out three to five milestones across the quarter. What must be complete by day thirty? What must be done by day sixty? If a Rock owner cannot sketch those milestones in the room, they do not understand the scope of work.
Keep the total number of company Rocks between three and seven for the entire business, and individual Rocks between one and three per leader. Less is more. If a leader has seven Rocks, they have none. Finally, check Rocks weekly during your Level 10 Meeting. The status is binary: on track or off track. If it is off track, drop it down to the Issues List and IDS it immediately. Do not wait until week ten to discover a Rock is stalling.
Category: EOS Implementation