EOS Rock Dependencies: Put Off-Track Work on the Table
EOS Rock dependencies can involve several departments, even when one person owns the quarterly priority.

An operations leader may own a new scheduling process. Finance must confirm the reporting fields. A department manager must provide test cases. The owner must resolve a policy decision.
If those contributions remain informal, the Rock owner may spend weeks following up without a useful place to resolve the delay.
The priority needs a clear owner. Its dependencies also need to be visible.
Keep the status report honest
In EOS, Rocks are priorities for a 90-day period. EOS Worldwide’s guidance places an on-track or off-track report in the weekly Level 10 Meeting, with off-track issues moving to the Issues List for problem solving.
That structure depends on an honest assessment. A contributor saying they expect to respond soon does not, by itself, establish that the priority will finish on time.
The Rock owner should consider the remaining work, the decisions still needed and the time available. If the required result is at risk, report it accordingly.
EOS Worldwide also addresses the danger of optimistic on-track reporting and suggests intermediate milestones. A useful companion is a short record of the inputs needed to reach those milestones.
Name EOS Rock dependencies precisely
“Waiting on Finance” leaves too much unexplained. It does not say what Finance must provide or whether the request has even been accepted.
A clearer dependency might read: “The controller must confirm which job-cost codes the test schedule will use by Tuesday so the operations team can run Thursday’s pilot.”
That sentence identifies an output, a contributor, a date and a consequence.
Use a short record with these fields:
Rock and accountable owner.
Required input or decision.
Person responsible for supplying it.
Date needed and date agreed.
Consequence if it arrives late.
Escalation point if the commitment is at risk.
The distinction between “date needed” and “date agreed” matters. A date entered by the Rock owner is a request until the contributor accepts it or negotiates a workable alternative.
Resolve competing priorities directly
Suppose the controller is also responsible for month-end close. They may understand the scheduling request and still lack capacity to meet the proposed date.
That is a leadership decision to resolve. The team might adjust the pilot sequence, narrow the test, assign support or change the timing. Each option has a cost.
Repeated reminders cannot make that tradeoff for the leadership team. The Rock owner should raise the actual conflict early enough for a decision to matter.
This also protects relationships. A factual discussion of two competing commitments is more useful than allowing one department to conclude that the other does not care.
Bring a clear issue into problem solving
The dependency record supports preparation. It should not turn the short Rock Review into a detailed project meeting.
When an off-track Rock requires problem solving, bring a clear description of the issue and the decision needed through the team’s established EOS process.
For example: “The test cannot start until the codes are confirmed. The available Finance resource cannot complete both commitments by Tuesday. We need to agree which work takes priority or provide another resource.”
After the discussion, capture the resulting commitments in the normal place. Update the dependency record so the next person can see the agreement.
The Rock remains with its original owner unless leadership deliberately changes ownership. Other contributors own the actions they have accepted.
Check the result of the handoff
A file arriving on time does not always complete the dependency. The receiving team may need to confirm that it contains the agreed information and is usable for the next step.
Define that acceptance before work begins. For the scheduling example, the output might need confirmed codes, a responsible data owner and one representative test job.
Keep acceptance proportionate to the work. The aim is to avoid discovering a missing detail after the pilot has been scheduled.
If the input falls short, identify the gap promptly and agree on a correction. This keeps progress grounded in evidence.
Start with one priority that keeps stalling
Choose a Rock that has generated repeated follow-ups. List the decisions and contributions it needs over the next two weeks. Confirm those commitments with the people involved.
Then ask whether the current status still reflects the real path to completion.
PSG’s overview of fractional Integrator support for EOS execution explains the broader role. Day-to-day coordination becomes useful when it helps a leadership team resolve the specific dependencies preventing execution.
If quarterly priorities repeatedly stall between departments, talk with Joel Kahn about the operational leadership your team needs between planning sessions.


Comments