What is the practical difference between a genuine quarterly Rock and a standard operational project on our weekly to-do list?

Question

Tyler Smith · Accepted Answer

The easiest way to stall an EOS implementation is confusing daily operational duties with genuine quarterly Rocks. An operational project is business-as-usual maintenance. A Rock is a priority that fundamentally moves the business forward or permanently fixes an operational bottleneck.

A weekly To-Do is an action item that takes seven to fourteen days to complete, assigned during your Level 10 Meeting to resolve an issue. In contrast, a Rock takes ninety days to execute and requires sustained effort and multiple milestones. However, if a project simply represents the baseline responsibilities of an existing seat, it belongs on your weekly Scorecard or job description, not on your Rock sheet.

For example, hitting a standard monthly sales quota or closing monthly financial books is part of running the business. Designing and implementing a brand-new automated commission structure or migrating to a cloud-based ERP system is working on the business. That is a Rock.

To test whether a project qualifies as a Rock, ask two questions: Does this deliver on a specific goal outlined in our 1-Year Plan on the V/TO, and would the business suffer strategic stagnation if we left it undone for ninety days? If the answer is no, it is merely everyday operational work. Keep Rocks reserved for the vital three to seven priorities that alter your operational capacity or drive clean growth.