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.
>So this has raised a number of questions in my mind, most having to do
>with how people use the tools available to them. They can gripe and
>moan about useless manuals, and techies in the field can point to the
>latest in online technology as a means of getting information, but I
>wonder if these aren't all somewhat irrelevant. What do you do if your
>(extremely intelligent but incredibly busy) user community won't use the
>tools available, and the program itself isn't particularly intuitive?
>What to you do about the basic problem of overload? Documentation -
>whether paper or online - can only do so much.
> Elna Tymes
> Los Trancos Systems
As Elna points out, a busy person won't take the time to read if he or she
can get results without reading the documents.
What's more, if the software is intuitive, there is less need to read the
documents until you get stuck. After all, if you are working with a
drawing software application and you see a push button with a box in the
it, it seems intuitive that this has something to do with objects that
have parallel and perpendicular sides.
The less intuitive something is the more we need to read to understand it.
