What specific protocol should an Integrator enforce when an unexpected operational emergency mid-quarter threatens to derail multiple leadership team Rocks?

Question

Tyler Smith · Accepted Answer

Mid-quarter operational emergencies are inevitable. The difference between companies that finish their quarterly Rocks and those that fail is how the Integrator manages the boundary between daily fires and strategic commitments.

When a crisis erupts, teams instinctively abandon their Rocks to jump into firefighting mode. The Integrator must stop this knee-jerk reaction by executing a disciplined three-step protocol:

- First, route the emergency directly to the Issues List of the weekly Level 10 Meeting. Do not allow impromptu hallway panic or endless emergency Slack threads to derail daily execution.
- Second, use IDS to determine whether the emergency is truly an existential threat or simply noise caused by a broken Core Process or seat vacancy. Most perceived emergencies can be contained without sacrificing strategic priorities.
- Third, if the crisis legitimately requires immediate leadership bandwidth, the Integrator must force explicit trade-offs. The team must identify which specific Rock will be paused, recalibrated, or reassigned.

A Rock is a binary 90-day commitment, not a casual to-do list item. An Integrator never allows team members to quietly walk away from a Rock because they got busy. By containing crises within the IDS framework and actively protecting Rock bandwidth, the leadership team maintains operational momentum even during turbulent quarters.