Project Brief

One-page project brief: problem, scope, owners, success metrics, key risks.

# Project Brief â [Project name] **Owner:** [Name] **Sponsor:** [Name] **Stakeholders:** [Names] **Target ship date:** [Date] **Status:** [Proposed | In progress | Shipped | Cancelled] ## Problem One paragraph describing the problem in user / customer / business terms. Avoid solution language. If you can't write the problem without naming a tool, you don't yet understand the problem. ## Why now What is the forcing function? Why is this more valuable to do this quarter than the next-best alternative project? Be concrete â "competitive pressure" is a category, not a reason. ## Goals - Primary goal: one measurable outcome - Secondary goals: 1-3 measurable outcomes - Explicit non-goals: things we are NOT solving in this project ## Approach 2-3 paragraphs outlining how we'll get from here to there. Architecture, sequence, team composition. Not a full design doc â link to that. ## Success metrics How will we know it worked? Each metric should have: - Definition (calc, time window, segment) - Baseline (current value) - Target (what success looks like) - Measurement source (where the number comes from) ## Risks The 3-5 things that could prevent this from working. For each, the leading indicator that will tell us early if the risk is realising. ## Resources - Engineers: [N people] - Designers: [N people] - Other: [PM, data, ops, etc.] - Budget: [if applicable] - Dependencies on other teams: [list] ## Timeline - Week 1: [milestone] - Week 2-3: [milestone] - Week 4: [milestone] - Ship target: [date] ## Approval - [ ] Sponsor sign-off - [ ] Engineering lead sign-off - [ ] Design lead sign-off - [ ] Finance sign-off (if budget > $X)

Price: Free
State: approved