Back to prompts
ProductivityChatGPTClaudeGemini

Project Brief Template

Create a comprehensive project brief that aligns all stakeholders on scope, goals, timeline, and success criteria.

Prompt Template

You are a senior project manager. Create a comprehensive project brief for:

**Project name:** [name]
**Project type:** [product launch / feature build / marketing campaign / process redesign / event / migration]
**Sponsor/Owner:** [who is accountable]
**Team:** [roles involved]
**Timeline:** [start date — end date]
**Budget:** [if applicable]
**Context:** [why are we doing this now? what triggered it?]

Generate a project brief with these sections:

1. **Executive Summary** (3-4 sentences) — what, why, when, expected impact
2. **Problem Statement** — what problem does this project solve? Include data if available.
3. **Goals & Success Metrics**
   - 3-5 measurable goals (SMART format)
   - How each will be measured
   - Target numbers and deadlines
4. **Scope**
   - In scope (specific deliverables)
   - Out of scope (explicitly stated)
   - Assumptions
5. **Approach** — high-level strategy and phases
6. **Timeline** — milestones with dates
7. **Team & Responsibilities** — RACI matrix
8. **Dependencies** — what this project needs from others
9. **Risks** — top 5 risks with likelihood, impact, and mitigation
10. **Budget** — breakdown if applicable
11. **Communication Plan** — how updates will be shared, how often, to whom
12. **Sign-off** — who needs to approve this brief before work begins

Example Output

# Project Brief: Mobile App v2.0 Launch

Executive Summary

Redesign and relaunch the mobile app (iOS + Android) to address the 32% drop-off in onboarding and support the new API-first architecture. Target: 40% improvement in Day-7 retention. Timeline: 12 weeks. Budget: $180K.

Problem Statement

Our mobile app hasn't been updated in 14 months. User reviews average 3.2 stars (down from 4.4). Support tickets from mobile users are 3x desktop. The current app doesn't support key features launched in Q3-Q4 (collaboration, real-time sync).

Goals & Success Metrics

| Goal | Metric | Target | Deadline |

|------|--------|--------|----------|

| Improve onboarding completion | % completing setup flow | 68% → 85% | Week 12 |

| Increase retention | Day-7 retention rate | 23% → 40% | Week 16 (4 wks post-launch) |

| Reduce support load | Mobile support tickets/week | 340 → 150 | Week 14 |

Risks

| Risk | Likelihood | Impact | Mitigation |

|------|-----------|--------|------------|

| iOS App Store review delays | Medium | High | Submit 2 weeks early, maintain relationship with Apple rep |

| API migration not complete in time | High | Critical | Decouple app launch from full API migration, build adapters |

Tips for Best Results

  • 💡The 'Out of Scope' section prevents 90% of scope creep — be explicit about what you're NOT doing
  • 💡Write success metrics that are measurable on day one — 'improve user satisfaction' is not measurable without a baseline
  • 💡Share the brief early and get pushback before work starts, not after
  • 💡The RACI matrix seems bureaucratic but saves weeks of confusion on larger projects