Our market changes every few weeks. Should we choose a continuous-planning approach instead of EOS with its quarterly Rocks?
Do not reject EOS solely because it uses quarterly Rocks. First distinguish changing market information from a leadership team that repeatedly changes its mind. Those require different responses.
Rocks are the most important priorities for the quarter, not a requirement to ignore new information or stop making daily decisions. However, EOS does ask leaders to establish focus and accountability. If every new request displaces an existing commitment, adopting the terminology will not fix the underlying behavior.
Compare EOS with your continuous-planning alternative using actual examples:
- Which recent changes genuinely invalidated a priority?
- Which were urgent requests that could have been handled without resetting the company’s direction?
- Who authorized the changes, and did they acknowledge the work being displaced?
- Did frequent replanning improve outcomes or mainly keep everyone busy?
Bring those examples to the 90-Minute Meeting. Ask how an EOS-running leadership team would surface new information, resolve the issue, and make an explicit decision about an existing Rock. Do not assume the introductory meeting will redesign your planning process.
EOS's simplicity is useful only if it helps the team make clearer choices. A continuously updated plan is useful only if people still know what they own and what completion means.
My recommendation is to choose the approach that combines responsiveness with dependable commitments. After the meeting, agree on what would justify changing a priority and how your team would communicate the consequences. Neither system should become an excuse for rigidity or constant churn.
Category: EOS vs. Other Operating Systems