tyler-smith.com · Questions & Answers

How do we write the specific definition of done for our quarterly Rocks so there is no ambiguity or subjective debate at the end of the quarter about whether a Rock actually crossed the finish line?

Rocks fail to finish when they are scoped as ongoing initiatives rather than binary milestones. When a Rock is worded as improve client onboarding or upgrade financial reporting, the owner can always claim progress even if the company gained zero functional capability. You prevent this by forcing a clear, objective finish line during your quarterly planning session before anyone leaves the room.

Every Rock must follow a strict format: a single verb, a specific deliverable, and clear acceptance criteria. For example, rather than revamp sales collateral, the Rock should be written as deliver three client case studies and a standard pitch deck approved by sales leadership. If you cannot answer the question of completion with a simple yes or no on the final day of the quarter, the Rock is poorly written.

Use this three-part standard for every individual and company Rock:

- Define the exact tangible artifact or measurable result produced.
- Establish who must review, approve, or sign off on the deliverable.
- Break the ninety-day goal into three thirty-day milestones so lag is exposed early.

In EOS®, there is no partial credit. An eighty percent complete Rock is incomplete. If your leadership team debates whether something counts as done during week twelve, your planning failed in week one. Force the debate on day one. When you clarify the exact conditions of completion upfront, the owner knows the target and cannot hide behind busywork when time runs out.

Category: EOS Implementation

← All questions