Our leadership team consistently writes quarterly Rocks that drag on or get rolled over. What exact mechanism forces Rocks to actually get finished within the 90 days?

Question

Tyler Smith · Accepted Answer

Rocks drag out or fail to cross the finish line because they are framed as ongoing operational duties rather than project deliverables with binary completion criteria. A Rock is not an ongoing goal such as improve customer service or build marketing pipeline. A Rock is a specific milestone that is either complete or incomplete at the end of the quarter, with zero room for interpretation.

To ensure Rocks finish, enforce three specific disciplines during your quarterly session:

- Define the end state on day one. When writing the Rock, ask the owner what specific artifact will prove the work is complete. If it is a process overhaul, the Rock is not complete until the process is documented, the team is trained, and the first live transaction passes through it.
- Establish specific milestone check-ins. Require each Rock owner to map out milestones for weeks three, six, and nine. While the Level 10 Meeting simply tracks whether the Rock is on or off track, the Integrator must hold owners accountable to their internal pacing.
- Enforce strict binary scoring on session day. A Rock that is ninety percent done is scored as incomplete. There are no partial grades and no excuses.

When you eliminate gray areas and demand complete finishes, team members stop treating Rocks like suggestions. They learn to scope their commitments conservatively, write clear deliverables, and sprint through the final weeks of the quarter instead of negotiating for rollover status.