{"id":180,"date":"2022-12-28T04:53:49","date_gmt":"2022-12-28T04:53:49","guid":{"rendered":"https:\/\/jsystemsafety.com\/blog\/?p=180"},"modified":"2022-12-28T04:53:49","modified_gmt":"2022-12-28T04:53:49","slug":"foray-into-the-unknown-the-forbidden-science-of-plain-english","status":"publish","type":"post","link":"https:\/\/jsystemsafety.com\/blog\/foray-into-the-unknown-the-forbidden-science-of-plain-english\/","title":{"rendered":"Foray into the Unknown – the Forbidden Science of Plain English"},"content":{"rendered":"\n

by Ann S. Waterman <\/strong> <\/p>\n\n\n\n

<\/div>\n\n\n\n

[Editor\u2019s note: This editorial originally appeared in Vol 33 Issue 4 of Hazard Prevention (now Journal of System Safety) in 4Q 1997. It has been reformatted from the original, but the text is otherwise unchanged. We note that in the 25 years since this article was published, “terminal acronymia” has gone from novel phenomenon to global engineering pandemic!]<\/em><\/p>\n\n\n\n

<\/div>\n\n\n\n

\u201cI don\u2019t know what this means,\u201d he ventured hesitantly after glancing at my note. I smiled. That was precisely my point.<\/p>\n\n\n\n

What I had written, in response to his request for comments on his paper, was a long series of capital letters, broken into random threes and fours, and crammed mercilessly into already overburdened parentheses. Looking again at his own first page, he burst out laughing. Terminal acronymia, to be sure.<\/p>\n\n\n\n

In the first paragraph, not one sentence consisted entirely of English words. Several consisted almost entirely of acronyms, some of which were being used to explain other acronyms. Some were not explained anywhere in sight, an apparent revision having bumped the definitions to subsequent pages. Still others were left entirely to the imagination, an option far more appealing than deciphering the text. I finally decided that DSAG stood for \u201cdesperately seeking a glossary.\u201d \u201cBut everyone in my group understands these,\u201d the gentleman protested, shaking his head. Perhaps, but his group wasn\u2019t the intended audience. Who were the authors writing for? By definition, the goal of publishing is to reach a wide audience. Reaching them, though, is only the beginning.<\/p>\n\n\n

\n
\"\"
A few acronyms used in system safety<\/em><\/figcaption><\/figure>\n<\/div>\n\n\n

Clearly, as technical writing becomes more widely disseminated through journals, conferences and the Internet, vital participants are being increasingly left out of the process: the readers. This is a trend that needs to be reversed before it renders technical writing pointless and therefore obsolete.<\/p>\n\n\n\n

Respected engineering journals such as Hazard Prevention regularly publish articles that were originally written in a language other than English. No one would recommend publishing the original in an English language magazine because the majority of readers wouldn\u2019t understand it; and yet authors continue to publish articles in a language that no one understands. For scientists, the logic must confound.<\/p>\n\n\n\n

Those readers for whom English is a second language are being asked to learn a third one and translate twice. All readers are being asked to memorize definitions, or else to constantly flip back and forth. And what is their reward? The opportunity to try to forget this batch of acronyms and clear their brains for the lot in the next article. Yet authors seem to be oblivious, as they compete to create new and more imaginative acronyms to perpetuate the cycle.<\/p>\n\n\n\n

The most baffling fact of all is that it seems much more excusable to publish in a foreign language than to ask engineers to separate from their acronyms. They have forgotten that other means of expression exist. \u201cBut I don\u2019t want to say System Safety Working Group when I can say SSWG.\u201d Of course you don\u2019t. Say it once, and then \u201cthe group\u201d will work just beautifully. After all, \u201cthe group\u201d has two syllables, while \u201cSSWG\u201d has six. This is economizing?? Now think about other substitutions for most of your acronyms: \u201cthe system\u201d; \u201cthe engineer\u201d; \u201c review team\u201d; \u201cbook\u201d; \u201ctest suite.\u201d And do we really need an acronym to say \u201cstart the engine,\u201d \u201cclose the file\u201d or \u201cnotify the boss\u201d? Words are a scientist\u2019s most powerful tool, since without them the others are meaningless.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/figure>
\n

“Words work. They have amazing clarity, speed and precision – if only people will take a shortcut and use them!”<\/em><\/strong><\/p>\n<\/div><\/div>\n\n\n\n

<\/div>\n\n\n\n

Look at the bright side. With fewer acronyms you won\u2019t have to worry about inadvertently spelling a word (as an embarrassed associate recently did with Numeric Engineering Requisition Directives), conveying the wrong image (as another did with GYN) or staring at a page for twenty minutes trying to figure out how to say it quickly (as a rushed proposal team did with NAWSEAWARENGSTA). Words work. They have amazing clarity, speed and precision – if only people will take a shortcut and use them!<\/p>\n\n\n\n

Hazard Prevention has adopted a policy of ensuring that the articles we publish will be understood by a majority of its readers. In many cases, this means translating acronyms into plain English. We have entered into a brave and wondrous new world. Won\u2019t you join us? Your readers are eagerly waiting.<\/p>\n\n\n\n

\n\n\n\n

About the Author<\/strong><\/p>\n\n\n\n

Ann Waterman is the former Editor-in-Chief and Publisher (1997-2007) of Hazard Prevention, the journal of the System Safety Society. She is a former director of the Society and the 2005 winner of the Society’s International award.<\/p>\n","protected":false},"excerpt":{"rendered":"

by Ann S. Waterman   [Editor\u2019s note: This editorial originally appeared in Vol 33 Issue 4 of Hazard Prevention (now Journal of System Safety) in 4Q 1997. It has been reformatted from the original, but the text is otherwise unchanged. We note that in the 25 years since this article was published, “terminal acronymia” has […]<\/p>\n","protected":false},"author":1,"featured_media":182,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[34,17,15],"class_list":["post-180","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-from-the-archives","tag-clarity","tag-skills","tag-system-safety"],"_links":{"self":[{"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/posts\/180","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/comments?post=180"}],"version-history":[{"count":5,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/posts\/180\/revisions"}],"predecessor-version":[{"id":187,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/posts\/180\/revisions\/187"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/media\/182"}],"wp:attachment":[{"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/media?parent=180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/categories?post=180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jsystemsafety.com\/blog\/wp-json\/wp\/v2\/tags?post=180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}