Dependency War Room

What participants gain

• Identify critical cross-roadmap dependencies and resource bottlenecks
• Shift perspective from single-project execution to portfolio-level management
• Negotiate sequence adjustments to relieve systemic friction
• Establish cross-functional communication protocols for the execution phase

Materials needed

• The 3 completed 1-Page Roadmaps, pinned to a central board
• Balls of brightly colored yarn or string (Red, Yellow, Blue)
• Push pins
• Dependency Risk Cards
• Master 'Connection Circle' canvas on the floor or large table

How to run Dependency War Room, step by step

1. Pin the 3 completed roadmaps next to each other on a massive central wall.
2. Bring all 24 leaders together in a semi-circle facing the wall.
3. Instruct Team 1 to present their roadmap in exactly 3 minutes, focusing purely on sequence and major milestones.
4. After the presentation, Teams 2 and 3 must identify where Team 1's plan intersects with their own (e.g., 'We both need the Data team in Q2').
5. Use a push pin and red yarn to physically connect the two intersecting milestones across the different roadmaps.
6. Repeat the presentation and string-mapping process for Teams 2 and 3, creating a visual web of dependencies.
7. Identify the 'Knots'—areas on the board where multiple strings converge, indicating a massive systemic bottleneck.
8. Force real-time negotiation to untangle the knots: Which bet takes priority? Which timeline must shift to accommodate the constraint?
9. Document the agreed-upon resolutions on 'Dependency Risk Cards' and adjust the 1-page roadmaps accordingly.

Facilitator tips

• The visual impact of the yarn is crucial; it makes the abstract concept of 'we are too busy' undeniably real.
• Do not let them say 'we will figure it out later'. Force the negotiation of sequence right there in the room.
• Pay special attention to shared services (IT, Legal, HR) which often become the hidden bottlenecks for all bets.
• If a knot cannot be untangled, escalate it immediately as a primary risk for the executive sponsors to manage post-workshop.
• Celebrate the discovery of dependencies; framing them as 'disasters averted' rather than 'problems created'.

Common challenges

• Avoidance - Teams don't want to challenge each other's plans at the end of a long day. Solution: The facilitator must actively probe for intersections if the teams are too quiet.
• False Agreements - Leaders nod along but secretly plan to fight for resources later. Solution: Document the priority calls explicitly on the Risk Cards and have sponsors sign them.
• Complexity Overwhelm - The web of yarn becomes too messy to read. Solution: Only map critical-path dependencies, not minor collaborative touchpoints.
• Defensiveness over timeline shifts - A team refuses to move their milestone. Solution: Remind them of the CEO's mandate; the portfolio's success supersedes individual project speed.

Running it virtually

Place screenshots of the 3 roadmaps on a shared digital canvas. Use the digital pen tool to draw bright, thick lines between dependencies. Use custom tags to mark the 'Knots' and document the resolution directly on the connecting lines.

Expected results

A fully integrated view of the strategic portfolio, with all major dependencies visually mapped, negotiated, and documented, resulting in slight adjustments to the individual roadmaps to ensure systemic viability.

Build a session around Dependency War Room

METODIC drops Dependency War Room into a complete session plan with timing, materials, worksheets, and a facilitator guide — for any workshop, meeting, or team session.

Generate a session with Dependency War Room · Try METODIC free