RE: reviewing user manuals

[Alan Bucher <bucherino -at- yahoo -dot- com>]

Let them review it. At best, you'll get useful feedback. At worst,
you'll get no feedback at all, but they'll feel good that you
included them in the process, they'll be educated on how much and
what kind of documentation is available, and they won't be able to
later complain about not having an opportunity to provide input.

I usually get a representative from each department to review my
work. Half do, half don't. But everyone appreciates that I asked
them, and it's good exposure for me in the rest of the company.


mark Dsouza wrote:
>I am wondering who all should be invloved in the review process.
>We have customer support guys here, developers and the marketing
>team. It is the customer support who is directly interacting with
>the cusomers. My feeling is the marketing guys should not be
>invloved since we have seperate documents for them, like product
>description documents. Any views on this approach?


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at http://www.ehelp.com/techwr-l


---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.