TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Why people read what we write (short version) From:arroxaneullman -at- aol -dot- com To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 22 Mar 2006 12:44:54 -0500
Steven Brown <stevenabrown -at- yahoo -dot- com> asked, "Why don't people read
what we write? Are we at all
responsible?"
A number of very good answers exist.
Foremost is the expectation of readers that they will not easily or
accurately find what they need. People deal with so much
disorganization in life that they learn to be suspicious of anything
claiming to have the answers.
When faced with a question, the easiest thing for most of us is to ask
another human. We know from experience that Joe knows Sue's pone
number; why should we take the time to look it up in the phonebook or
online? But if Joe's not around, we go the next fastest source of
information. And so on down the line until we get to manuals and
references.
The problem with manuals and such is that oftentimes what the user is
asking is not expressed the way it is in the manual. For instance, your
question is "How do I contact Sue" and the manual has that information
under "Phoning Peers." An ideal index would include every synonym and
possible variation for every question that a user has so that you could
easily find the answers. But, that is impossible to accomplish.
Basically, the nature of manuals is that they are slower and less
effective than humans, so poeple refuse to use them (or online help,
etc).
As technology advances and people learn more about how we think,
communicate, and learn, this gap may close. It is our responsibility as
technical communicators to stay with these transitions and use them to
the best of our ability.
Or else we'll all just have to learn to read the friggin' instructions.
;)
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.componentone.com/TECHWRL/DocToHelp2005