We got a few good mnemonics so far! Hope to see a few more from different folks.
Ignoring "change management." What a great point. There are these policies/procedures issues that are ignored. Just about every certification exam's objectives list identifies policies/procedures, but do any of us effectively cover their creation and how to write them, let alone how to follow them.
And this is something of a niche, because most of your technical types aren't the best writers, where an organization's writers aren't very capable, technologically. And only larger organizations are going to hire technical writers, choosing to outsource that writing to a scribbler house or some other thing.
I do believe that a good technical writing course taught by someone who actually have to write within the field is a great asset to any post secondary program. One of the worst things that an organization can do ( and I'm sure your JD it's about screaming now), is pulling somebody else's policies off of the Internet, changing the logo and some of the vernacular, and publishing as organizational policy, rather than actually having a proper sitdown with the appropriate management teams to work out what the actual problems are, the things that would need to be managed by policy.
But, we don't live in a perfect world. Most organizations don't have that nifty technical writer, nor access to an external contractor who can do that technical writing. But they do have that organizational requirement usually brought on by insurance, or some other compliance organization, that says they have to have these policies in place and accessible for inspection. So, a network engineer starts the Google process: +"IT Security Policy"
I met with resistance from the English Department because I did not have a master's or doctorate degree that focused on English or Communication.
This is the kind of insane elitism that is prevalent in Academia; something that I personally witnessed so many times, that it has become very cliché. But, that's the college world for you - an awful lot of ivory towers and little fiefdoms that spring up for people to feel self-important, meanwhile there are lots of good people who are capable of the task.
For example, I had to deal with this when I was building a computer technology associate degree program. While it turned out to be far more favorable and amicable in the end, there was a fair bit of surprise that a 20+ IT Technologist (with a Master's, but still), would be able to navigate the choppy waters of accreditation and build a program that would satisfy state requirements as well as requirements from the accreditor. It could have just as easily gone negative, but there was that little wisp of surprise that someone like me would actually know what he's doing in setting up a collegiate program.
/r