We are setting Rocks, but we struggle with vague definitions of completion, leading to debates at the end of the quarter about whether a Rock is actually done. How do we write bulletproof, binary Rocks that leave zero room for interpretation?

Question

Tyler Smith · Accepted Answer

The primary reason Rocks fail to cross the finish line is because they are poorly scoped and written with vague, subjective language. If a Rock is to improve our customer onboarding process, you are guaranteed to have a debate at the end of ninety days about whether you actually succeeded. You must eliminate all room for interpretation by writing binary Rocks.

A binary Rock has only two possible outcomes: it is either done or not done. There is no partial credit. To achieve this, use the definition of done framework. Instead of improve onboarding, your Rock must be written as: create and document the new client onboarding process in our Core Processes, train the account management team, and achieve a one hundred percent adoption rate for new accounts starting after November first.

To make this stick, every Rock must have a clear owner who has the GWC™ (Get It, Want It, Capacity to Do It) for that specific goal. During your quarterly planning, pressure-test each proposed Rock by asking: How will we know, without a shadow of a doubt, that this is complete on day ninety?

If you cannot answer that question with a simple yes or no metric, the Rock is not ready. Write out the exact deliverables, milestones, and completion criteria. This eliminates the grey area and ensures your team finishes what they start.