How to Fix The Technobabble Snafu
Technobabble has become so much a part of our lives that we often don’t see the snafus it can create. It is a language unto itself: It is a technical language that is difficult for ordinary people to understand. Technobabble is well-defined as a type of nonsense that consists of buzzwords, esoteric language, or technical jargon. There is little question that technobabble has its place. But the world is changing and the need to communicate information to diverse audiences requires an approach that the entire audience–not just part of it–can understand. Simplified English
A Technobabble Snafu
“Complex technical instructions can be misunderstood and misunderstandings can lead to accidents. STE makes technical texts easy to understand by all readers”
Some Assembly Required
Some Assembly Required is rarely a reason to buy a product and is often a reason to not buy it. The directions may be unclear and likely written in text so small that you have to find the Internet version just to read it. It would be a pleasant surprise if the manual were written in Simplified Technical English that virtually anyone can understand.
Understandable directions, laid out with graphics that actually relate to the product, help to sell it. The fact that a manual can be understood by a broad audience does not diminish the product: It makes it more accessible and more marketable. In fact, any text written so that it can be understood is more engaging and the content is easily understood.
Avoid Your own Technobabble Snafu!
We can help you communicate in Simplified Technical English or just plain English. Either way, your audience will be engaged in and easily understand your message.
An STE Transformation
Leveraging STE
Case study of a Simplified Technical English (STE) conversion in the Engineering sector. The conversion was intended to remove the archaic wording and make the text easier to translate and understand. The transformation resulted in reduced cost and better translations.
“STE was developed to help the readers of English-language documentation understand what they read, particularly when these readers are non-native English speakers.” – ASD-STE100
English, Simplified, Might Solve Many Technobabble Snafus
Heading 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ut diam consectetur, semper orci quis, euismod elit. Integer tristique, nulla ac mattis pharetra, felis leo sollicitudin nisl, a suscipit elit metus nec justo. Nulla egestas ornare condimentum.
Heading 2
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ut diam consectetur, semper orci quis, euismod elit. Integer tristique, nulla ac mattis pharetra, felis leo sollicitudin nisl, a suscipit elit metus nec justo. Nulla egestas ornare condimentum.
Heading 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ut diam consectetur, semper orci quis, euismod elit. Integer tristique, nulla ac mattis pharetra, felis leo sollicitudin nisl, a suscipit elit metus nec justo. Nulla egestas ornare condimentum.
Heading 2
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ut diam consectetur, semper orci quis, euismod elit. Integer tristique, nulla ac mattis pharetra, felis leo sollicitudin nisl, a suscipit elit metus nec justo. Nulla egestas ornare condimentum.
Avoid Your own Technobabble Snafu!
As Einstein said, “Everything should be made as simple as possible, but not simpler.” We can help you reach a broad audience without burying the content–and context–of your message.
…in Plain Language
Plain English
Writing that is clear and to the point helps improve all communication as it takes less time to read and comprehend. Clear writing tells the reader exactly what the reader needs to know without using unnecessary words or expressions. Communicating clearly is its own reward as it saves time and money. It also improves reader response to messages. Using plain language avoids creating barriers that set us apart from the people with whom we are communicating.
-Office of Personnel Management
Plain Lanuage Rules
- Write for your reader, not yourself. Use pronouns when you can.
- State your major point(s) first before going into details.
- Stick to your topic. Limit each paragraph to one idea and keep it short.
- Write in active voice. Use the passive voice only in rare cases.
- Use short sentences as much as possible.
- Use everyday words. If you must use technical terms, explain them on the first reference.
- Omit unneeded words.
- Keep the subject and verb close together.
- Use headings, lists, and tables to make reading easier.
- Proofread your work, and have a colleague proof it as well.
Heading 3
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ut diam consectetur, semper orci quis, euismod elit. Integer tristique, nulla ac mattis pharetra, felis leo sollicitudin nisl, a suscipit elit metus nec justo. Nulla egestas ornare condimentum.
Heading 4
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras ut diam consectetur, semper orci quis, euismod elit. Integer tristique, nulla ac mattis pharetra, felis leo sollicitudin nisl, a suscipit elit metus nec justo. Nulla egestas ornare condimentum.
What Are Simplified Technical English Rules?
STE has two parts: a set of writing rules (part 1) and a controlled dictionary (part 2). The writing rules cover aspects of grammar and style. The dictionary gives the general words that a writer can use.
Writing Rules
STE addresses difficulties in English comprehension related to complex sentence structures, confusing word forms, and ambiguous vocabulary.
The Writing Rules differentiate between two types of topics: procedure and description. The Writing Rules also specify restrictions on grammar and style usage. For example, they require writers to:
- Restrict the length of noun clusters to no more than three words
- Restrict sentence length to no more than 20 words (procedural sentences) or 25 words (descriptive sentences)
- Restrict paragraphs to no more than six sentences (in descriptive text)
- Avoid slang and jargon while allowing for specific terminology
- Make instructions as specific as possible
- Use articles such as “a/an” and “the” wherever possible
- Use simple verb tenses (past, present, and future)
- Use active voice
- Do not use present participles or gerunds (unless part of a Technical Name)
- Write sequential steps as separate sentences
- Start a safety instruction (a warning or a caution) with a clear and simple command or condition.
Controlled Dictionary
STE has a controlled general dictionary that gives the words that are most frequently used in technical writing.
The Writing Rules differentiate between two types of topics: procedure and description. The Writing Rules also specify restrictions on grammar and style usage.
The approved words were selected because they were simple and easy to recognize. In general, each word has only one meaning and functions as only one part of speech. For example, “to fall” has the approved meaning of “to move down by the force of gravity,” and not “to decrease”.
When there are several words in English for the same thing (synonyms), STE permits one of these synonyms to the exclusion of the others. For example, STE uses “start” instead of “begin”, “commence”, “initiate”, or “originate”. STE approved meanings and spelling are based on American English (Merriam-Webster’s dictionary).
In addition to its general dictionary, STE permits the use of company-specific or project-oriented technical words (referred to in STE as technical names and technical verbs). These words are related to the categories listed in the respective rules.
Basically, writers can use the approved words in the dictionary as a core vocabulary. But they can also use terms that are usual in their companies or industries and applicable to their projects and products.
Why Work With Us?
We are creative, believers in critical thought. Our layouts are sophisticated and appropriate, effective. Our work is informative and engaging. We speak simplified technical English. Let our technical writing services save you time, money, revisions and failed presentations.
Do You Need STE Clarity? Let’s Talk