Our leadership team sets Rocks with clear end goals, but halfway through the quarter, critical Rocks stall out because dependencies between departments were never mapped during session day. How do we prevent cross-department bottlenecks from killing our Rock completion rate?

Question

Tyler Smith · Accepted Answer

Cross-department Rock failures happen because leadership teams treat Rock creation as an individual exercise rather than a collective commitment. An Integrator or Operations leader writes a Rock to deploy new software, assuming the Sales leader will train their reps by week six, but that expectation was never explicitly agreed upon in the session room.

To eliminate this bottleneck, you must operationalize the handoffs before leaving your quarterly session. Every Rock must have one, and only one, owner on the Accountability Chart. However, once individual Rocks are drafted, the team must run a dependency check across the table. For every Rock requiring input, testing, or execution time from another seat, the Rock owner must state the exact deliverable and deadline needed from that peer.

The supporting leader must then evaluate their own capacity and quarterly priorities before committing. If the Sales leader cannot commit ten hours in week six because they are launching an enterprise campaign, the Rock must be rescoped immediately or designated as the top collaborative priority for both seats.

During execution, establish three to five measurable milestones for the quarter and set milestone deadlines. If a dependency is missed by even forty-eight hours, the Rock must be called off track in the next Level 10 Meeting so the team can IDS the constraint immediately. Hitting the eighty percent threshold requires confronting departmental friction in week three rather than offering excuses in week twelve.