deliver-launch-checklist

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Launch Checklist
3 
4A launch checklist is a comprehensive verification document that ensures all functions are ready before releasing a feature or product. It coordinates across engineering, QA, design, marketing, support, legal, and operations to prevent launch-day surprises. Good launch checklists surface blockers early and create shared accountability for launch readiness.
5 
6## When to Use
7 
8- 1-2 weeks before any significant launch
9- During launch planning kickoff meetings
10- When coordinating cross-functional releases
11- Before major version releases or feature rollouts
12- After incidents to improve launch processes
13 
14## When NOT to Use
15 
16- You are validating whether to ship at all via an experiment -> use `measure-experiment-design`
17- You need the customer-facing announcement of what shipped -> use `deliver-release-notes`
18- The launch already happened and you want results or reflection -> use `measure-experiment-results` or `iterate-retrospective`
19- The change is small and single-team with no cross-functional surface: a launch checklist adds ceremony without value; track it in the sprint instead
20 
21## Instructions
22 
23When asked to create a launch checklist, follow these steps:
24 
251. **Define Launch Context**
26   Document what is launching, when, and who the key stakeholders are. Establish the launch tier (major release, minor feature, experiment) as this affects checklist scope.
27…