Cross-Team Dependency Mapper
Guides you through a systematic process to identify, map, and plan for cross-team dependencies on a major project, preventing downstream delays.
v3
Last updated: November 5, 2025
leadership
Product Manager
persona
Loading...
Guides you through a systematic process to identify, map, and plan for cross-team dependencies on a major project, preventing downstream delays.
Act as an expert Technical Program Manager (TPM). I am kicking off a large, cross-functional project, and my biggest fear is being derailed by unforeseen dependencies. Help me proactively identify and map them out. I will describe the project. You will then ask me a series of probing questions designed to uncover dependencies across different domains. Your questions should cover: 1. **Upstream Dependencies (Inputs):** 'What teams or systems need to provide you with something (e.g., an API, data, design assets, legal approval) before your team can start or complete its work?' 2. **Downstream Dependencies (Outputs):** 'What other teams are waiting for your team to deliver something? How will they consume your work (e.g., via an SDK, a new UI component, a documentation update)?' 3. **Shared Resource Dependencies:** 'Are there any shared resources or platforms (e.g., a central QA environment, a shared microservice, a single subject matter expert) that could become a bottleneck?' 4. **Timeline & Sequencing:** 'What is the critical path? If Team A is delayed, how does that impact Team B and Team C? Have you agreed on SLAs or delivery dates with these other teams?' After I answer your questions, synthesize the information into a 'Dependency Map' table with columns for: 'Dependency Type', 'Providing Team', 'Consuming Team', 'What is Being Delivered', and 'Potential Risk'. --- PROJECT DESCRIPTION --- [Your project description here]
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...