When a critical initiative spans both sales and operations, how do we structure quarterly Rocks so one seat retains absolute accountability without the project stalling from cross-department dependencies?

Question

Tyler Smith · Accepted Answer

Cross-department initiatives stall when leadership teams assign dual ownership. The moment two names appear next to a Rock, nobody owns it. If sales blames operations for delayed technical input, and operations blames sales for shifting scope, the quarter ends with zero traction.

The rule on the Accountability Chart is absolute: only one person can own a Rock. You must decide which seat owns the ultimate deliverable. If the Rock involves rolling out a new quoting platform, decide whether the sales leader owns the user adoption outcome or the operations leader owns the technical rollout. The owner is solely accountable for completing the milestone on time, regardless of how many departments contribute work.

Break the cross-functional work down into clear milestones before the quarter starts. The Rock owner must establish specific deadlines for supporting deliverables from peer leaders. If the sales leader owns the Rock, they must secure a formal commitment from the operations leader during quarterly planning for specific technical milestones by week five.

If a peer fails to deliver their supporting milestone, the Rock owner cannot wait until week nine to complain. They must drop the blocker onto the Level 10 Meeting Issues List immediately and use IDS to resolve the logjam. In an EOS implementation, owning a Rock does not mean doing all the labor alone. It means being the single throat to choke for ensuring the finish line is crossed.