A friend of mine (you know who you are) posted this to his Facebook this morning. Ostensibly, it’s in response to the growing controversy about the New York State governor (I won’t go there; that’s not what this is about, and I still despise politics), but my friend’s post was so compelling that I thought it was worth sharing.
As a professional communicator, I can’t tell you how many times someone either delivered a talk or a document and became frustrated when (s)he didn’t understand why his or her message did not get conveyed. Granted, in some cases, it might be that the sender is not a native speaker of the language and doesn’t know it well enough to convey his or her message. For those people, I’ll cut them some slack.
However, I am continually frustrated by people who insist that (s)he wrote a great document, only to find that what (s)he wrote was so obfuscated by detail, technical jargon, lack of organization, an avalanche of information, poor command of language, lack of understanding about design, or other reasons. This is the kind of thing that keeps me employed as a technical writer.
I’ve written many times before that it’s often the sender’s responsibility to ensure the message is clear. For example, I’ve come across too many instances (and I still continue to) in which a technician, writing a document, keeps insisting on including every little piece of detail in his or her document. And I continue to pound into people’s heads that reading is work!!!
So to my friend who posted this this morning, all I’ll say is, thank you for supporting my passion and my mission. This is exactly what drives me to do SQL Saturday and Data Saturday talks. And I’ll continue doing so until people get the message.