We are struggling to define what a completed Rock actually looks like, leading to debates at the end of the quarter about whether a priority is truly done. How do we establish objective, binary standards of completion for every quarterly Rock during our planning sessions?

Question

Tyler Smith · Accepted Answer

If your leadership team is arguing about whether a Rock is finished at the end of the ninety-day cycle, the issue lies in how the priority was written during your planning session. A Rock must be binary: it is either done or not done, with no room for subjective interpretation or partial credit.

To establish objective standards, you must define the exact, measurable finish line before the session ends. A well-scoped Rock should have a specific, verifiable deliverable. If a Rock is written as improve customer service, it is too vague. Instead, it must be written as reduce average support ticket resolution time from forty eight hours to twelve hours, or hire and onboard two customer service representatives.

When setting your quarterly Rocks, use the following checklist to ensure binary completion:
- Define the physical or digital output that proves the Rock is done, such as a signed contract, a published document, or a deployed software tool.
- Assign a single owner to the Rock, ensuring one person is accountable for driving the objective to the finish line.
- Validate that the owner GWC™ the priority and has the necessary resources to complete it within seventy five days.

Establishing this discipline during your quarterly planning prevents end of quarter frustration. It ensures that when your ninety days are up, the leadership team can objectively mark each Rock as done or not done, keeping your execution clean and focused.