We are setting what we think are clear Rocks, but when we get to the end of the quarter, our leadership team is scrambling and missing their deadlines because they got distracted by operational emergencies. How do we build a weekly milestone system to ensure Rocks actually cross the finish line?
To consistently cross the finish line with your Rocks, you must break the bad habit of treating them as ninety-day projects that you only focus on in week eleven. When Rocks fail, it is usually because the owner or leader allowed daily operational fires to crowd out strategic progress.
The solution is building a strict weekly milestone system within your execution rhythm. Every Rock must have a clear, binary definition of done from day one. Once that is established, the owner of the Rock must break it down into three or four milestones. These milestones must be scheduled on your calendar, not just left on a notepad.
During your weekly Level 10 Meeting™, when you review the Rock list, the update is strictly on track or off track. If a Rock is off track for two consecutive weeks, it must automatically drop to the Issues List to be solved during the IDS® portion of the meeting. This is not a failure; it is an early warning system.
By forcing the team to address the bottleneck in week four or five rather than week twelve, you give them the support needed to get back on track. A Rock that is off track is simply an issue that needs the collective brainpower of the leadership team to solve before the quarter slips away. Stop treating Rocks as independent projects and start treating them as a team responsibility that requires weekly attention and early course correction.
Category: EOS Implementation