An unexpected market shift just threatened our core revenue model midway through the quarter. Does EOS allow us to scrap our quarterly Rocks mid-cycle, or are we locked into our commitments until the next offsite?

Question

Tyler Smith · Accepted Answer

EOS is designed to deliver focus and traction, not dogmatic rigidity. While the ninety-day world protects leadership teams from the chaos of weekly shiny-object syndrome, it is not a suicide pact. When an existential market shift occurs, sticking your head in the sand to preserve arbitrary quarterly goals is bad leadership.

If a macro change renders an active Rock irrelevant or counterproductive, you do not need to wait until the next quarterly offsite session to adjust. However, you must handle the change with discipline so you do not reopen the door to constant mid-quarter churn.

Bring the issue directly to your next weekly Level 10 Meeting. Use the IDS process to analyze the market threat thoroughly. Do not let one leader unilaterally abandon their commitment; the entire leadership team must evaluate whether the original Rock still serves the 1-Year Plan or if resources must be urgently redirected.

If the leadership team reaches consensus that the current environment makes the Rock obsolete, formally agree to drop it. Document the decision clearly in the meeting notes, archive the Rock, and establish a new ninety-day priority that directly tackles the threat. Assign a single owner and clear milestones for the remaining weeks of the quarter.

Changing Rocks mid-quarter should be an exceptional event reserved for genuine structural threats, not an escape hatch for poor project planning. When handled transparently through the Level 10 agenda, adjusting mid-cycle reinforces the strength of the operating system rather than undermining it.