Write a Cross-team Dependency Map for a Project

When to use this

Use when you need a second opinion on how to write a cross-team dependency map for a project and want the reasoning shown, not just an answer.

Prompt template

Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.

Task: Write a cross-team dependency map for a project.

Context to use:
- Feature or initiative: {{feature_or_initiative}}
- Key stakeholders: {{stakeholders}}
- Constraints or deadline: {{constraints}}

Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklist

Customize

Preview

Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.

Task: Write a cross-team dependency map for a project.

Context to use:
- Feature or initiative: {{feature_or_initiative}} missing
- Key stakeholders: 
- Constraints or deadline: 

Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklist

Usage instructions

Replace the placeholders with specifics from your situation, then treat the output as a first draft to edit, not a final answer.

Example output

A short recommendation, a structured deliverable broken into clear sections, a list of assumptions, and a validation checklist, all specific to the write a cross-team dependency map for a project scenario described above.

Limitations

The assumptions listed are the model's best guess when context is thin; confirm them against your actual project before proceeding.

Rate this prompt