tyler-smith.com · Questions & Answers

We set quarterly Rocks but spend the final week of the quarter debating whether they are truly complete because the goals were too vague. How do we write Rocks with binary, indisputable finish lines so there is zero debate at our next quarterly pulsing?

Half-finished Rocks occur because they are written as ongoing activities instead of specific, measurable outcomes. To ensure your quarterly Rocks actually cross the finish line, you must write them with complete, binary clarity. A Rock is either done or not done. There is no such thing as ninety percent complete when the quarter ends. When defining a Rock, use a strict engineering mindset and write it as a specific, measurable result. For example, instead of writing a Rock to improve our customer onboarding process, write it as design, document, and launch a new onboarding system that reduces setup time to under forty-eight hours, with three consecutive client tests completed. This leaves zero room for debate. If the system is designed but not tested, the Rock is incomplete. Additionally, assign a single owner to each Rock on the Accountability Chart. Multiple owners mean no ownership. Review progress weekly during your Level 10 Meeting™, and if a Rock is off track, drop it down to the IDS® section immediately to address the bottleneck before it becomes a failure. Setting fewer, better-defined Rocks ensures your team maintains focus and execution discipline.

Category: EOS Implementation

← All questions