Halfway through the quarter, a massive operational disruption struck our business, and several leaders want to drop or swap their agreed-upon Rocks. How do we handle mid-quarter disruptions without destroying execution accountability?
Disruptions happen, but abandoning Rocks mid-quarter is the fastest way to destroy traction and teach your organization that quarterly commitments are optional. The ninety-day cycle exists specifically to protect your company from reactive knee-jerk decisions.
When a major event occurs, follow a strict protocol. Bring the issue directly to the next Level 10 Meeting™ and drop it onto the Issues List for IDS®. Do not make a unilateral decision during the week. In the meeting, the leadership team must evaluate whether this disruption is an existential crisis that genuinely invalidates company strategy, or simply a loud fire that can be managed within normal operational capacity.
In ninety percent of situations, the Rock should stand. The owner may need to re-delegate day-to-day firefighting to their team to protect their milestone delivery. If the landscape has genuinely altered and continuing work on a Rock would actively harm the business, the leadership team must agree collectively to kill it.
However, you never erase the Rock or secretly swap in a convenient substitute. You mark the Rock as dropped or off-track, document the strategic reason why, and focus on surviving the disruption. When you refuse to rewrite history, you protect the sanctity of the EOS® quarterly pulse and prevent leaders from treating external surprises as an automatic pass to miss their goals.
Category: EOS Implementation