Our quarterly Rocks always show as on track in our weekly meetings until week nine or ten, and then half of them suddenly fail. How do we catch struggling Rocks early enough to save them before the quarter ends?
This pattern is known as the watermelon Rock: green on the outside all quarter, but bright red on the inside when you cut into it at week ten. It happens when leadership teams treat Rock reporting as a status update rather than a trigger for team problem-solving.
During your weekly Level 10 Meeting, the Rock review should take less than five minutes. Each owner says only one of two phrases: on track or off track. There is no commentary allowed. However, human nature tempts leaders to say on track because they plan to work on the Rock over the weekend or believe they can make up lost time next week. That optimism kills execution.
Fix this by enforcing two strict rules during Rock creation and weekly pulsing:
- Every Rock must have clear thirty-day and sixty-day milestones agreed upon during your quarterly session. If milestone one is not finished by day thirty, that Rock is mathematically off track, regardless of the owner optimism.
- Establish a culture where declaring off track is rewarded, not penalized. When a Rock goes off track, it immediately drops to the bottom of the Issues List. The team then uses IDS to solve whatever obstacle is in the way.
If a leader waits until week ten to admit their Rock is off track, hold them accountable for failing to raise the issue in week four or five when the team still had time to help. A Rock that drops off track early and gets fixed is a normal part of business. A Rock that stays quietly green until it dies at quarter-end is a breakdown in team trust.
Category: EOS Implementation