We have no problem setting Rocks, but our team constantly gets to week eight and realizes their Rocks were scoped so poorly they are impossible to finish. How do we properly scope and define a Rock on day one so it is guaranteed to cross the finish line by day ninety?

Question

Tyler Smith · Accepted Answer

Poorly scoped Rocks are usually the result of vague writing and a lack of clear milestones. To fix this, you must stop writing Rocks that sound like ongoing operational duties or broad initiatives. A Rock must be specific, measurable, attainable, realistic, and timely. On day one of your ninety-day cycle, every Rock must have a clear definition of done. If the leadership team cannot agree on what the final deliverable looks like in physical or digital form, the Rock is not ready to be approved.

The best way to ensure a Rock finishes is to break it down into three or four clear milestones. For example, if a Rock is to document our sales onboarding process, week three must be draft outline complete, week six must be first draft reviewed, and week nine must be final document approved. If your milestones are not defined on day one, you are just hoping for the best.

Furthermore, your Integrator must ruthlessly police the scoping during your quarterly planning session. If a Rock is too big, slice it in half and make the first half this quarter's Rock. It is far better to complete three smaller, highly impactful Rocks than to fail at five massive ones. This discipline is what builds organizational traction.