ProjectManager.co

Most dependency failures aren't caught until the damage is done. This episode breaks down how to manage external dependencies deliberately — with named owners, proactive conversations, and contingency thinking baked in before anything slips.

Show Notes

External dependencies are one of the quietest sources of project failure. A date slips, a handoff never happens, and by the time the RAG status turns red, the schedule is already underwater. This episode of ProjectManager.co tackles a conversation most teams skip entirely during planning — and shows exactly what it takes to manage dependencies that sit outside your direct control.

Here's what the episode covers:

  • Defining the real problem: A dependency isn't just a task on someone else's list — it's any deliverable you cannot accelerate, reassign, or resolve through your own effort, only influence and plan around.
  • Why "we sent an email" isn't a commitment: True dependency accountability requires a named individual on the other side who has acknowledged the date, understands the downstream consequences of missing it, and has protected it in their own plan.
  • The three-question conversation: A short, specific dialogue that turns passive dependencies into active ones — including the often-skipped question about what your earliest warning system looks like if the date is at risk.
  • Critical path prioritization: Using the critical path to categorize dependencies by their true weight — and pre-mapping contingencies for path-critical items before a slip forces your hand.
  • Making dependencies visible in status reporting: Surfacing every open external dependency with a date, a named owner, and a last-confirmed field — because a dependency that was green three weeks ago and hasn't been reviewed since isn't green, it's unknown.
  • The PMO's role across projects: How the PMO framework can map shared dependencies across multiple initiatives and surface conflicts before they cascade — turning organizational coordination into genuine risk reduction.

The episode's practical anchor is treating your dependency log as a living document rather than a static plan entry. Teams that want a ready-made structure for this can start with the RAID log, which captures risks, assumptions, issues, and dependencies in one place. If your project is already showing strain from missed handoffs, the episode How to Recover a Project That Has Already Gone Sideways picks up where this one leaves off.

ProjectManager.co

What is ProjectManager.co?

Project management for people who deliver, not people who certify. Estimation that survives contact with reality, scope and dependency management, status reporting nobody has to decode, and where self-hosted and AI-assisted tooling genuinely helps.

Each episode takes one practice — a re-estimate mid-project, a dependency nobody owns, a status meeting that produces nothing — and works through a better way to handle it. Written for delivery leads and PMs running real projects, with no methodology evangelism. Five or six minutes, one practice at a time.

Topics include estimation that survives reality, dependency and critical path management, scope negotiation, status reporting nobody decodes, resource planning, retrospectives that change something, and self-hosted versus SaaS tooling.

Produced by ProjectManager.co, self-hosted AI project management. Full details, services and further reading at https://projectmanager.co