Cross-Functional Kickoff Brief

Description

Create a project kickoff document that aligns engineering, design, marketing, and business teams on goals, scope, timeline, roles, and communication norms before development begins.

You are a PM leading a cross-functional project kickoff. Create a kickoff document that gets all teams aligned.

## Project Context
- **Project name:** {{project_name}}
- **Sponsor:** {{executive_sponsor}}
- **PM:** {{your_name}}
- **Teams involved:** {{engineering, design, marketing, sales, CS}}
- **Timeline:** {{start_date}} — {{target_launch}}

## Kickoff Document

### 1. Why This, Why Now
[2-3 sentences: the problem, the opportunity, and why it's urgent]

### 2. Success Definition
| Outcome | Metric | Target | Timeframe |
|---------|--------|--------|-----------|
| Primary | | | |
| Secondary | | | |
| Guardrail | | | |

### 3. Scope
**In scope:**
- [Specific deliverable 1]
- [Specific deliverable 2]

**Explicitly out of scope:**
- [What we're NOT doing and why]

### 4. Team & Roles (RACI)
| Area | Responsible | Accountable | Consulted | Informed |
|------|------------|-------------|-----------|----------|
| Product decisions | | | | |
| Engineering | | | | |
| Design | | | | |
| Marketing | | | | |
| QA | | | | |

### 5. Timeline & Milestones
| Milestone | Date | Owner | Dependencies |
|-----------|------|-------|-------------|
| Kickoff | | | |
| Design complete | | | |
| Dev complete | | | |
| QA/Testing | | | |
| Launch | | | |

### 6. Communication Norms
| Channel | Purpose | Frequency |
|---------|---------|-----------|
| Slack #{{channel}} | Day-to-day coordination | Async |
| Weekly sync | Status + blockers | 30 min weekly |
| Stakeholder update | Progress report | Bi-weekly email |

### 7. Risks & Mitigations
| Risk | Owner | Mitigation |
|------|-------|-----------|
| | | |

### 8. Open Questions
| Question | Owner | Due By |
|----------|-------|--------|
| | | |

Customize This Prompt