We often set valuable quarterly Rocks that end up stalling mid-quarter because we are waiting on external vendors, clients, or partners. How do we keep these externally dependent Rocks on track so we actually finish them by the end of the quarter?

Question

Tyler Smith · Accepted Answer

Relying on external parties is a common excuse for unfinished Rocks, but it is rarely the real root cause of the failure. The breakdown usually happens because the Rock owner treated the external vendor or client like an internal employee who understands the urgency of the ninety-day cycle. They do not.

To keep these Rocks on track, you must build external dependencies directly into your scoping process at the beginning of the quarter. When you write the Rock, you must identify every external deliverable required and set aggressive, early deadlines for them.

Do not wait until week seven to ask a vendor for a crucial piece of software or integration. Your milestones for the Rock should require external inputs to be completed by week four or five. This gives you a buffer to handle delays without blowing past your quarterly deadline.

If an external partner misses a milestone, do not sit on it. Immediately raise it as an issue on your weekly Level 10 Meeting™ agenda. Use the IDS® process to figure out how to apply pressure, find an alternative solution, or pivot your internal efforts. The Rock owner remains fully accountable for the outcome, regardless of vendor delays. If you cannot control the external timeline, you should not have set it as a quarterly Rock in the first place.