When an executive realizes in week four or five that a quarterly Rock is falling off track, what is the exact operational protocol to salvage or recalibrate it?

Question

Tyler Smith · Accepted Answer

When an executive realizes in week four or five that a quarterly Rock is off track, the worst reaction is to stay silent and attempt a frantic sprint in week eleven. That behavior guarantees failure. The purpose of tracking Rocks in every weekly Level 10 Meeting is to identify trouble while there is still enough runway to correct course.

The moment a Rock owner identifies a blocker, they must drop the status to off track during the weekly Level 10 Meeting. That status change is not a personal failure or an invitation for an excuse. It is an operational trigger that pushes the Rock onto the Issues List for immediate IDS.

When resolving an off-track Rock, the leadership team must choose one of three distinct actions:
- Reallocate team resources. If the owner lacks the bandwidth or internal support, assign specific sub-tasks to other team members who have capacity that week.
- Clear an external dependency. If the Rock is blocked by a vendor, client, or cross-department handoff, the Integrator steps in immediately to remove the barrier.
- Descope the deliverable. If the original definition was overscoped or predicated on flawed assumptions, adjust the milestone criteria right there in the room while maintaining the core intent of the objective.

Never roll an off-track Rock into the next quarter without an honest IDS session. Salvaging a Rock mid-quarter demands radical transparency, tight accountability, and an Integrator who refuses to let pride compromise quarterly delivery.