During quarterly planning, our leaders write vague Rock descriptions that lead to arguments in week twelve about whether the goal was actually met. How do we write bulletproof definitions of done for our quarterly Rocks so execution is unambiguous?

Question

Tyler Smith · Accepted Answer

A Rock that lacks an unambiguous definition of done fails the moment you step out of your quarterly session. When a Rock says improve customer onboarding or revamp sales collateral, completion becomes a matter of personal opinion. That ambiguity guarantees frustration and debate in the final Level 10 Meeting of the quarter.

Every quarterly Rock must meet the SMART standard, with special emphasis on specific and measurable. During your session, the leadership team must aggressively pressure-test every proposed Rock before locking it down. The owner of the Rock must state exactly what will physically exist on the final business day of the quarter that does not exist today.

Use a three-part standard for every Rock description:
- The tangible deliverable: What specific asset, workflow, or software system is live?
- The objective standard: What metric or test proves it operates as intended?
- The milestone roadmap: What are the three interim milestones due in weeks three, six, and nine?

Instead of writing upgrade warehouse management system, write: New inventory tracking module live in production, zero paper manifests used for seven consecutive operating days, and all five shift leads certified on the handheld scanners.

If a Rock cannot be verified in five seconds by examining a screen, a report, or an active process, it is not properly scoped. Once drafted, the Integrator asks the room: If this exact criteria is presented in ninety days, will everyone agree this Rock is complete without debate? Only when every leader confirms do you record the Rock.

This discipline eliminates eleventh-hour scrambling and keeps your team accountable to verifiable results.