tyler-smith.com · Questions & Answers

Our quarterly Rocks consistently suffer from ambiguity at the deadline because the owner claims the Rock is done while the Integrator says it is not. How do we define verifiable completion criteria at the start of the quarter?

A Rock that cannot be verified by a third party with a simple yes or no is not a Rock; it is a wish list. Subjective disagreements at the end of a quarter happen because the leadership team accepted vague milestones during quarterly planning.

To solve this, implement a strict definition of done before any Rock is approved. A Rock must never be written as an activity, such as research CRM systems or work on hiring plan. It must be written as a finished, binary outcome. For example, write it as new CRM system fully migrated with entire sales team logging calls and thirty-day pipeline report generated.

During your quarterly session, the Integrator must pressure-test every single Rock using the SMART framework. Ask the owner: exactly what evidence will you place on the table on day ninety to prove this is one hundred percent finished? If the answer involves subjective words like improved, streamlined, or enhanced, reject the Rock immediately. Force the owner to attach a tangible artifact.

Acceptable artifacts include:
- A documented and fully executed standard operating procedure.
- A newly hired leader who has completed their thirty-day onboarding roadmap.
- A technical integration running live in production with zero open critical bugs.

Once the criteria are locked, they cannot be renegotiated at week eight because the owner ran out of time. If the binary condition is not met at the end of ninety days, the Rock is incomplete. This removes emotion and forces leaders to accurately scope their capacity upfront.

Category: EOS Implementation

← All questions