Or you could just do your fucking job and create a real disaster recovery plan.
This is not like, super trivial. People needed to figure out power, hardware, networking, vpn, etc.. etc.. etc.. and staffing. A lot of that had absolutely nothing to do with IT, but some of it did.
These are the kind of things that fall between the gaps in smaller companies and there's no expert to build this disaster recovery plan because there is no risk or compliance department.
It falls into the lap of whomever is dealing with the audits or whoever has a reputation for getting things done and unblocking people.
What I won't do is "Tom Sawyer it" to an AI. That's the sort of thing that kids do. I'm assuming the OP is an adult.
If you think there is always someone willing _and_ available to work on any given problem then... well I don't even know. Maybe I've only worked at smaller companies but that's never been my experience.
I manage (as well as code) but one thing I think more people need to understand: This is a _job_ and at the end of the day I really don't care if X task is something you don't want to do. I will do my best to match people with tasks, even adjusting timeline out further to accommodate people's tastes but there are somethings that just have to get done and the bad attitudes I've seen or had directed at me when this happens is a bit shocking. If you want to only work on things you want to work then work for yourself or find a company more aligned to your preferences (good luck finding one that only does what you want).
I understand why people in and out of the industry see developers as childish (I was/am part of the problem, no doubt).
> Why waste this guy's time.
I feel like I need a megaphone: Employees don't get to decide what is or isn't a "waste of time". Or rather, they can voice their dissent but once a decision is made you are _literally_ being paid to do what you are asked. If you don't like that then look for another job. I'm not trying to be a jerk or pretend job-switching is easy, but I've dealt with high-paying developers who whine (yes, whine) when you ask them to _do their job_ and it's infuriating. Before I started managing people I would regularly go to the mat over decisions but once I had said my piece and a decision was made I'd go along with it, I'd done my job (voice concern) and past that it's out of my hand and not my responsibility if it doesn't pan out. Every combination of being right/wrong about the final outcome and being the right/wrong side of the decision has happened to me, you do the best with the info you have and you deal with the fallout.