How To Create User-Friendly Documentations With Simplified Technical English

How To Create User-Friendly Documentations With Simplified Technical English [Featured]

The English language is one of the most widely used languages in technical writing. But the English language is complex - rich in idioms, verbal phrases, figure of speeches, synonyms, ambiguous words and terms that may confuse secondary speakers and even native speakers. This is one of the key reasons why some users don’t read help manuals.
While documenting, almost every technical writer contends with the daunting task of communicating complex technical terms in very simple and easy-to-understand words, sentences, and instructions. In most cases, the technical writer’s effort is measured by user feedback.
So to make technical documentations such as user manuals, help files, safety guides etc. easier to understand and user-friendly, the Aerospace and Defence Industries Association of Europe (ASD) developed Simplified Technical English (STE), otherwise known as the ASD-STE100 or the Thumbs-up technique.

STE is primarily important for writing clear and unambiguous content especially for user instructions such as maintenance manuals, user guides, safety guides, and other help documentations. You can learn how to write a great help manual by using the Simplified Technical English approach.

How To Use Simplified Technical English (STE)

The Thumbs-up technique involves three key steps for using Simplified Technical English. These steps are:

  1. Figure out the relevant information and delete the irrelevant ones.
  2. Check the approved meaning of words on the online STE Dictionary
  3. Change your sentences using simple and easy-to-understand languages, according to the suggestions of the STE dictionary.

1. Figure out the relevant information and delete the irrelevant ones

Many instructional content like warnings and task descriptions often contain irrelevant information about how users can complete a task.

For instance: How to install software version 2.11 quickly within few minutes without wasting time.
Can be modified to: How to install software version 2.11 quickly.
Removing other part of the sentence “quickly within few minutes without wasting time” will not alter the instruction in any way.

The first step of the Thumbs-up Technique is about deleting all irrelevant information and leaving only the relevant ones. One easy way to identify irrelevant information is by asking yourself this simple but logical question: “Does the user really need this information or word to complete this task?” If removing any word or phrase will not alter how the task is performed or completed, then you don’t need such word or phrase.

2. Check the approved meaning of words on the online STE Dictionary

The online STE Dictionary contains approved meaning of words that makes technical documentations easier for users to understand. While documenting, chances are you’ll use words you aren’t so sure if users will understand the intended meaning.

You can use the online STE Dictionary as a verification guide to make sure you documentations are user-friendly. The use of approved and unapproved words is summarized in the following four writing rules:

  1. Only use those forms of verbs and adjectives shown in the STE-Dictionary.
  2. Keep the approved meaning of a word in the STE-Dictionary. Do not use the word with any word or meaning.
  3. Choose only words from the words in the dictionary.
  4. Use approved words only as part of the given speech.

While writing your documentation, consider using a HAT such as HelpNDoc which includes multiple dictionaries to make sure the content is as perfect as possible.

3. Change your sentences using simple and easy-to-understand languages, according to the suggestions of the STE dictionary

This step refers to practically applying the first step of Simplified Technical English. First, you’ll have to determine the relevant information in your documentation and keep them. Delete every irrelevant information. There are two things you can do to convert sentences in your documentations into STE.

First, look up your sentences under the “Approved Example” in the STE Dictionary. There are 66 Writing Rules, while you may not know all of them, you can copy and paste common similar sentences from this column or emulate their structure to create your own sentences.

Second, present the core information, convey it in simple, easy-to-understand language. But documenting in a controlled language requires a functional approach. Practically, there are specific rules for text functions like instructions, results, or warning messages. Here are 2 key examples of functional, controlled-language rules:

Example 1:
Text function: Instruction
Pattern: Verb (infinitive) + article + object + punctuation mark
Example text: Click the button.

Example 2:
Text function: Result
Pattern: Article + object + verb (present tense) + punctuation mark.
Example text: The Expense Report window appears.

The two examples present the core content of the information, expressing it in very simple easy-to-understand language. Keep this in mind when modifying your sentences to adhere to STE.

Enjoy documenting!

See also...

7 Key Reasons Why You Need A Responsive HTML Website [Featured]
7 Key Reasons Why You Need A Responsive HTML Website

Would you love your website to look great with a stunning and richer user experience across all devices, platforms, and screen sizes? It’s easy to conclude that you need such a website because of …

Read More →
How To Create An Appealing Online Documentation [Featured]
How To Create An Appealing Online Documentation

It is easy to assume that content is the only element users care about whenever they use a documentation. But such an assumption is absolutely far from reality. Design is one of the most crucial …

Read More →
Online User Guide Writing Tips [Featured]
Online User Guide Writing Tips

Online user guides and manuals are absolutely convenient for users because they can be accessed easily and almost anywhere. As such, online user guides and manuals must be written appropriately to …

Read More →
6 Technical Writing Principles To Make Your Documentations More User-Friendly [Featured]
6 Technical Writing Principles To Make Your Documentations More User-Friendly

A user-friendly documentation is a winning documentation for any technical writer. But creating one can be tricky, especially if you’re writing for a diverse audience that cuts across locations and …

Read More →