We struggle to write our quarterly Rocks in a way that makes their completion binary, often resulting in debates at the end of the quarter about whether a Rock was actually achieved. How do we scope our quarterly Rocks during our planning sessions to eliminate this ambiguity?

Question

Tyler Smith · Accepted Answer

Setting vague quarterly commitments is a primary reason teams fail to cross the finish line. To solve this, you must adopt an engineering mindset during your quarterly pulsing sessions. When a Rock is proposed, do not let the session exit until the definition of done is completely clear and measurable. A well-written Rock must be binary, meaning at the end of ninety days, the answer to is it done is either a yes or a no, with no room for a ninety percent complete middle ground.

To achieve this, avoid verbs like improve, analyze, or streamline without a concrete metric. Instead, use specific deliverables. For example, rather than writing improve customer onboarding, write document the five-step onboarding process, train the support team, and achieve an onboarding time of under forty-eight hours. This level of specificity leaves zero room for debate on week twelve.

Before finalizing any Rock on your V/TO®, put it through a simple test. Ask the owner what physical evidence they will present at the next quarterly meeting to prove the Rock is complete. If they cannot describe a specific document, a live system, or a recorded metric, the Rock is not ready. Your Integrator must hold the line here. Reject any Rock description that requires a subjective assessment. This discipline forces the leadership team to think through the execution steps during the planning session rather than trying to figure them out mid-quarter when daily operations are already chaotic.