When we set quarterly Rocks, how do we write specific milestone definitions during session day so that completion is purely binary and leaves zero room for debate at the end of the quarter?

Question

Tyler Smith · Accepted Answer

A Rock fails to finish when its definition of done was soft on session day. If a Rock description contains words like improve, evaluate, research, or streamline, you have already failed. Those are activities, not deliverables. An activity can drag on indefinitely. A completed Rock is a closed event.

To write a Rock that finishes, force every owner to state the exact deliverable in observable, binary terms before anyone leaves the room. Ask the room: on the final day of the quarter, how will we verify this without taking your word for it? The answer must be a specific artifact or a measurable threshold.

Use a simple three-point check for every single Rock:
- Define the physical deliverable, such as a signed contract, an installed software tool, or an SOP published to the company knowledge base.
- Set three clear milestones at days thirty, sixty, and seventy-five to prevent a panicked sprint in week twelve.
- Confirm the Rock has only one owner on the Accountability Chart, never two.

If a project requires multiple departments, the Rock belongs to the person responsible for the final outcome. The other seats take supporting Rocks or weekly To-Dos. When you make the finish line binary, there is no room for debate when the quarter ends. The deliverable either exists in production or it does not.