launch-plan

name	launch-plan
description	Coordinate a launch across product readiness, messaging, channels, support, documentation, analytics, timing, owners, and contingency plans.

Launch Plan

Use for public launches, major feature releases, campaigns, or coordinated announcements.

Procedure

1. Define the launch objective, audience, date constraints, and exact product state being launched.
2. Establish readiness dependencies across product, engineering, QA/security, documentation, support, marketing, analytics, and operations.
3. Build a timeline backward from immutable dependencies while preserving buffers for validation.
4. Assign owners for every launch-critical artifact and decision.
5. Define message, channels, assets, enablement, monitoring, and post-launch response.
6. Identify failure scenarios and contingency actions, including delay criteria.
7. Run a final readiness review based on evidence, not optimism.

Quality gate

A launch plan is complete when product readiness and audience-facing execution are synchronized and every critical dependency has an owner.