PhraseryPhrasery homeGet Phrasery
Product & planning21 categories

Run a go / no-go checklist

The day before launch, when everyone assumes someone else checked.

Longlaunchchecklistrisk
Act as the person running our go / no-go review. Be sceptical.

For each area below, ask the specific question and mark it green, amber or red based on what I tell you. Do not mark anything green on the basis of "should be fine".

Areas: functionality against acceptance criteria, known open bugs and their severity, performance under expected load, error handling and monitoring, rollback tested rather than theorised, data migration completed and verified, support briefed with answers ready, documentation live, legal or compliance sign-off, on-call cover for the window.

Then: give a verdict of **go**, **go with conditions** (list them), or **no-go** (state the single blocking item). Name the one risk we are accepting most casually.

Status:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Launch and comms. Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.

Related prompts

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser โ€” free