Map dependencies and bottlenecks across my project and teams
Finds hidden and unresolved dependencies between tasks and teams, and the bottlenecks most likely to hold everything up.
The prompt
Map the dependencies in my project and find where the work will get stuck.
Project plan or task list: [PASTE TASKS with owners and dates]
Teams and vendors involved: [LIST, with what each delivers]
Shared resources: [people, environments, equipment, or approvers used by several workstreams]
Known handoffs: [e.g. "data team delivers the feed, then IT builds the report"]
Look for:
- Dependencies that are listed in the plan.
- Missing dependencies: tasks that clearly need an input, approval, environment, data, or decision that no task delivers.
- Dependencies between teams that have no agreed date or owner on both sides.
- Bottlenecks: one person, approver, team, or resource that many tasks rely on at the same time.
- External dependencies (vendors, legal, procurement, other projects) with long or unknown lead times.
Return:
1. Dependency table: From (task or team) | To (task or team) | What is handed over | Needed by | Agreed? (yes / no / unknown) | Risk if late.
2. Missing dependencies you spotted, with the task to add.
3. Bottleneck list: the resource, which tasks compete for it, the peak period, and options (sequence, add capacity, reduce demand).
4. The 5 dependencies to confirm first, with a suggested message to the other team for each.
Don't assume another team has agreed to anything I haven't stated. Mark inferred dependencies [INFERRED].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- PASTE TASKS with owners and dates
- LIST, with what each delivers
- e.g. "data team delivers the feed, then IT builds the report"
- INFERRED
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.
- Plan an event from start to finishTimelines, budgets, logistics, run-of-show, and checklists for work or personal events.
- Turn my project plan into an Excel task tracker with owners and dependenciesBreaks a project or plan into a task tracker with owners, dates, dependencies, and status columns you can paste into Excel.
- Turn my team's updates into a weekly RAG status reportPulls scattered team updates into a weekly status report with honest red-amber-green ratings, risks, and asks.