Why people read what we write (short version)

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

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

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 lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.

Re: Rhetoric And Technical Writing?: From: Steven Brown

Previous by Author: The 10 Worst Presentation Habits
Next by Author: Re: Rhetoric And Technical Writing?
Previous by Thread: Re: Rhetoric And Technical Writing?
Next by Thread: RE: Rhetoric And Technical Writing?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads