Our leadership team regularly marks Rocks as on track during weekly meetings, only for those same Rocks to fail or get pushed into the next quarter during week twelve. How do we fix our weekly tracking so off-track Rocks get salvaged before time runs out?

Question

Tyler Smith · Accepted Answer

The issue is psychological safety disguised as false optimism. Leadership teams hate admitting that a Rock is off track in week four or six because they treat it as an admission of personal failure. Instead, they say on track, hoping they will work late in week eleven to catch up. That is how quarters get wrecked.

You must enforce a strict cultural definition: marking a Rock off track is not a punishment. It is an operational alert. The entire purpose of the Level 10 Meeting Rock review is to find friction early so the team can help solve it.

During the Rock review, the Integrator must maintain zero tolerance for vague updates. Team members are only allowed to say on track or off track. No explanations, no storytelling, and no excuses. If a Rock is off track, drop it down to the Issues List immediately without debate.

During the IDS portion of the meeting, dig into why the Rock stalled. Is the owner stuck on an internal bottleneck? Do they lack cross-functional resources from operations or tech? Does the scope need to be adjusted?

By identifying off-track status in week four, you give the leadership team eight full weeks to remove the roadblock, reallocate resources, or adjust the milestone path. When you celebrate leaders for proactively reporting off-track Rocks early, you kill the eleventh-hour scramble and ensure your ninety-day commitments actually cross the line.