The vendor dependency
A nearly finished interface is blocked by missing external access. · PM Drills · 31 · 30 sec–2 min
The vendor dependency · 30 sec–2 min
Situation
Launch is next week; vendor approval is pending.
The UI works against a mock API. The vendor has not issued production access and has no confirmed approval date.
Think before scrolling
How should the plan and communication change?
What can progress independently, and what remains unproven?
How a strong PM thinks
Expose the dependency and preserve options.
Name the owner, required output, uncertainty, and fallback. Continue useful contract and interface testing, but do not present mock integration as production readiness.
Explore a narrower launch, another approved path, or a date change. Communicate the dependency's effect before external commitments harden. Include time for real integration failures after access arrives.
Takeaway
Readiness depends on the critical path.
A dependency without a confirmed date should remain visible in the delivery confidence, not hidden behind a high completion percentage.