tyler-smith.com · Questions & Answers

Our quarterly Rock completion rate hovers around sixty percent, and leaders always show up at the ninety-day mark with eighty percent done excuses. What specific mechanism forces Rocks across the finish line before day ninety?

An eighty percent finished Rock is zero percent finished. In the EOS framework, a Rock is strictly binary: you either achieved the specific outcome, or you did not. When a team regularly lands at sixty percent, the breakdown is almost always a failure of definition at the beginning and a failure of tracking in the middle.

First, ban vague Rock titles. Never allow a Rock called Improve Client Onboarding or Update Financial Reporting. Those are ongoing responsibilities, not quarterly projects. A valid Rock must have a crystal-clear, measurable definition of done. Rephrase those Rocks as Client Onboarding Process Documented with Five Loom Videos and Signed Off by Operations, or New Weekly Cash Flow Dashboard Live and Tested with Three Weeks of Data. If a third party cannot look at the outcome on day ninety and definitively say yes or no, the Rock was poorly written.

Second, enforce the milestone rule. On the day a Rock is set, the owner must identify three to four clear monthly checkpoints. A ninety-day project cannot live as a single giant task.

Third, kill polite reporting in the weekly Level 10 Meeting. During the Rock review, the response is only on track or off track. If a leader says on track for eight weeks and suddenly drops the Rock in week ten, that is a breakdown in integrity. The moment a milestone is missed, mark the Rock off track and drop it down to the IDS list. Solving the roadblock in week four is how Rocks get finished in week twelve.

Category: EOS Implementation

← All questions