I know Frans from our involvement in a collaboration between companies to develop and market controlled language checking technology. Frans showed great talent and efficiency as a technology developer and communicator of technical ideas. He is fluent in multiple human and computer languages and his understanding of the principles of controlled language writing and clear communication enable him to provide great value to his customers.

The course was quite challenging for me intellectually, in the way that there were a lot of rules to take in in order to be able to apply them to the text given in the assignement. To spot the errors in the text and choose the correct rule for the problem wasn't always easy, but I thought the assignment itself, i.e. the practical application of the theory, was an effective way to evaluate the learning curve of the student. To cut a long story short, yes, I think the content and the assessment are appropriate. After what I have learned in the course, it seems appropriate and relevant for technical communicators to know STE at a professional level!

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.  

TAI hired Frans to work with our experienced team and help them to improve their ASD-STE100 Simplified Technical English skills. Frans helped us to identify areas for improvement both in our own documents and in those supplied by our customers and partners. At the end of the training, we all had learned simple yet effective methods to improve the quality, readability and compliance of our writing. Most importantly, we learned how to scrutinize text for commonly made mistakes and how to balance compliance with optimum readability. We enjoyed working with Frans, who has a pleasant personality and an open mind. I am happy to recommend him to any company that wants to improve its documentation, be it for compliance reasons or to facilitate translation. Top Qualities: Great Results, Expert, Good Value

I would rate the introduction to ASD-STE100 Simplified Technical English an 8 out of 10. Base on the STE presentation on rules, my favourite would be Rule 2.3 where you use an article (the, a, or an) or a demonstrative adjective (this, these) before a noun. The STE exercises provided in this workshop were of a very high standard and I would rate them 9/10. In terms of trainer evaluation, I would rate Shumin's training an 8 out of 10.

The introduction to ASD-STE100 has offered me some helpful insights into the theoretical background of this technical language standard. The STE rules are governed a logical flow of technical information. I would certainly recommend this course to writers who are interested in changing the way of technical writing with buy-in from the company. Overall, I have enjoyed Shumin's presentation!

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.

Shumin introduced the very interesting concept of a controlled language in the form of Simplified Technical English (STE). My favourite STE rule is to use approved words from the dictionary only as the part of speech given. In the two-day duration, we were able to familiarise ourselves with all the STE rules as well as practical steps for implementation of this controlled language standard. Shumin is very capable of explaining STE concepts in a brief but accurate manner, giving us easy access to a highly technical subject. Love the humour you inject in between lines! Top Qualities: Concise, Personable, Knowledgeable

Frans was both consultant and trainer to my authoring team as we developed a version of STE specifically targeted for the information technology sector. His tremendous experience in the field and passion for conferring that knowledge to our writers was instrumental in our success in adapting the authoring process as well as the documentation itself. In the long run, controlled authoring initiatives are only as good as the writers themselves and the enthusiasm with which they adopt the changed working environment. I believe Frans was critical in assisting with the cultural reformation of my team. Top qualities: Great Results, Expert, High Integrity

The introduction provided a well-rounded history of ASD-STE, the types of industries that use it, and how they use it. I now have a better understanding of what ASD-STE is and how our company should be using it. My favorite writing rule is Rule 1.3 (Use approved words only with their approved meanings.) This rule is the heart of STE. It makes consistency, clarity, and comprehension ubiquitous across all documents regardless of who writes them. It is the main rule that unifies writers with one voice. My favorite STE verbs are Apply, Attach, Make Sure, and Show. The verb Apply has multiple use cases for our documents. The verb Attach is a great utility verb because common alternatives like “mount” are not approved. The verb “make sure” is extremely helpful in cautions and warnings, also in some procedural steps. Finally, the verb “show” is extremely helpful when I write about background processes and how things work in general. 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 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.