When a critical department head falls behind on their Rocks three weeks after a quarterly session, how do we use our weekly Level 10 Meeting to course-correct before it becomes a rescue operation requiring your intervention?

Question

Tyler Smith · Accepted Answer

When a leader falls behind on their Rocks, you must address the issue immediately within your weekly Level 10 Meeting rather than waiting for our next quarterly session. The beauty of the ninety-day execution cycle is that it exposes performance gaps in real-time. If a Rock is off track, it must be dropped down to the issues list. During the IDS portion of your meeting, the team must identify the root cause of the delay. We do this by moving through Kolb's learning cycle; we analyze the concrete experience of why the milestone was missed, reflect on the operational bottlenecks, and agree on a plan for active experimentation to get it back on schedule. We also shift our language to drive personal accountability. Instead of allowing the department head to use passive verbs such as trying to finish or working on it, we ask them to own the outcome. We encourage them to state clearly what support they need from the team to hit their target. If the issue is a systemic lack of capacity, we use a Strategic Pause to evaluate if we need to temporarily reallocate resources. By addressing the bottleneck collectively and transparently every single week, you prevent a minor delay from compounding into a quarterly failure.