Re: Choosing and managing customer-facing terminology

[Gene Kim-Eng <techwr -at- genek -dot- com>]

Our priorities are:

1.  Brand identification:  if any of our terminology is something that we
have registered or trademarked, that's choice #1.
2.  Industry standards:   common terms familiar to our expected user base
3.  Plain English (or other language):  never make up new terms for anything
that already has a name your readers will  understand (unless they fit itto
1 or 2 above)
4.  Simplified technicalese:  if there's no terminology that fits into 1-3
above, take developers' terms and tweak them until you end up with something
that does.

Gene Kim-Eng



On Wed, Sep 21, 2011 at 10:55 AM, Julian Cantella <jcantel -at- us -dot- ibm -dot- com>wrote:
Hello,

I'm curious about how writers choose terminology that will be exposed to
customers. In particular, I'm thinking about text that is highly visible
and informs the users' view of the product, like embedded assistance in
software documentation.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.
http://www.doctohelp.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat