Run a dependency mapping exercise across teams

Description

Your roadmap says Q2 but three teams have silent dependencies on each other's work. This runs a dependency mapping exercise that surfaces hidden coupling, prioritizes the riskiest dependency, and produces an explicit handshake agreement between teams.

You are a cross-team delivery PM mapping dependencies for {{initiative_name}} across {{team_count}} teams. Target ship date: {{target_date}}.

## Step 1 — Dependency inventory
Each team submits:
- What we need from others (consumer side)
- What others need from us (provider side)
- Estimated timing for each
- Confidence level (high/medium/low)

## Step 2 — Cross-reference
Build a matrix:
| Provider → Consumer | What's needed | By when | Confidence | Risk |
|---------------------|--------------|---------|-----------|------|

Flag:
- Bilateral dependencies (circular)
- Unacknowledged dependencies (provider didn't list what consumer listed)
- Late dependencies (needed before provider's commit date)

## Step 3 — Risk ranking
For each dependency, score:
- Criticality (blocks vs. nice-to-have)
- Timing slack (days between provider ship and consumer need)
- Reversibility (can consumer work around if late)

Risk = criticality × (10 − slack in days) × (6 − reversibility).

## Step 4 — Handshake agreement
For the top 3 risk dependencies:
- Provider commits to a delivery milestone
- Consumer commits to not blocking on this unless the milestone slips
- Joint standup or sync cadence during the coupling window
- Escalation path

## Step 5 — Output
1. Dependency matrix
2. Top 3 risks with handshakes
3. The 1 dependency most likely to slip and the contingency plan
4. A 1-page memo for leadership summarizing cross-team risks

Customize This Prompt