TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Correct terms vs. commonly used terms From:rjl -at- BOSTECH -dot- COM Date:Thu, 8 Feb 1996 12:11:33 EST
Eric is facing (among other things) the following problem:
>I argued for 15 minutes this morning
>about the difference between using "correct" terminology,
>using what our users expect, or using what they'll need to learn.
I'm assuming the situation is that you've got a "proper" name for a
part ("double-flanged web span longeron") while the users have their
own term ("batman fitting).
A tough call, but the reality is that you likely can -not- retrain
the users to adapt to your terms, especially if the "proper" terms
are longer and more awkward to say. One solution that I've seen work
with some success is to provide a conversion chart of sorts. At one
company, at the back of each maintenance section was a two column table.
One column contained the common-usage terms, the other contained the
equivalent corporate nomenclature. This was useful when the customers
would call in to our support line, it allowed us to ensure that we
and the customer were speaking about the same systems when referring
to certain parts.
rjl -at- bostech -dot- com