Cutover nights: what belongs on the wall

Slide decks disappear when the lights stay on past midnight. Before a production wave, we ask clients to put a short set of artefacts on the wall—or on a shared screen that everyone can see without hunting folders.

What stays visible

• Wave objective in one sentence — which services move, and which explicitly do not.
• Entry criteria — green checks that must be true before the first change.
• Rollback triggers — the conditions that stop forward progress without debate.
• Named owners — who speaks for application, database, DNS, and communications.
• External contacts — cloud support case number, ISP, and building access if you are in a cage.

What does not belong on the wall

Long architecture histories, vendor marketing, and unresolved opinion threads. Those belong in the decision log for later, not in the moment when a DNS TTL is already draining.

A Thailand-specific note

If your ops lead and your developers sit in different cities, agree the Thai and English labels for the same steps in advance. We have watched delays come from polite confusion over which “final” checklist was current.

When we provide Cloud Migration Advisory, the wall pack is part of the rehearsal output—not an afterthought the night before.