tyler-smith.com · Questions & Answers

During our weekly Rock review, one of our leaders consistently reports their Rock as on track, but when the end of the quarter arrives, they admit it is not done. How do we use our weekly Level 10 Meeting to catch these false-positive updates before we hit the quarter-end wall?

A leader who repeatedly claims their Rock is on track when it is actually lagging is violating the core team trust required in an EOS® business. This behavior usually stems from a fear of looking incompetent, but it ultimately results in missed quarterly goals and operational friction. Your weekly Rock review must be a source of brutal truth, not wishful thinking.

To fix this, you must change how you define on track during your weekly Level 10 Meeting™. A Rock is only on track if the specific milestones for this week are fully complete. If a leader has a Rock to document all operational processes, and they have not written a single page by week six, that Rock is off-track, even if they plan to pull an all-nighter in week eleven.

The facilitator must ask for proof when updates seem vague. Instead of accepting a simple yes, ask: What specific milestone did you complete this week to keep that Rock on track?

If they hesitate or admit they are behind on their weekly milestones, the Rock must instantly be marked off-track and dropped to the Issues List for IDS®. There is zero shame in a Rock being off-track mid-quarter. The shame is in hiding it until it is too late to solve. Force the truth out early so the team can help them cross the finish line.

Category: Level 10 Meetings

← All questions