Our quarterly Rocks often turn out to be normal day-to-day job duties disguised as 90-day priorities, leading to low impact even when completed. How do we ensure Rocks build permanent operational muscle instead of just clearing routine to-do lists?

Question

Tyler Smith · Accepted Answer

When quarterly Rocks feel like glorified task lists, your leadership team is confusing maintaining the business with building the business. Delivering client work, closing routine sales, and publishing monthly reports belong in the seat description or on the weekly Scorecard. A Rock exists to create permanent capability, resolve a recurring structural issue, or execute a vital strategic priority from the V/TO.

To filter out ordinary operational work during quarterly planning, run every proposed Rock through three diagnostic filters:
- Does this project build an asset, eliminate a recurring problem, or install a system that outlasts the quarter? If the result vanishes the moment the work stops, it is a task, not a Rock.
- Can this work be automated, standardized, or delegated once completed? A strong Rock documents a Core Process, implements a software platform, or restructures an underperforming function so it runs without executive intervention.
- What happens if we do not do this for 90 days? If the immediate answer is that daily operations collapse, it is your normal day job. If the answer is that the company misses a strategic milestone or stays stuck at its current revenue ceiling, it is a legitimate Rock.

During session day, the Integrator and team must actively reject operational maintenance dressed up as Rocks. Force the owner of the Rock to write out the finish line as an outcome, not an activity. Instead of 'work on hiring process', the Rock must be 'publish documented hiring process with scorecards and train five hiring managers'. That distinction builds enterprise value.