The go/no-go call: 12 questions before you flip the switch

The riskiest moment in any project isn’t the build — it’s the night you cut over. And the most dangerous go/no-go meetings are the confident ones, where everyone nods, nobody has the exit criteria in front of them, and “we’ve come too far to stop now” quietly becomes the decision-making framework.

A go/no-go call should be boring. Boring means you decided the criteria in advance and you’re simply checking them. Here are the twelve questions that get you there.

Readiness

1. Are the exit criteria written down, and are they actually met — zero critical/high bugs, UAT signed off, performance within SLA?
2. Has the full cutover run-sheet been rehearsed end to end, not just discussed?
3. Is the data migration validated against production-scale volumes, with a trial run behind you?
4. Are smoke tests defined for the moment after cutover, before you open the doors?

People

5. Have end users, admins and support been trained, with quick-reference guides in hand?
6. Are accounts and permissions provisioned and tested — not something you’ll “sort out live”?
7. Has the comms plan gone out, so nobody’s surprised the system changed under them?
8. Is the war room staffed — cross-functional leads in one channel, ready to triage?

Safety

9. What are the exact rollback triggers? “We’ll know it when we see it” is not a trigger.
10. Has the rollback procedure itself been tested — can you actually get back to the last known good state?
11. Who holds decision authority — by name — to call go, no-go, or abort mid-cutover?
12. What’s the hypercare plan — who’s on high alert, for how long, after you’re live?

The thing every rollback plan forgets

Teams lovingly document how to roll back — and forget to decide who can pull the trigger and when. At 2 a.m., with a half-migrated database and a VP asking for “five more minutes,” you do not want to be debating authority. Assign it in daylight: one accountable person, clear triggers, no ambiguity. A rollback you’re too hesitant to call isn’t a safety net — it’s decoration.

Flip the switch when the criteria say so — not when the room runs out of patience.