During our weekly Level 10 Meetings, our Rocks are almost always reported as on track, but then three of them fail in week twelve. How do we expose Rock drift before it is too late to fix?

Question

Tyler Smith · Accepted Answer

Rock failures in week twelve happen because teams treat the weekly Rock review as an exercise in optimism rather than an objective status check. In a Level 10 Meeting™, a Rock owner often reports on track simply because they intend to work on it soon.

To eliminate this blind spot, force clear milestones during the quarterly planning session. A ninety-day Rock should have verifiable milestones at day thirty and day sixty. For example, if a Rock is to launch a new estimating software, the day thirty milestone might be selecting the vendor, and the day sixty milestone might be completing staff training.

During the weekly Level 10 Meeting™, the review is strictly binary. The leader says on track or off track. There is no explanation permitted during the reporting phase. If the owner has missed their day thirty milestone, the Rock is officially off track, regardless of their good intentions. It immediately gets dropped down to the Issues List for IDS®.

Once an off-track Rock is on the Issues List, the team spends five to ten minutes diagnosing the bottleneck. Does the owner lack time, budget, or cross-functional support? You solve the obstacle in week four or five when you can still recover, rather than discovering a catastrophe during the final week of the quarter. Honesty in week five is what protects your ninety-day completion rate.