tyler-smith.com · Questions & Answers

Our leadership team is great at setting ambitious quarterly Rocks, but we struggle to get them across the finish line, often declaring them ninety percent complete at the end of the quarter. How do we break this cycle of nearly done and ensure our Rocks are fully executed and closed out on time?

Getting Rocks to one hundred percent completion is not a matter of effort; it is a matter of definition and weekly tracking. Many leadership teams fail to cross the finish line because they write vague, activity-based Rocks rather than objective-based ones. A Rock is only done when it meets a binary, pass-fail test. If there is any room for interpretation, you have designed it poorly.

To fix this, every Rock must have a clear, written description of what done looks like on day one of the quarter. This is your definition of done. Once that is locked in, the weekly Level 10 Meeting™ is your primary tracking mechanism. The status of a Rock is either on track or off track. There is no such thing as seventy-five percent done during week eight. If a Rock is off track, it must immediately be dropped down to the IDS® portion of your agenda.

The Integrator must enforce this strictly. When a Rock goes off track, the team must solve the underlying bottleneck rather than accepting excuses. Additionally, you should assign milestone dates to each Rock. Break the ninety-day goal into thirty-day and sixty-day deliverables. If a leader misses their thirty-day milestone, the Rock is officially off track. This visibility prevents the typical end-of-quarter rush.

Finally, remember that setting fewer Rocks increases your completion rate. If your team is consistently failing to finish, you are likely taking on too much. Limit your leadership team to three to five team Rocks per quarter and hold each other ruthlessly accountable to the binary completion criteria you established on day one.

Category: EOS Implementation

← All questions