Our leadership team consistently hits a wall around week seven of the quarter, and Rocks that were marked on track suddenly turn red in week ten. How do we keep Rocks moving through the messy middle of the 90-day cycle?
The mid-quarter collapse happens because teams treat the weekly Level 10 Meeting Rock review as a status report instead of an early-warning radar. Leadership teams get polite, say their Rocks are on track out of pride, and hide behind optimistic forecasts until week ten when failure is mathematically guaranteed.
To eliminate this pattern, enforce radical intellectual honesty during the weekly reporting section. A Rock is either on track or off track. There is no such thing as mostly on track. If a leader encounters any obstacle that threatens the deadline, or if they have completed zero milestones over the prior two weeks, they must call it off track immediately.
Calling a Rock off track is not an admission of failure. It is simply a trigger to drop the Rock to the bottom of the weekly Issues List. When you get to the IDS portion of the meeting, solve the obstacle as a team. The owner of the Rock does not have to solve it alone. The other leaders step in to remove roadblocks, reallocate resources, or adjust milestones.
Additionally, every Rock should have thirty-day and sixty-day milestones mapped out on session day. During weeks four and eight, the Integrator should run a quick milestone audit. If thirty-day deliverables are unfinished in week five, the Rock is officially off track and requires immediate attention. Weekly transparency combined with ruthless milestone accountability keeps Rocks from stalling in the messy middle.
Category: EOS Implementation