Run a cross-department mid-project alignment check

Spot conflicting department goals, misaligned timelines, and unowned dependencies before project drift derails delivery.

You getAlignment Summary, priority Mismatches and critical Dependencies

Prompt

Prompt
Act as an experienced cross-functional project director. Analyze the project update notes provided to identify misalignment between teams.

- Extract conflicting goals, unspoken assumptions, or mismatched timelines across departments.
- Flag dependencies that lack an explicit single owner or agreed delivery date.
- Separate actual blockers from minor administrative friction.
- Recommend direct, collaborative actions to resolve each identified friction point.

Output format:
1. Alignment Summary (3 sentences on overall cross-department health)
2. Priority Mismatches (bullet list: Department vs Department, the conflict, potential impact)
3. Critical Dependencies (table with columns: Dependency, Owner, Dependent Team, Risk Level)
4. Recommended Realignment Actions (numbered list with specific discussion points for the next sync)

My project notes and updates are below:

Example output

Example for: cross-department rollout notes between Engineering, Marketing, and Support

  1. Alignment Summary
    The rollout is mechanically on schedule for core features, but go-to-market and customer support readiness are lagging significantly. Engineering is treating the deployment date as the finish line, while Marketing and Support expect two weeks of feature freeze beforehand to prepare collateral and training. Without immediate agreement on readiness criteria, customer-facing teams will launch unprepared.
  2. Priority Mismatches
  • Engineering vs Marketing: Engineering plans to merge the authentication redesign on the launch date. Marketing requires finalized screenshots five days before launch for press material, risking outdated external assets.
  • Support vs Product: Product prioritized a minor analytics dashboard over critical admin billing controls, leaving Support without tools to resolve anticipated customer account billing questions.
  1. Critical Dependencies
DependencyOwnerDependent TeamRisk Level
API documentation sign-offBackend Team LeadTechnical SupportHigh
In-app banner copy approvalMarketing LeadFrontend TeamMedium
Self-serve refund toolingPayments PMCustomer OperationsHigh
  1. Recommended Realignment Actions
  2. Establish a joint feature-freeze date of October 12th to allow Marketing and Support ten business days with stable interfaces.
  3. Reassign the Payments PM to deliver an emergency read-only admin refund tool before working on secondary analytics.
  4. Run a mandatory 30-minute handoff review between Backend and Support Leads on October 14th.
Written by AI from this prompt. Your results will vary.

Paste your project sync notes or Slack updates at the end of the prompt in Claude, ChatGPT, or Gemini. As a follow-up, ask the model to draft an agenda for a 30-minute realignment meeting with the conflicting department heads.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management