When a quarterly Rock requires execution from peers across different departments, the designated Rock owner often struggles to hold colleagues accountable for their milestones. How do we ensure cross-functional Rocks actually finish on time without creating political friction?

Question

Tyler Smith · Accepted Answer

Rocks stall when accountability is diffused across multiple departments. When everyone is responsible for a project, nobody is responsible. Every quarterly Rock must have exactly one owner on the leadership team. That person holds the single throat to choke for its delivery, regardless of how many other departments must touch the work.

To finish cross-functional Rocks reliably:

- Define binary completion at the start: Clarify the exact end state in measurable terms. Write out what done looks like on day ninety so there is zero debate at quarter end.
- Establish interim handoff dates during planning: Break the thirteen-week quarter into strict milestone dates. If marketing must deliver copy by week four so IT can build the portal by week eight, record those milestone commitments explicitly.
- Raise roadblocks instantly in the Level 10 Meeting™: The Rock owner does not need managerial authority over peers. They have the EOS® process. If a peer misses a week-four milestone, the Rock owner flags the Rock as off-track during the weekly review and drops it to the Issues List.

During IDS®, the Integrator addresses the bottleneck immediately. The Rock owner does not plead with their peer offline; the team solves the capacity or priority issue openly. When leaders know cross-department handoffs are monitored weekly, Rocks finish.