How do we prevent leadership team members from passing the buck when a single quarterly Rock requires deliverables from multiple department seats to cross the finish line?
A Rock with two owners is a Rock with no owners. The most common excuse for a failed cross-functional initiative is that one seat was waiting on another seat. In EOS, shared ownership is forbidden. Every Rock must have exactly one owner on the leadership team who is solely accountable for crossing the finish line.
When a Rock depends on deliverables from other seats, follow this framework:
- The Rock owner must define every cross-department dependency and deadline during the quarterly planning session before the Rock is officially locked.
- The contributing department leaders must publicly agree to those interim deadlines in the room.
- If a supporting deliverable is substantial, the supporting leader must take an individual Rock or an explicit milestone within their own seat to support the primary company Rock.
During the weekly Level 10 Meeting, the Rock owner reports on track or off track. They are never allowed to say they are off track because another department failed them. If a colleague misses a supporting milestone, it is the Rock owner's responsibility to drop that bottleneck onto the Issues List immediately for IDS. You do not wait until week nine to announce that operations never gave you the data marketing needed. Own the outcome, identify the friction early, and solve it as a team.
Category: EOS Implementation