We started our EOS journey but we are still arguing at the end of every quarter about whether a Rock is truly done or not because the owner changed the scope halfway through. How do we lock down our Rock definitions at the start of the quarter so there is absolutely zero gray area?

Question

Tyler Smith · Accepted Answer

To stop arguing about whether a Rock is finished, you must eliminate all subjective language during your quarterly session. When a Rock is set, it cannot be written as a vague activity like improve marketing or work on the sales pipeline. It must be written as a specific, measurable end-state with a binary yes or no outcome.

We use the one sentence rule. A properly defined Rock must state exactly what done looks like in a single sentence. For example, instead of write new sales manual, the Rock must read draft, finalize, and train the sales team on the new five-step sales playbook, with signed off receipts from all five sales reps.

If the owner or any leader attempts to alter the scope of a Rock mid-quarter, the Integrator must step in and protect the boundaries. A Rock is a firm ninety-day commitment. If market conditions change or the scope must expand, you do not rewrite the existing Rock. You either push the new scope to the next quarter or kill the current Rock and document it as a conscious pivot on your weekly issues list. Never allow quiet scope creep to turn a finished Rock into a failure. By enforcing strict, binary definitions at the start of the ninety days, you remove all emotional debate during the review.