Re: Choosing and managing customer-facing terminology

Subject: Re: Choosing and managing customer-facing terminology
From: punit shrivastava <punitshrivastava -at- gmail -dot- com>
To: jcantel -at- us -dot- ibm -dot- com
Date: Thu, 22 Sep 2011 00:16:15 +0530

Very good question Julian. I am sure many this discussion would benefit
many.

To come to the answer, we follow defined terminology in our org. For example
there are highly technical terms and some abbreviations that SMEs generally
use in their discussions and development too. But, when such terms are to be
produced in documentation our standards dictate what would be used for
clients.

The agreement on terms to prepare the standard terms have been prepared in
agreement with doc team management and other teams.

thanks
Punit

On Wed, Sep 21, 2011 at 11:48 PM, <mattgras -at- comcast -dot- net> wrote:

> Actually, I think this topic may have a big "affect" rather than an
> "impact" (KABOOM!!!!) on user perception.
>
> ----- Original Message -----
> From: "Julian Cantella" <jcantel -at- us -dot- ibm -dot- com>
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Sent: Wednesday, September 21, 2011 10:55:43 AM
> Subject: Choosing and managing customer-facing terminology
>
> 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.
>
> Do you use whatever terminology your subject matter experts provide?
> Consult domain publications and other products in the field?
>
> When you decide what terminology you'd like to use, how do you enforce it
> and ensure that everyone (other writers for the same product, developers,
> maybe even marketing) is on the same page? Do you record your decision in
> a common database?
>
> And finally, what happens when you and your subject matter experts
> disagree? Do you try to put alternatives in front of users?
>
> This topic is pretty broad, but it's an important one that has a big
> impact on users' perception of product and documentation quality.
>
>
> Sincerely,
>
> Julian Cantella
> Information Developer
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 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 mattgras -at- comcast -dot- net -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/mattgras%40comcast.net
>
>
> 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
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 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 punitshrivastava -at- gmail -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/punitshrivastava%40gmail.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
>
>


--
Punit S.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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


Follow-Ups:

References:
Choosing and managing customer-facing terminology: From: Julian Cantella
Re: Choosing and managing customer-facing terminology: From: mattgras

Previous by Author: Re: second acts for technical writers?
Next by Author: Re: Grammar - The Gotcha Microsoft Gives
Previous by Thread: Re: Choosing and managing customer-facing terminology
Next by Thread: RE: Choosing and managing customer-facing terminology


What this post helpful? Share it with friends and colleagues:


Sponsored Ads