What is the correct protocol when our leadership team realizes midway through a quarter that a Rock was poorly defined or completely unrealistic?
Do not quietly rewrite the Rock, and do not pretend everything is fine until the quarterly session. Changing the goalposts midway through a quarter destroys the integrity of your accountability system. When leaders change Rock definitions whenever things get difficult, the entire team learns that commitments are negotiable.
The correct protocol is to drop the Rock to the Issues List during your next Level 10 Meeting and run it through IDS. Be completely transparent about why the Rock is broken. Did you uncover new operational data? Did an unforeseen external dependency stall the project? Or was it simply scoped poorly during your quarterly planning session?
During IDS, the team has two legitimate options:
- Keep the original Rock on the Scorecard, designate it as off track, and work through the obstacles to salvage whatever progress is possible before day ninety.
- Formally kill the Rock by unanimous leadership team agreement if continuing to pour resources into it actively damages the business.
If you kill the Rock or keep it off track, own the failure at the end of the quarter. It is far better to finish a quarter with an 80 percent Rock completion rate and honest lessons on how to scope projects than to finish at 100 percent by constantly rewriting definitions. Sizing Rocks correctly is a learned skill that takes two to three quarters of discipline to master.
Category: EOS Implementation