launch-planning
Launch Planning
Plan launches that drive adoption, not just press releases.
How to use
/launch-planningApply launch planning constraints to this conversation./launch-planning <feature>Build a launch plan for the described feature or product.
Constraints
Launch Tiers
Not every launch deserves the same effort. Tier them:
- Tier 1 (big deal): new product, major feature, pricing change. Full cross-functional coordination.
- Tier 2 (notable): significant improvement, new integration. Blog post, email, in-app announcement.
- Tier 3 (incremental): bug fixes, small improvements. Changelog entry, maybe a tooltip.
- MUST assign a tier before planning. Over-launching small things causes announcement fatigue.
Pre-Launch
- MUST define success metrics before launch, not after
- MUST have a rollout plan: internal dogfood → beta → phased → GA
- SHOULD run through the launch checklist with every function: engineering, design, marketing, sales, support
- MUST ensure support and sales know about the launch before customers do
- NEVER launch without documentation and support readiness
Launch Day
- MUST have a single owner for launch coordination
- SHOULD have a war room or dedicated channel for real-time issue tracking
- MUST monitor key metrics in real time during rollout
- MUST have a rollback plan if something goes wrong
- NEVER launch on a Friday unless you want to work the weekend
Post-Launch
- MUST review metrics against success criteria within 1-2 weeks
- SHOULD gather early user feedback actively, not passively
- MUST run a retrospective: what went well, what didn't, what to change next time
- SHOULD have a fast-follow plan for known gaps and quick improvements
- NEVER move on immediately without measuring whether the launch actually worked
Anti-Patterns
- The Silent Ship: launching without telling anyone and wondering why adoption is low
- Launch and Forget: big announcement, zero follow-through or measurement
- The Big Bang: months of secret building followed by a massive reveal. Ship incrementally instead.
- Support Surprise: customers asking about a feature support hasn't heard of
- The Premature Launch: announcing before the product is actually ready to handle real usage
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1