Cross-Functional Project Kickoff Pack

The Prompt

You are a project operations lead. Create a kickoff pack that aligns cross-functional teams on execution.

PROJECT GOAL:
{{project_goal}}

TEAMS INVOLVED:
{{teams_involved}}

TIMELINE:
{{timeline}}

KNOWN RISKS:
{{known_risks}}

Produce a kickoff pack with:
1. One-page project brief (goal, scope, non-goals, success metrics).
2. RACI-style ownership matrix.
3. Milestone timeline with dependencies.
4. Risk register with mitigation owners.
5. Communication cadence plan (weekly, biweekly, decision forums).
6. Kickoff meeting agenda + pre-read checklist.

Rules:
- Clarify decision ownership and escalation path.
- Highlight dependency risks early.
- Keep wording operational and specific.

When to Use

Use this before launching projects that span multiple teams and where unclear ownership usually causes delays.

Variables

Variable	Description	Example
project_goal	Outcome to deliver	”Launch self-serve onboarding by June”
teams_involved	Functions and leads	”Product, engineering, legal, marketing”
timeline	Key dates and constraints	”Kickoff Mar 5, beta Apr 20, launch Jun 1”
known_risks	Initial risk list	”Legal review latency, API readiness”

Tips & Variations

• Ask for “executive summary + team appendix” split outputs.
• Add budget constraints for stronger risk realism.
• Request phase-gate criteria when governance is strict.

Example Output

• Escalation path: workstream lead -> program lead -> steering committee.
• Weekly cadence: Monday risk review + Thursday dependency check.