Our leadership team regularly reaches the end of the quarter with Rocks that are eighty percent finished, leading to arguments over whether they should count as complete. How do we write Rock definitions so they finish clean on week twelve?

Question

Tyler Smith · Accepted Answer

A Rock that is eighty percent finished is incomplete. In EOS, a Rock is binary: it is either done or not done. The reason leadership teams get stuck in partial completion debates is that they write vague, activity-based Rock descriptions instead of clear milestone definitions with measurable end states.

When setting Rocks during your quarterly planning session, never accept an open-ended title like Improve customer onboarding or Upgrade sales automation. Force the Rock owner to write a specific definition of done. What concrete deliverable will exist on the final day of the quarter? A valid description sounds like this: Customer onboarding SOP documented, tested with three new accounts, and adopted by all four account managers with signed acknowledgments.

Next, mandate that every Rock includes three to five chronological milestones mapped across the ninety days. If a Rock owner cannot describe what week four, week eight, and week eleven look like, the Rock is not ready for approval. Your Integrator should reject any Rock that lacks clear milestone gates.

During the weekly Level 10 Meeting, keep Rock status strictly binary: on track or off track. If a Rock owner reports on track for eight weeks and suddenly drops the ball in week ten, your team failed to run IDS on the true velocity earlier. By demanding black-and-white completion criteria on day one, you remove personal opinions and force execution across the full quarter.