Our leaders consistently report their quarterly Rocks as on track during the weekly Level 10 check, only to drop them to off track in week ten when it is too late to fix. How do we force honest, predictive Rock status reporting?

Question

Tyler Smith · Accepted Answer

Reporting a Rock as on track during weekly pulses when milestones are falling behind is not optimism; it is an accountability failure. A Rock is only on track if the owner has absolute confidence that all ninety-day milestones will be completed by the final day of the quarter.

To prevent week-ten surprises, redefine what on track means inside your Level 10 Meeting. Apply these operational rules during the weekly Rock review:
- Enforce milestone milestones. Every Rock must have clearly dated interim milestones established during quarterly planning. If a week-four or week-six milestone is missed, the Rock is automatically declared off track during the Level 10 review.
- Drop off-track Rocks immediately. When a Rock owner states "off track," the Integrator must drop it to the Issues List without debate. The purpose of flagging a Rock as off track is not to penalize the owner; it is to leverage the brains of the leadership team during IDS to get it back on schedule.
- Remove the stigma of calling a Rock off track in weeks four through eight. A healthy leadership team expects multiple Rocks to hit obstacles mid-quarter. What is unacceptable is keeping a struggling Rock hidden until week ten, when no amount of team problem-solving can rescue it.
- Hold the Integrator accountable for probing vague statuses. If an owner says "on track" but everyone knows the project is behind schedule, the Integrator must challenge it: "You missed your software testing deadline on Friday. How is this Rock still on track?"

Honest reporting creates early intervention, which turns doomed projects into completed Rocks.