Our leadership team constantly writes Rocks that depend on outside vendors or cross-departmental teams, and they stall out by week seven. How do we scope and structure Rocks during quarterly planning so they are insulated from external bottlenecks?

Question

Tyler Smith · Accepted Answer

A Rock stalls midway through the quarter when the owner scopes the end goal instead of scoping the specific operational deliverable they can control within ninety days. If your Rock requires a vendor to finish software development or requires three other departments to overhaul their workflows, you have created a wish list rather than an executable priority.

Fix this during quarterly planning by applying two strict scoping rules:

- Scope the Rock strictly to the milestone your team directly controls. If you are hiring an agency to rebuild your website, the Rock cannot be "Launch new website." The agency controls the build schedule, which introduces outside risk. The Rock must be "Approve wireframes, deliver brand assets, and sign off on technical specs for website." That deliverable is completely within your internal team control.

- Map critical path dependencies during the session, not in week six. When an executive presents a proposed Rock, the Integrator must immediately ask: Who else must do work for this to cross the finish line? If the marketing head needs forty hours of engineering time, the engineering seat must explicitly commit to that resource allocation right then. If engineering cannot commit the capacity, the Rock must be rescoped or abandoned.

Furthermore, every Rock owner must break their ninety-day objective into three thirty-day milestones by week two of the quarter. If a vendor or internal dependency slips in the first thirty days, the Rock owner must drop it to the Level 10 Issues List immediately. Do not wait until week seven to acknowledge that an outside party is killing your traction.