Dependency Map Template for Product Planning

A single-team feature might have zero external dependencies. A cross-org initiative involving 4-6 teams typically has 8-15 explicit dependencies. If you are tracking more than 20, consider whether the initiative should be broken into smaller, more independent workstreams. The [capacity planning template](/templates/capacity-planning-template) can help you scope the work more precisely.

The PM leading the initiative owns the map and is responsible for keeping it current. Individual dependency owners (listed in the register) are responsible for providing status updates. The PM facilitates coordination but does not own every dependency.

A [RACI matrix](/templates/raci-matrix-template) defines roles and decision authority for activities. A dependency map defines what must happen before other things can start. They are complementary. Use RACI for who does what. Use the dependency map for what blocks what.

First, confirm the capacity constraint is real by reviewing it with the other team's PM and engineering lead. If confirmed, you have three options: negotiate priority with their leadership, find a workaround that removes the dependency, or adjust your timeline. Document the decision in the mitigation plan and escalate if needed using the [escalation template](/templates/escalation-template).