Our quarterly Rocks frequently stall when they require cooperation between multiple departments, leading to finger pointing at the end of the quarter. How do we assign and enforce sole ownership for collaborative, cross-functional Rocks?
Cross functional Rocks fail because shared responsibility equals zero accountability. When a Rock requires input from both Sales and Operations, it is common to assign it to both heads. This is a fatal mistake that guarantees a weak finish.
To get these Rocks across the finish line, you must designate one single owner on your leadership team. This person is not necessarily doing all the work, but they own the ultimate outcome. They are the single point of accountability on your Accountability Chart.
The owner must define the sub tasks and assign them to the other team members as weekly milestones. If the head of Sales owns a Rock to implement a new customer portal, they must treat the head of Operations as an internal vendor. The Sales head is responsible for securing the necessary inputs, scheduling the working sessions, and raising the red flag in the Level 10 Meeting™ if another department is stalling the project.
Before you finalize your quarterly Rocks, run a quick dependency check. Ask each Rock owner if they require assets, time, or approvals from other team members to cross the finish line. If they do, those commitments must be agreed upon right then. By forcing a single point of accountability and aligning dependencies early, you eliminate the gray areas that allow critical projects to slip.
Category: EOS Implementation