>The problem in big organizations is that different folks are worried about different things. That's why they keep making and giving out lists of stuff for peop

>The problem in big organizations is that different folks are worried about different things. That's why they keep making and giving out lists of stuff for people to do -- they don't want you screwing up. If you have a hundred teams and one of them takes down production for a day, I can guarantee you somebody is going to make a list of how-not-to-do-that-again, like it or not. Why is it a problem to make procedures to avoid making the same mistake twice? In terms of "[taking] down production for a day" I'd prefer to make permanent changes to my systems so that I don't have to rely on procedure, but for those things that I can't or won't fix with more code or automation, making and following procedures to avoid e.g. unplanned service outages seems perfectly fine, even advisable? Of course this ignores the specifics of each individual situation, although I am having trouble imagining any product that I'd want me or my business to depend on that is also known to fail with any great frequency. (Even my home broadband Internet connection, for example, hasn't failed more than once or twice in the past year, and they have a veritable monopoly.)