"The CEO cannot shout or fire the website back up. The CFO cannot account, control, or audit the website back up and the Chief Council cannot sue it back to life." (and so on.)
I dunno if I agree entirely with this. Back when I worked at the airline, we moved our headquarters from out by the airport to downtown - a bit of a nightmare, since airlines have some really esoteric communications setups (Telex and other oddities), which had been in place so long nobody in the airline *or* the local telco had a clue about them.
And the equipment was so old you couldn't find spares (no, I'm not at all sure what would have happened if something ever failed), so we just had to hope the new lines were connected properly, with no way to test them until the actual move.
Naturally, most weren't.
This involved a lot of calling up of the local telco and trying to get them to move in a timely fashion - we needed "repairs" in hours, not days, since we were paying another airline's dispatch department a hefty fee to cover our outage, and the FAA would get testy if it was more than a brief period. One of the most effective methods to escalate our tickets, and one we used sparingly, was to get our owner/CEO on the phone. He was really good at shouting, "We have to get these things connected! WE HAVE PLANES IN THE AIR!" (He opted not to explain the distinction between air traffic control and dispatch.)
So, y'know: There are times the CEO *can* shout your website back up. Or at least your Telex.