Our quarterly Rocks are well defined, but when someone reports their Rock as off track in week six of the Level 10 Meeting, they usually brush it off and say they will catch up. How do we use IDS to actually rescue an off-track Rock before it turns into a failed quarter?
In a healthy Level 10 Meeting, an off-track Rock is not an informative status update. It is an immediate alarm bell that demands an issue be dropped to the bottom of the agenda. The moment a leader says off track, the Integrator must write that Rock onto the Issues List without allowing any storytelling, excuses, or defensive explanations during the Rock review segment.
When you reach the IDS portion of the agenda, tackle the off-track Rock with urgency. The goal of IDS is to identify the real root cause of the delay, discuss practical solutions, and solve the bottleneck so the Rock can return to on track by the following week.
Start by probing for the true obstacle. The root cause is rarely a lack of effort. It usually falls into one of three buckets:
- Resource conflict, where operational fires or competing department priorities hijacked the owner's time.
- Unrealistic milestones, where the sequence of sub-tasks was poorly planned during quarterly planning.
- Cross-departmental dependencies, where the Rock owner is stuck waiting on another leader who has not delivered their part.
Once the root cause is named, the team must decide on a definitive action plan. That might mean temporarily shedding non-essential operational duties, reassigning a milestone to another team member, or reprioritizing department resources. What you must never do is accept off track as an acceptable condition for two consecutive weeks. If a Rock stays off track for fourteen days without a solution, your team is failing to IDS properly.
Category: EOS Implementation