by Gordon Farrington |
![]()
A problem that sometimes occurs, when authors ask my advice about the method of presenting an instruction, is that they use words that I think will not necessarily be understood by people whose mother-tongue is not English.
This is especially true where the words are traditionally generic to the engineering domain, and I advise people to try and avoid using them.
Consider the instruction #1 below:
The replies produced the following statistics:
|
Prefer Para. 1 |
Prefer Para. 2 |
No Preference |
|
2 |
9 |
4 |
Those preferring #1 obviously had a good command of English engineering terms as well as the language, and were used to reading such terms.
Those not specifying a preference were either not in the same engineering domain, wanted to debate the pros and cons of audience analysis, or were totally non-committal, with regard to the intent of the original question.
Those preferring #2 generally stated ‘better understanding’ as the main reason for their choice. These replies represented 60% of all replies and 82% of the replies specifying a choice. Provided that you can get your meaning across to your audience, without causing ambiguity or losing important meaning, do not include terms that you suspect are specific to your domain/locality.
If you do, you run the risk of baffling your audience with ‘technocratese’.