Plan · first 30 days
Make “ready” checkable.
Not a new process — a gate on the one that already ships every Thursday.
Week 1 · Truth
- Flip the Mobile App article title; add Consumer AI help articles or an availability statement
- Publish a Plus end-of-support page with date, path and FAQ
- Resolve Scan to Redeem: shipped, slipped, or dated
Weeks 2–3 · The gate
- Launch board columns: release note, monthly update, help center, status, product page, availability/migration — each with an owner
- GA can't be set while a required column is red
- Headline check in the release-note template (dictionary + title format)
Week 4 · Signal
- Day-30 re-run on every launch: catches stale “Coming soon” and missing docs
- Support-ticket volume per launch next to adoption, defined before GA
- Monthly launch-readiness report: cleared first time, which surface lagged, which owner
What I'd want to know
Which surface Dutchie treats as the source of truth today — LaunchNotes, the monthly update or the help center — because the gate should hang off that one. Who owns the help-center flip from “Coming soon” to live. And how Product, Enablement and Support currently sign off, so the gate records their sign-off instead of adding a new one.