Cross-Functional Project Kickoff Pack

The Prompt

You are a program operations lead. Build a kickoff pack that turns a cross-functional project into a concrete operating plan, not just a meeting deck.

PROJECT GOAL:
{{project_goal}}

TEAMS INVOLVED:
{{teams_involved}}

TIMELINE:
{{timeline}}

KNOWN RISKS:
{{known_risks}}

Return exactly:
1) Framing check
   - refined project goal
   - likely scope boundary
   - missing context that could break planning
2) One-page brief
   - goal
   - scope
   - non-goals
   - success metrics
3) Ownership map
   - workstream
   - decision owner
   - execution owner
   - consulted teams
4) Milestone and dependency plan
   - milestone
   - dependency
   - risk if dependency slips
5) Risk and assumption register
   - risk or assumption
   - severity
   - owner
   - mitigation or validation step
6) Communication plan
   - weekly operating cadence
   - decision forum cadence
   - escalation path
7) Kickoff meeting pack
   - agenda
   - pre-read checklist
   - questions that must be resolved in the meeting

Rules:
- Clarify decision ownership explicitly; do not blur approvers and implementers.
- Call out hidden dependencies early instead of assuming they will sort themselves out later.
- Keep wording operational and specific enough that the output could become the first working draft of the project plan.
- If the timeline is unrealistic, say so directly and explain where the compression risk sits.

When to Use

Use this before launching any project where multiple teams share delivery responsibility and unclear ownership usually creates drag. It is especially useful when the kickoff meeting risks becoming a status ritual instead of a decision-making event.

Variables

Variable	Description	Example
project_goal	The outcome the project is meant to deliver	”Launch self-serve onboarding by June”
teams_involved	Functions, owners, or partner teams involved	”Product, engineering, legal, marketing”
timeline	Key dates, deadlines, and fixed constraints	”Kickoff Mar 5, beta Apr 20, launch Jun 1”
known_risks	Early risks, open concerns, or constraints already visible	”Legal review latency, API readiness”

Tips & Variations

• Add budget limits, staffing assumptions, or required approvals if those are real constraints; the quality of the ownership map usually improves immediately.
• Ask for an “executive summary plus working-team appendix” when leaders need a short brief and operators need detail.
• Request phase-gate criteria if the project has governance checkpoints or release readiness reviews.
• If there are already disagreements between teams, ask for a “likely tension map” so the kickoff agenda addresses them directly.

Example Output

Dependency risk: launch depends on security review sign-off by May 12; if it slips, onboarding copy freeze moves with it.

Escalation path: workstream lead -> program lead -> steering committee.