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:User Interfaces From:"Eric J. Ray" <ejray -at- OKWAY -dot- OKSTATE -dot- EDU> Date:Wed, 10 Mar 1993 15:55:04 CST
You suggested "updating" the user interfaces, and believe me, if I could, I
would. I spend about one day each week on the help desk, and I suffer as much as
anyone. (BTW--I like to think of my time on the help desk as extended audience
Unfortunately, changing the interfaces or the systems isn't an option, and
we have to deal with what we have. I doubt that this is a unique problem--
few people who are really familiar with the product they are documenting
would say that the product is beyond improvement.
Tying in the other thread--how do we implement "quality" or access to quality
when working with less-than-ideal interfaces and systems? All of the
systems have strengths, but the quality isn't uniform.
I really don't believe that it is possible to write a great manual
about a less than great product, but I would like to have at least
usable or acceptable manuals coming out of my office.