There is no maintenance window

I have been asked, more than once, when we can take the system down. The honest answer on a national news platform, a pharmacy chain, or a fashion stack with 1,300 stores is: you cannot. The hour you would pick is the hour someone else is already using.

At Moneycontrol a market-moving story is exactly when you cannot be down. At Wellness Forever a store that cannot bill is not having a migration. At XY Retail a shop floor that waits for headquarters to finish a clever rewrite is the whole problem. I have stopped treating “no maintenance window” as a constraint on the project plan. It is the project.

What that actually means

You do not get a dual-run as a courtesy. You get a dual-run because the old path has to keep taking traffic while the new path proves it can. You do not get a feature flag as a nice-to-have. You get one because the only safe write is a write you can refuse.

The teams that struggle here are not short of engineers. They are short of a sentence that says which path is live, who can switch it, and what you do when the new path is wrong at 11am on a Tuesday.

What I watch for

A cutover deck with a start time and no abort. A migration whose rollback is “restore the backup.” A demo that only works if nobody is using the old thing. If any of those are in the room, you do not have a no-window plan. You have a window you have not admitted to.

I would rather ship a dull, reversible slice than a complete cut that needs the building to hold its breath. Completeness is a slide. Reversal is an operation.