My favorite STE writing rules:
* Rule 1.9 and Rule 1.10
When you must select a technical name, use one which is short and easy to understand. Both rules ensure a better understanding of technical contents.
* Rule 3.6
Do not use a past participle with a helping verb to make a complex verb. Past tenses may be adequate for marketing texts due to stylistic reasons, but not for technical contents, where precision and clarity play a major role.
* Rule 5.1
Keep procedural sentences as short as possible. The description of procedures in technical manuals has to be as simple as possible to avoid confusing the reader.
TCLoc Master's Student University of Strasbourg
I am glad to say the STE course attended by team was really satisfactory. Feedback is very positive and we will be interested in repeating the experience in a near future. Top Qualities: Personable, Expert, On Time
Felix Donoso Translation Manager, arvato technical information S.L.
I have worked with Frans for a number of years now, first as a collaborator and later, alas, as a competitor. I have no hesitation in recommending him for his abilities as a linguist, polyglot, and technical innovator. In addition, he is an accomplished speaker, and a great salesman for his products. As someone who works closely with the ASD Simplified Technical English writing standard, I have been impressed with the breadth and depth of his knowledge of that subject. He is a world leader in the implementation of Controlled Language processes. So I am very happy to endorse him.
Rick Wojcik Associate Technical Fellow, Boeing
The introduction to the ASD-STE100 gave me a nice and clear overview of what to expect in the two training days that followed. Consistent language and spelling in STE are the rules I like best. The list of approved and unapproved verbs was a nice surprise for me. Shumin gave a highly practical STE training using relevant and pragmatic examples that relate closely to our field of work.
Maikel Kornuit Technical Writer, Triview
Shumin is personable and easy to work with, so it was great to work together on aviation management related events during her tenure. She is a good communicator, and a consultative manager who would often involve others in problem solving, team building, and focuses her time on more important activities while providing proper recognition, which I am appreciative of.
Joyce Tay Senior Executive, Programme & Event Management at Civil Aviation Authority of Singapore
Shumin gave a two-day ASD-STE100 training to standardize and improve the language used by technical authoring personnel. I learnt a great deal in terms of advantageous STE writing rules for the authoring of technical manuals. Thank you once again for the excellent training!
Fatih Ülger Product Support Engineer, FNSS Defence Systems
The introduction to Simplified Technical English (STE) was simple to follow and understand. Rule 1.4 to use only the approved forms of verbs and adjectives from the STE dictionary is something that I appreciate very much. Applying the rules faithfully was a challenging albeit enjoyable process. There is a lot of good writing rules to learn here. I've found the exercises to be very useful for learning reinforcement, and they have helped me to apply STE rules in a more efficient manner and I've gained a much better understanding of STE as a result. Shumin's training methodology is easy to follow, and she offers us great technical writing advice and has simplified the process for us. Every aspect of this training is a 10/10 for me.
Nour Bazuhair Engineer Trainee, NIMR Automotive
I am giving this training a 10/10. There was a good introductory and explanation to describe the 2-day training seminar. Rule 1.1 0 lets me use words that are: approved in the dictionary / technical names / technical verbs and is one rule I like very much because of its flexibility.
I think rule 1.1 is the most critical and important for STE dictionary. Sometimes I have to use non-approved words as an exception, but I will try to keep this rule 1.1 in my documents for good measure.
Although some of the exercises were tricky, they remind me of each rule application at that time. So they were practical for my role as a technical writer.
I want to recommend this course to current technical writers in Korea or engineers who are interested in writing their own documents effectively.
Seung Eun Lee, Technical Writer DB HiTek
I've found all the rules introduced in this workshop equally valuable and applicable in my field of work. The ASD-STE100 Specification is very useful for searching examples and finding STE compliant alternatives. It was also great that we has such a large number of practical exercises. Personally, it would be more valuable to have more context available. This helps us judge how to apply STE optimally. Thank you Shumin! Your workshop was concise, clear, and pragmatic. I also liked the occasional humour! 🙂
Diane Goodrick, Information Architect/ Author Trainer Schindler Managment AG
The presentation on rules clarified a lot of things of which I was unaware. I have a much better understanding of how to format lists with colons, when to use obey vs. comply, and the differences between notes, cautions, and warnings. Moving forward, I will be able to utilize the ASD-STE rules more effectively to write better documents.
I appreciated the exercises completed in this workshop because they helped me immediately practice and enforce the ASD-STE rules. I like the fact that they were timed. Writing under time-constraints forced me to think quickly and fully concentrate on my writing.
I will definitely recommend this training to writers of many fields, especially technical fields. The material, presentation, and instructor are fantastic. I learned a lot about ASD-STE. Even though I’ve been using this writing convention for almost eight years, formal training brought much clarity and comprehension that I had not previously realized. I now know that an aptitude for writing and a copy of the STE rules is a good start, but not enough. This course takes your understanding to a professional level!
Lauren Gelli Senior Technical Writer, Aerotech Inc.