Re: Recovering after loss of power - paper bootstrap.
That only works if they get followed.
Early in my career my boss insisted I create, print and laminate procedures for critical systems for the new guy (moved from office temp to IT support thanks to an embellished CV) to follow when I wasn't around.
One day I come back from buying lunch to office panic.
Boss: (dirty look) The main ISP went down 20 mins ago, why isn't there a procedure to switch to the backup?
Me: (calmly points to laminated procedure pinned to the server cabinet in clear line of sight 6 feet away) You mean like that one?
Boss: Oh. Yeah. Didn't see that.
Me: That you asked me to create and print out?
Boss: Yeah, I didn't..
Me: That you had (non-technical new guy) laminate and pin to the server cabinet?
Boss: We didn't think to look there...
Me: So between the 2 of you it didn't occur to look at the wall of procedures 1 of you told me to create and the other physically pinned up there? You've spent 20 mins doing what?
Boss: (to new guy) Let's follow this procedure as far as we can and use this as an opportunity to improve it.
I then calmly sit at my desk to finish lunch while Tweedle Dumb & Tweedle Dumber work through the instructions. They fix the problem quickly then Boss decides to pick it apart with awkward "what if" questions. The answer to each was "It's in the procedure, read all of it"
Luckily years of family tech support taught me to write for non-technical folks. The new guy had a post-it with the AD admin password on his monitor and the manager couldn't see why that was a problem in an office with high staff traffic, so not exactly IT professionals.
My 2nd best day working there, runner up to the day I left :)