We are setting quarterly goals, but our leadership team continuously writes Rocks that are too vague to track, leading to arguments at the end of the quarter about whether they were actually completed. How do we enforce a strict, measurable standard for writing Rocks during our planning sessions?
The failure to finish Rocks almost always begins in the planning room. When leadership teams write Rocks, they often use soft, subjective verbs like streamline, improve, evaluate, or oversee. These are activities, not outcomes. By the end of ninety days, you will inevitably argue over whether the goal was actually met.
To fix this, every Rock must pass the binary test. It is either done or not done, with zero room for interpretation. When a team member proposes a Rock, the rest of the team must ask: What does done look like?
Define the exact endpoint before you leave the quarterly session. Instead of write a new sales playbook, the Rock should be draft, test, and obtain leadership approval on a sales playbook with five core chapters. Instead of improve customer satisfaction, the Rock must be achieve a net promoter score of seventy-five or higher based on at least sixty customer surveys.
Your Integrator must hold the line on this during the session. If a Rock cannot be measured with a simple yes or no on day ninety, do not write it down. If you struggle to define the metric, the Rock is not ready, or you are trying to solve an operational issue under the guise of a strategic goal. Keep refining the language until there is absolutely no gray area.
Category: EOS Implementation