alexe-ev Plan Product Launch
Purpose
Help teams structure a comprehensive launch plan that coordinates readiness, channels, stakeholders, and success criteria.
Skill type
Conceptual skill
Use this skill when
- A product or feature is approaching launch and needs a coordinated plan
- A launch is happening without clear readiness criteria or coordination
- A team needs to align on what "ready to launch" means
- Post-launch monitoring and rollback criteria need to be defined
Do not use this skill when
- The product isn't close to launch yet (use product-planning skills first)
- The goal is positioning and messaging definition (use develop-positioning-messaging)
Required inputs
- Product or feature being launched
- Target launch timeline
- Target audience
Optional inputs
- Readiness criteria list
- Stakeholder list
- Channel options
- Success metrics
Upstream context
Works best when:
- Feature is built and in testing
- Positioning and messaging are defined
- Success metrics are defined
If upstream context is missing
Produce a launch readiness assessment framework and flag what is still needed.
Downstream handoff
Output can feed:
- enable-sales-cs (sales and CS enablement for the launch)
- analyze-experiment-results (if launch includes an A/B test or phased rollout)
Instructions
- Define launch readiness criteria across: product, quality, support, marketing, sales, legal/compliance.
- Identify the launch audience: internal, beta, soft launch, full launch.
- Define channels and messaging for each audience.
- Build a pre-launch, launch day, and post-launch checklist.
- Define success metrics and when to measure them.
- Define rollback criteria and process.
- Map stakeholders and communication plan.
Output
Provide:
- Launch readiness criteria by area
- Launch audience and rollout strategy
- Channel plan and messaging brief
- Pre-launch / launch day / post-launch checklist
- Success metrics and measurement plan
- Rollback criteria and process
- Stakeholder communication plan
Risks / caveats
- A launch without rollback criteria is a gamble
- Support and sales must be enabled before launch, not after
- Define "done" clearly — "feature is live" is not the same as "launch is successful"