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:Re: Tech Writing Problems From:Sue Heim <SUE -at- RIS -dot- RISINC -dot- COM> Date:Mon, 27 Feb 1995 15:08:08 PST
Herman Holtz wanted to know about the most difficult probs tech
1. Writing for vapor ware (or products that do not yet exist).
2. Writing for products in which the user interface has not yet
been frozen (and which will not be frozen until it actually
goes into production. This is known as trying to shoot at a
3. Lack of formal specifications with which to begin writing.
4. Informal development process whereby changes are implemented
at the developer's whim, and you must rely on the developer to
inform you of the change in time to change the documentation.
5. Expectations that, no matter how much the actual development
schedule slips, you are expected to continue to produce legible
documentation within an unreasonable amount of time AFTER
the product has received a) UI freeze (if ever) and b) the product
has been released to FINAL beta and testing.
6. Expecting writers to work on antiquated, obsolete or just plain
inadequate equipment with inadequate tools while the rest of
the development staff (yes, the programmers) get state-of-the-art
equipment and tools simply by asking.