RE: Requesting feedback for a user guide - good or bad idea?

["Victoria Nuttle" <vnuttle -at- cauto -dot- com>]

When I started at the job I am now, I was surprised/pleased to see a
documentation questionnaire in each manual, especially since nearly all
the doc is internal anyway.  After working at jobs where the writers
were so forbidden to talk to the users that we often wondered if we even
had any, I was anxious to start getting feedback to see what needed to
be done with the documentation.

Two years later, I have yet to see a SINGLE form or word of feedback
cross my desk.  And no, that does not mean that the documentation is
perfect.  There are manuals that haven't been updated since 1997 while
the software itself changes at least monthly.  I find that at least *my*
users just don't bother with giving feedback, or in many cases, don't
bother with the documentation at all.

--------------------------------------------
Victoria J. Nuttle
Technical Writer, Creative Automation
vnuttle -at- cauto -dot- com
708.236.2377



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Robohelp X3, from eHelp, lets you quickly and easily create
professional Help systems for all your Windows and Web-based
applications, including Net.

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.

Order RoboHelp today: 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.