donotdeploy.si

do not deploy.

There are many good reasons to reject a deployment plan.

A rejected plan is not a rejected change. It is a change that is not ready yet.

Why a plan gets a no

It’s Friday
Or the afternoon before a holiday, or a gap in on-call coverage. The change may be sound. The people who would fix it may not be there.
Untested rollback
A hope to “just roll it back” is not a plan until someone has practiced it, or can show that it will work for this change.
No owner on call
If this breaks at two in the morning, a named person should already know they are the one who will be asked.
No window, no word
A change without a declared window, and without telling the people who will feel it, is a surprise. Surprises do not belong in production.
Bundled changes
If two things go out together and something breaks, you will not know which one to undo.
No canary
A full cutover is a bet that the first users will all be fine. Start with a few.
Not like production
An environment that is not like production is a hope, not a test.
Irreversible migration
If the data can only move forward, the plan has to be right the first time — or it needs a tested way back.
No success signal
If you cannot watch the change, and you have not said what “good” looks like, you will find out from the users.
Another moving part
A vendor cutover or a new dependency beside your own change is two new things at once. That is a riddle, not a rollout.
Unknown blast radius
If the people shipping it cannot say what else it might touch, it is not ready.
“Just a config change”
Configuration is still a change. It reaches production the same way everything else does, and it can undo a system just as thoroughly.
A freeze is in effect
The freeze exists because someone already paid for a week like this one. Honor it, or obtain a real exception — not a quiet one.
Secrets, mixed in
Credential and access changes are their own kind of risk. They should not ride along with a feature.

What a yes looks like

A plan worth approving has these, written down, and believed by the people who will live with the result.

Please don’t be cross with the person who sent you here. They are trying to help the plan, not to embarrass it.

Even very large systems have had to learn this in public. The lesson is always the same.