RE: Gauging Audience Satisfaction

["Lauren" <lt34 -at- csus -dot- edu>]

Hi Pete,

I have written documentation that I was told would never be read, however,
that was for a job where the previous technical writer produced something
that could not be read.  So I think that somebody was reading it.

It seems to me, that the audience doesn't really know when they're looking
at good technical writing, but they have no problem spotting bad technical
writing.  I do get some feedback, but rather than ask an SME if the document
is good I essentially ask if it is thorough and readable from the
perspective of the intended audience.

My dad always says, "You might not hear the good news, but bad news travels
fast."  For technical writing, I tend to gauge that my work by whether or
not there are complaints and if I get more work.  I work on short-term
contracts that don't really leave time for compliments and instant
gratification from hearing that a job is well-done, so I pretty much accept
that I am doing good work, when I am the contractor that is closing the
project rather than the one that is replaced.

Lauren

> -----Original Message-----
> From: techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com 
> [mailto:techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com] On 
> Behalf Of wawelsmok
> Sent: Sunday, February 25, 2007 5:56 AM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Gauging Audience Satisfaction
> 
> Hi Everyone!
> 
> I've been writing documentation for over 2 years now and the 
> other day this thought came to me head: "Is anyone reading 
> this stuff? Are they happy with it? Finding it useful?"
> 
> Do any of you have contact with your end audience? How do you 
> gauge their satisfaction with your documentation? What would 
> interest me most are methods besides the run of the mill 
> satisfaction survey - if that is even possible.
> 
> I really need some input here from my audience!
> 
> Thanks in advance...
> 
> Pete :)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Create HTML or Microsoft Word content and convert to Help 
> file formats or printed documentation. Features include 
> single source authoring, team authoring, Web-based 
> technology, and PDF output. http://www.DocToHelp.com/TechwrlList
> 
> Now shipping: Help & Manual 4 with RoboHelp(r) import! 
> New editor, full Unicode support. Create help files, 
> web-based help and PDF in up to 106 languages with Help & 
> Manual: http://www.helpandmanual.com
> 
> ---
> You are currently subscribed to TECHWR-L as lt34 -at- csus -dot- edu -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/lt34%40csus.edu
> 
> 
> 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/techwhirl/ for more resources and info.

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

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList

Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -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%40infoinfocus.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/techwhirl/ for more resources and info.