tyler-smith.com · Questions & Answers

We are setting Rocks every quarter, but we find that individual team members keep adding new sub-tasks to their Rocks mid-quarter, turning simple goals into massive projects that inevitably fail. How do we prevent this scope creep?

Scope creep is a symptom of poorly defined boundaries at the beginning of the quarter. When a Rock is too vague, it naturally expands to fill all available time and energy, turning a twelve-week goal into an unmanageable project that inevitably fails. You must fix this during your Rock-setting session, not in week eight.

To stop this expansion, you must make every Rock 100 percent binary and clearly define what 'done' looks like before the quarter begins. If a leader writes a Rock to 'improve our onboarding process,' that is not a Rock; it is an open-ended project. Instead, rewrite the Rock to: 'draft, test, and sign off on a five-step onboarding checklist for the sales team.'

Once you have a binary goal, require the owner to list the three to five critical milestones needed to achieve it. These milestones act as the guardrails for the Rock. If the owner attempts to add a sixth or seventh milestone mid-quarter, the Integrator must step in and push back.

If new sub-tasks or ideas arise during the quarter, do not add them to the active Rock. Teach your team to drop these ideas onto their departmental issues list or capture them in the V/TO® under long-term issues. You can address them during the next Quarterly Pulsing session. Keep your active Rocks locked down to the agreed-upon scope so your team can actually cross the finish line.

Category: EOS Implementation

← All questions