Re: Communication "Preferences"
In the product documentation, you need to document the options so that there's enough information that you can make that shorter page. True, that documentation and the checklist you're making are probably not written by the same person, but it is still important to have them both. I can't count the number of configuration pages where there is an option that I can configure but I have no clue what it does because it just has "TRS, default setting 0", and doesn't expand TRS or explain what it does. The more professional the equipment, the more likely there's a manual which explains it somewhere, but there is a lot out there without such a thing.
If I'm supposed to be a human computer, simply setting anything the way that my knowledgeable colleague said, this is not a problem. In that situation, there is no need to train any other engineers either, since we just need to have existing engineers write up some one-page processes and hand them to people who need to have no skills or interest in gaining them. There are quite a few people I know who don't know or want to know about computers but can be trusted to complete a completely rigid set of instructions about where to click and which box to put which value in. That is not what network engineering requires. The reason we need people with knowledge is that these things are complicated, and having the skills doesn't help unless they have enough information about what the systems do that they can figure out when the defaults or the things written on the previous configuration need to be changed, how to test that their changes worked, how to test that their changes didn't break something else, how to reverse them if they did fail, and how to diagnose a new problem that they haven't seen before. At most only one of them, number 2 on that list, can be in the one-page checklist, and in most of the ones I've seen, that one isn't on it either.