Earlier quoted context omitted.
A nap being a "necessity" doesn't necessarily mean that taking it at whatever time you want is a necessity. Take the nap before or after the release; or after service is restored. It's not that complicated. FWIW, I don't see why it would have to be either a perk or a necessity, rather than a potential productivity booster that shouldn't be mandatory but can be beneficial to both the employee and the company. I would…
>Take the nap before or after the release; or after service is restored. It's not that complicated. But if it is indeed a potential productivity booster, why would you skip the nap during service interruptions or product releases?
Unless your service interruption is lasting all day (in which case you have bigger problems), it's much better for the company to get the site back up in 10 minutes than to wait 30 minutes for you to finish your nap and then get it back up in 8 minutes. Especially if you're losing $10K in revenue (or more) for every minute of downtime.
Whereas the work you'll be doing once the service is back up can be done more efficiently or creatively or thoughtfully after a nap, but won't suffer from being pushed back half an hour.
Releases, well, that depends on your release process.