When a quarterly Rock requires cooperation from multiple department heads, who owns the outcome and how do we prevent finger-pointing if milestones are missed?

Question

Tyler Smith · Accepted Answer

A quarterly Rock must have exactly one owner. The moment two people share ownership of a Rock, nobody owns it. Shared accountability always leads to finger-pointing when the deadline arrives and the deliverable is incomplete.

When a Rock touches multiple departments, assign it to the seat on the Accountability Chart that has the highest operational stake in its completion. That owner is responsible for the final outcome. They do not have to do every task themselves, but they are fully accountable for driving the project, securing cross-departmental buy-in, and hitting every milestone on time.

To make cross-functional Rocks work, the owner must map out clear, interim milestones during the first two weeks of the quarter. If marketing needs to provide lead generation assets before engineering can build an automated workflow, those dependencies must be defined immediately with firm drop-dead dates.

When an external dependency slips, the Rock owner must drop that breakdown onto the Issues List during the next weekly Level 10 Meeting. They cannot wait until week eight to announce that another department stalled their work. By raising the issue early in IDS, the leadership team can remove the bottleneck and realign resources before the 90-day deadline is compromised.