Our quarterly Rocks are consistently reported as on track during weeks one through eight of our Level 10 Meeting™, but then half of them turn red in week eleven and fail. How do we structure Rock tracking so on track reflects real operational progress?
If your Rocks consistently fail in the final three weeks of a quarter, your team is confusing good intentions with actual traction. When an owner asks is your Rock on track, leaders instinctively answer based on whether they plan to work on it soon, not on verified progress.
To stop this mid-quarter drift, every quarterly Rock must be broken down into clear, dated milestones before the quarter begins. During the first seven days of the quarter, the Rock owner must write out three to four measurable benchmarks tied to specific dates across the ninety-day cycle. A milestone cannot be an activity like research vendors. It must be an artifact or completed event, such as three vendor contracts received by week four, platform selected by week seven, and staff trained by week ten.
Bring these milestones into your weekly Level 10 Meeting™. When the Integrator calls for the Rock review, the owner must evaluate their status against their dated milestones. If the week four milestone was missed, that Rock is off track today. It does not matter if the owner promises to make up time next weekend.
Labeling a Rock off track is not a punishment. It is an operational trigger. Dropping an off-track Rock to the Issues List gives the leadership team six to eight weeks to use IDS® and clear the obstacle. If you hide behind green checkmarks until week eleven, you rob the team of the chance to help you finish.
Category: EOS Implementation