RE: any cons to single sourcing?

Subject: RE: any cons to single sourcing?
From: Katav <katav -at- yahoo -dot- com>
To: techwr-l -at- lists -dot- raycomm -dot- com
Date: Fri, 18 Feb 2000 08:00:04 -0800 (PST)

Someone made the point that if a reader fails to find
the desired/needed information, the reader will call
tech support.

One of the biggest selling points to promote hiring
qualified technical writers specifically is to AVOID
calls to tech support. Tech support is a very high
overhead operation for most companies. (Worse than
tech pubs?? ;-] )

While no one can _ make _ a user read the
documentation (paper, PDF, HTML, OLH), the
documentation should contain all the information a
user needs for maximum utilization of the product.

How the documentation is presented (which kicked off
this discussion) is another matter. The bottom line is
to present the information to meet the target
audience's needs - DEFINING that is another subject
list members can, maybe "should," discuss.

Katav ( katav -at- yahoo -dot- com )
''Despise not any person and do not deem anything unworthy
of consideration, for there is no person without his hour,
and no thing without its place'' {Ben Azzai [Avot 4:2]}

Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.

Previous by Author: RE: any cons to single sourcing?
Next by Author: Re: What are SMEs?
Previous by Thread: RE: any cons to single sourcing?
Next by Thread: RE: any cons to single sourcing?

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

Sponsored Ads

Sponsored Ads