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.
With software, most users employe the "if all else fails, read the
manual" approach.
The stuff I write - most of it - is aimed at helping engineers and plant
operators to keep nasty stuff from getting loose into the environment.
Yes, they read it. We know because we encourage feedback. Every document
contains a statement encouraging users to contact the chief SME (subject
matter expert) if they know of a better way to do things. And we get a
fair number of responses.
When I see documentation that's inadequate - and that probably describes
the majority of the software documentation I see - I'm inclined to write
to the publisher with complaints and suggestions. As an example of one
that I'm preparing now, an on-line help screen told me to execute a
command, but it listed the wrong subdirectory. When I tried to execute
the command, it seemed to work. No error message, but I still hadn't
achieved what I wanted. By looking through the directory on the disk (a
CD-ROM), I managed to find the error.
So, the publisher will hear from me. I figure that I can (maybe) help
future users. It's like writing to a store's management if you get
treated badly. Help them learn.