When a quarterly Rock requires heavy execution from multiple departments, how do we establish singular accountability so the Rock does not collapse into cross-functional finger-pointing?

Question

Tyler Smith · Accepted Answer

A quarterly Rock can have multiple contributors, but it must have exactly one owner. When two or three leadership team members share responsibility for a Rock, nobody is truly responsible. The moment execution hits a roadblock, shared ownership turns into finger-pointing and missed deadlines.

The owner of the Rock must be the individual whose seat on the Accountability Chart owns the final outcome. That person is exclusively responsible for scoping the Rock, setting milestones, securing commitments from other departments, and declaring whether the Rock is on track or off track during weekly Level 10 Meetings.

To eliminate cross-departmental friction before the quarter starts, the Rock owner must establish clear sub-deliverables with other department leaders during the first two weeks of the quarter. If the Rock owner needs ten hours of developer time from Engineering or five marketing briefs from Marketing, those commitments must be locked down early. If an operational dependency cannot be resolved between two seat holders, the Rock owner must drop the dependency onto the Level 10 Meeting Issues List immediately rather than waiting for week eight.

During weekly Level 10 Meetings, the status call is strictly binary. The Rock owner says on track or off track. They do not get to say off track because another department was slow. If another department is bottlenecking the work, that bottleneck is an operational issue to be IDSed right then. The single owner remains accountable for delivering the finished, binary result by day ninety.