Prodigent

Pre-Release Alignment Checklist

A final pass before ship so GTM, support, and eng share the same story.

Launches fail quietly when teams ship different versions of the same feature — eng ships one behavior, marketing promises another, support hears about it from Twitter.

Pre-release checklist

  • Scope matches what is deployed (feature flags documented)
  • Success metrics and dashboards are live
  • Support macro / help article drafted
  • Known limitations communicated to sales and CS
  • Rollback or kill switch tested
  • Decision log updated for any last-minute trade-offs
  • Stakeholders notified with link to snapshot or release note

T-minus workflow

  1. 1

    T-7 days

    Freeze scope or log explicit exceptions as decisions.

  2. 2

    T-3 days

    Cross-functional read of release note vs. behavior.

  3. 3

    T-1 day

    Support and GTM briefing with FAQ.

  4. 4

    Launch

    Single channel for launch comms; link canonical snapshot.

  5. 5

    T+7 days

    Review metrics against success criteria; log learnings.