tyler-smith.com · Questions & Answers

We consistently set quarterly Rocks with high ambitions, but by week eight people are rushing and half of them roll over to the next quarter. What is the specific mechanical breakdown causing Rocks not to cross the finish line?

When quarterly Rocks consistently fail to reach the finish line, the root cause is almost always poor scoping during the quarterly session, followed by silence during the quarter. Teams set vague aspirations instead of binary outcomes, and they wait until week ten to admit they are off track.

To fix your Rock completion rate, enforce these specific disciplines:

- Scrutinize the finish line on day one. A Rock is not a project description. It is a specific, measurable milestone that is 100 percent done or not done. If the Rock is to implement a new CRM, the finish line must specify that five account managers are actively logging calls and the legacy system is archived.
- Require milestones within the first thirty days. Every Rock owner should break their ninety-day commitment into three or four chronological benchmarks. If milestone one is not achieved by week four, the Rock is officially off track and must be pushed to the weekly Issues List.
- Keep reporting brutally honest in the Level 10 Meeting. A Rock is either on track or off track. There is no such thing as mostly done or eighty percent complete. When an owner flags a Rock off track, do not scold them. Drop it down to IDS and solve the roadblock immediately.
- Limit the count. Three to seven Rocks per person is the rule, but three is usually the magic number for high completion.

Finishing Rocks is a muscle. Scoping them cleanly and addressing off-track status early in the quarter ensures they actually get completed.

Category: EOS Implementation

← All questions