Map cross-team dependencies before kickoff starts

Surface hidden handoffs, technical blockers, and team commitments before launch work begins. Use this during project planning to avoid timeline surprises.

You getDependency Matrix, critical Path Blockers and alignment Questions

Prompt

Prompt
Act as a technical project director reviewing cross-functional initiatives.

Analyze the project notes pasted below to extract all cross-team handoffs, shared systems, and interdependencies.
- Flag unconfirmed assumptions where one team assumes another has bandwidth or existing API endpoints.
- Identify critical path items that will block downstream deliverables if delayed.
- Highlight missing owners or undefined acceptance criteria.

Output format:
- Dependency Matrix: A Markdown table with columns (Dependency, Owning Team, Consuming Team, Required Date, Risk Level)
- Critical Path Blockers: Bullet points detailing the three highest-risk handoffs
- Alignment Questions: 4 specific questions to ask partner leads during the kickoff meeting

Project notes are below:

Example output

Example for: kickoff notes for a customer billing portal redesign involving product, payments backend, and data analytics

Dependency Matrix
DependencyOwning TeamConsuming TeamRequired DateRisk Level
Subscription Webhook V2Payments CoreFrontend WebOct 12High
Customer Churn Data PipelineData AnalyticsMarketing OpsOct 19Medium
Stripe Tax Calculation SyncInfrastructurePayments CoreOct 05High
Help Center SSO AuthenticationIdentity/SecFrontend WebOct 26Low
Critical Path Blockers
  • Subscription Webhook V2: Frontend engineers cannot build the billing history UI without the updated schema. If Payments Core misses the Oct 12 cutoff, frontend development stalls completely.
  • Stripe Tax Calculation Sync: Infrastructure has not confirmed migration scripts. A failure here blocks test transactions in staging.
  • Data Pipeline Schema Approval: Marketing Ops needs fields that Data Analytics has marked as tentative, risking rework on reporting dashboards.
Alignment Questions
  1. Payments Core: Has the V2 webhook schema been finalized and published in the staging environment for frontend mockups?
  2. Infrastructure: Who is the designated point of contact for the Stripe Tax script migration during the week of Oct 05?
  3. Data Analytics: Will the churn event payload include tenant-level metadata, or must frontend pass that separately?
  4. All Leads: What is our fallback plan if Payments Core requires an extra sprint to validate subscription edge cases?
Written by AI from this prompt. Your results will vary.

Paste your project scope, draft PRD, or kickoff notes at the bottom of the prompt in Claude, Gemini, or ChatGPT. If dates are uncertain, ask the model: "Which of these dependencies has the highest likelihood of delaying our end date by two weeks?"

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.

Leadership & Management

Create a post-crunch team recovery sprint plan

Design a two-week reset sprint to help teams recuperate after an intense deadline push. Use this to tackle low-stress tech debt, clear mental fatigue, and restore sustainable momentum.