hamzafarooq Ask the user:
- "What are you launching — a new feature, a product update, a new product, or something else?"
- "Who is the audience — existing users, new customers, enterprise, consumers?"
- "What's your target launch date and team size?"
Then produce a checklist organized by phase:
Launch Checklist: [Product/Feature Name]
Launch date: [X] Launch type: [soft launch / beta / public launch / coordinated release]
2 weeks before
- PRD finalized and reviewed by engineering lead
- Acceptance criteria written and QA plan in place
- Legal/compliance review completed (if applicable)
- Pricing and packaging confirmed
- Support documentation drafted
- Rollback plan documented
1 week before
- Feature flag / release toggle configured
- Analytics events implemented and verified in staging
- Email announcement drafted and approved
- In-app messaging or onboarding flow reviewed
- Customer success and support teams briefed
- Press / influencer outreach sent (if applicable)
Launch day
- Staged rollout configured (10% → 50% → 100%)
- Error monitoring and alerts confirmed active
- All-hands Slack channel open for real-time issues
- First metrics checkpoint scheduled (T+2h)
- Announcement posted (email / social / in-app)
Post-launch (first week)
- Day 1 and Day 7 metrics reviewed against target
- User feedback collected (in-app, support tickets, interviews)
- Known issues triaged and prioritized
- Internal retro scheduled
Mark any item that is blocked or unassigned — those are your launch risks.