When setting quarterly Rocks, how do we prevent individual owners from overcommitting to cross-departmental projects that collapse because other leaders never agreed to support the workload?

Question

Tyler Smith · Accepted Answer

Cross-departmental Rock failures are usually born during the quarterly session, not during mid-quarter execution. An ambitious leader commits to a major software rollout, product launch, or sales initiative, assuming the operations, finance, or marketing teams will absorb the secondary work without question. When daily operational fires hit, the supporting leaders naturally prioritize their own commitments, leaving the primary Rock owner stranded and off track by week six.

To prevent this breakdown, you must enforce a strict dependency check during the Rock-setting phase of your quarterly session before any Rock is officially finalized. Every Rock owner must answer one question: what specific hours, tools, or deliverables do you require from other seats on this Accountability Chart to cross the finish line?

If another leader cannot formally commit the capacity, the room has three choices:
- The supporting leader adopts a complementary Rock that officially commits their department resources.
- The primary Rock is rescoped to eliminate external dependencies entirely.
- The Rock is postponed until organizational capacity aligns.

Never allow a leader to leave the room with a Rock that relies on uncommitted goodwill. Binary accountability means the owner owns the outcome, which requires verified control over the inputs before the quarter begins.