Our team sets quarterly Rocks that look good on paper, but we constantly debate whether they were actually completed at the end of ninety days because the deliverables were too vague. How do we define and scope Rocks so that completion is 100 percent binary?

Question

Tyler Smith · Accepted Answer

Rocks fail at the beginning, not at the end. When a leadership team scrambles in the final week of a quarter debating whether a Rock is done, the problem is not execution. The problem is lazy scoping during quarterly planning.

A Rock must be binary. It is either 100 percent complete or it is incomplete. There is no such thing as an 80 percent complete Rock. If there is room for interpretation, the Rock was poorly written. Subjective goals like improve customer onboarding or overhaul marketing assets invite debate because completion is in the eye of the beholder.

To eliminate ambiguity during quarterly planning, apply these structural rules:
- Write the Rock with a clear, measurable finish line. Instead of improve customer onboarding, write new 5-step client onboarding workflow documented, tested with three clients, and approved by the Integrator.
- Define the specific deliverable upfront. Attach tangible artifacts such as an SOP link, a signed vendor contract, or a deployed software configuration.
- Break the Rock into three to five sequential milestones with internal due dates across the ninety days. If the owner hits milestones at days 30, 60, and 75, there is zero confusion by day 90.

When an owner presents a proposed Rock in your quarterly session, the other leaders must challenge vague phrasing. If someone cannot describe exactly what done looks like in a single sentence that a stranger could verify, do not accept the Rock onto the company list.