← Docs
Recipe

Recipe: Cross-team launch coordinator

Ship features that span engineering, marketing, and support without dropping a single handoff.

Ingredients

  • One shared launch doc (Notion or Google Docs)
  • Slack channel #launch-YYYY-MM-DD
  • Linear board with swimlanes per team
  • Feature flag in Meridian
  • 30-minute daily sync for the final week

Steps

  1. T-14 days: Lock scope. Every team lead signs off on the launch doc.
  2. T-10 days: QA freeze. Only launch-blocker fixes land.
  3. T-7 days: Marketing assets finalized. Support scripts written.
  4. T-3 days: Dry run in staging. Flip the feature flag for internal users.
  5. T-0: Gradual rollout. 10% → 50% → 100% with monitoring.
  6. T+1 day: Retrospective. What broke? What held?

Anti-patterns

  • Silent launches — marketing finds out on Twitter
  • No rollback plan — feature flag is your safety net
  • Single-person bottleneck — bus factor of one

Need a template? Grab the launch checklist and adapt it for your team size.