RE: Metrics used to evaluate Technical Writing/Publications

[Sion Lane <sion -dot- lane -at- unit4 -dot- com>]

Will Husa said:
" I suggest that you speak with your Help Desk. They are on the front line for
complaints. Ask them what your customers are complaining about and then
create a metric based upon that."

As part of this, ask your helpdesk to include a new question in their script "Did you try to solve this issue by checking the documentation?" or words to that effect. If the customer has not tried, the helpdesk could try and point them in the right direction for future reference; and if they have, they should be able to identify why it wasn't helpful. 

Spending a day sitting in on support calls can be a great way to identify holes in the documentation, and a depressing way to discover that nobody actually reads the fm.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW

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

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-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives