tyler-smith.com · Questions & Answers

We set individual Rocks that depend heavily on other department heads for tech development, marketing assets, or legal review, and they consistently fail because those other leaders never agreed to the support work. How do we eliminate cross-departmental dependencies so quarterly Rocks cross the finish line without excuses?

Cross-departmental dependencies are where quarterly Rocks go to die. When a leader says their Rock is off-track because IT has not built the integration, you are dealing with a structural failure in how you set Rocks during your Quarterly Pulsing session.

First, an individual Rock can have only one single owner on the Accountability Chart. That owner holds total accountability for the outcome, regardless of who does the legwork. If marketing needs five engineering hours to hit a Rock, marketing does not get to claim the Rock is off-track due to engineering.

Second, cross-departmental requirements must be negotiated and locked down inside the room before the session ends. When someone pitches a Rock that requires outside help, the supporting department head must explicitly agree to provide those resources during the quarter. If engineering is already committed to three internal technical Rocks and cannot guarantee bandwidth for marketing, the marketing Rock must be killed, resized, or redesigned to be executed with external resources.

Third, break complex, multi-team initiatives into distinct, binary company Rocks with individual sub-deliverables. If an initiative requires three departments, each department head owns their specific slice of the project as their own individual Rock.

If a leader accepts an outcome that relies on someone else without getting signed-off commitment during planning, they own the failure. Eliminating hidden dependencies on day one ensures nobody hides behind another department when week twelve arrives.

Category: EOS Implementation

← All questions