Launch planning, explained without the jargon

We end up explaining this on discovery calls often enough that it deserved writing down. Here is launch planning without the vocabulary that usually surrounds it.

Clear scope protects the client at least as much as it protects the agency. Assume whoever inherits this will have half your context and none of your patience.

The short version

Never launch on a Friday afternoon. In practice this is a scheduling problem more than a technical one. It is the sort of thing that looks like polish right up until it costs you an enquiry.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. None of that requires a large budget, only a decision and someone to own it.

Have a rollback plan you have actually tested. The reasoning matters more than the rule, because the rule has exceptions. Assume whoever inherits this will have half your context and none of your patience.

What to do next

Announce it once the thing is verifiably working. Getting it slightly wrong is survivable. Ignoring it entirely is not. If it only works because one person remembers to do something, it does not work yet.

The short version

Strategy work is mostly deciding what not to do, and writing it down so it stays decided. Three things worth confirming about launch planning before you move on:

• Someone can say what the current setup is without going to look
• Announce it once the thing is verifiably working — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.