Halfway through our quarterly cycle, several department leaders realize their Rocks are dead in the water because they are waiting on other departments. How should cross-functional dependencies be vetted during Rock setting to stop this mid-quarter bottleneck?

Question

Tyler Smith · Accepted Answer

Cross-functional bottlenecks during week six happen because teams write Rocks in silos during their quarterly session without testing operational bandwidth across departments.

A classic example is marketing committing to a new website launch that requires engineering to integrate the customer portal, while engineering has already committed all its capacity to an internal product upgrade. The marketing Rock stalls, engineering becomes defensive, and the leadership team wastes energy litigating who failed whom.

To prevent this, every proposed Rock must undergo a cross-functional dependency audit before the final Rock list is locked in on quarterly planning day. Follow this standard sequence:

- The Rock owner states the single objective and the specific finish line.
- The Integrator asks: 'Which other seats on the Accountability Chart must deliver work for this to be completed?'
- Every affected department head must review the required deliverable and explicitly state whether they have the capacity to deliver it within their own quarterly priorities.
- If a supporting department cannot commit the hours, the Rock must be rescoped, postponed to a future quarter, or adopted as a co-owned organizational priority where the supporting department takes a corresponding milestone.

Never allow shared ownership of a single Rock. Exactly one person owns the completion of the Rock, but all cross-functional inputs must be locked in as explicit milestones on day one.