We keep setting quarterly Rocks that are actually disguised multi-year initiatives, causing them to stall halfway through the quarter. How do we break massive strategic projects down into bite-sized ninety-day Rocks that actually get finished?

Question

Tyler Smith · Accepted Answer

Teams fail to finish quarterly Rocks when they confuse a multi-stage strategic milestone with a single ninety-day objective. When a leader claims a Rock like implement new enterprise CRM or overhaul company pricing structure, they are setting up a year-long program under the guise of a ninety-day commitment. By week six, the scope balloons, daily fires take over, and the Rock limps across the finish line incomplete.

To ensure quarterly Rocks actually cross the finish line:
- Limit the scope to what can be fully designed, executed, and validated within eighty to eighty-five days, leaving buffer for the final review.
- Write the Rock title as a completed end state with objective proof. Replace work on website redesign with new five-page website live in production with working demo booking form.
- Define three to four sequential milestones during session day. For example, milestone one is vendor selected by day thirty; milestone two is system architecture approved by day sixty; milestone three is full data migration verified by day seventy-five.
- Use the Level 10 Meeting™ strictly to verify status. If a Rock goes off track, use IDS® immediately to address the roadblock instead of waiting until week eleven when failure is guaranteed.

Finishing eighty percent or more of your Rocks every quarter requires radical discipline in the sizing of the rock during session day. Small, finished milestones build execution momentum; massive, unfinished goals breed complacency.