tyler-smith.com · Questions & Answers

Even when our Rocks are scoped properly, our leaders drop the ball around week six because day-to-day firefighting takes priority. How do we manage the weekly rhythm inside the Level 10 Meeting so Rocks actually cross the finish line on day 90?

Writing clean, binary Rocks during session day only sets up the starting line. Crossing the finish line on day 90 depends entirely on the accountability rhythm inside your weekly Level 10 Meeting.

During the weekly Rock Review, each leader states only whether their Rock is on track or off track. There is no middle ground. The fatal mistake teams make is tolerating false optimism. If a leader has a Rock with five milestones and by week six they have completed none of them, that Rock is off track, regardless of how confident the leader feels. The Integrator must challenge passive reporting and immediately drop lagging Rocks down to the Issues List.

When an off-track Rock is addressed in IDS, the goal is not to shame the owner. The goal is to identify what operational drag is blocking them. Ask the leader directly: what operational friction is preventing you from spending your allocated white space on this project? Is an operational crisis eating your calendar? Are you waiting on another department? Do you need to delegate lower-tier tasks to free up four hours this week?

By treating an off-track Rock as a systemic bottleneck rather than a personal failure, the leadership team can remove obstacles, reallocate internal resources, or shift daily tasks off the owner plate in real time. If you wait until week ten to rescue a stalled Rock, it is dead. Catching off-track status in week four or five gives you the runway needed to course-correct and achieve an 80 percent or higher team completion rate every single quarter.

Category: EOS Implementation

← All questions